-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: add debian build pipeline #287
base: master
Are you sure you want to change the base?
Conversation
@@ -48,3 +48,10 @@ jobs: | |||
with: | |||
user: __token__ | |||
password: ${{ env.B2_PYPI_PASSWORD }} | |||
|
|||
debian-release: | |||
name: Build Debian Package |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this step should be skipped if B2_DEBIAN
vars are missing - we won't be running this on our fork and will be running on the upstream
@@ -0,0 +1,43 @@ | |||
name: Debian Continuous Delivery |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+999999999 for putting this in a separate file
.github/workflows/cd_debian.yml
Outdated
with: | ||
buildpackage-opts: --build=binary | ||
|
||
- uses: qualk/upload-artifact-as-is@master |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is it a good practice to reference an actions master
and not a tag or commit?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried @v0
and @v1
as mentioned in various places, but neither of these works. But since we're uploading to B2, the artifact on Github is actually not needed. Removed.
working-directory: debian/artifacts | ||
run: | | ||
ls -1 *.deb | xargs -I {} sudo apt install ./{} | ||
pip install -U wheel b2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
inception :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
¯\_(ツ)_/¯
- name: Upload to B2 | ||
working-directory: debian/artifacts | ||
run: | | ||
ls -1 *.deb | xargs -I {} sudo apt install ./{} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this a test? why are these packages being installed here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes it's kind of a test
Co-authored-by: Michał Nowacki <77497496+mpnowacki-reef@users.noreply.github.com>
Dont merge this yet, there will be some adjustments backported from Salsa (Debian's Gitlab) needed to make their pipeline pass. |
Repo Setup
add the following pair of secrets for uploading the package into B2 bucket:
B2_DEBIAN_APPLICATION_KEY_ID
B2_DEBIAN_APPLICATION_KEY
add the following environment variable to determine which B2 bucket upload will go to:
B2_DEBIAN_BUCKET_UPLOAD