Build nightlies from this repository #1776
Assignees
Labels
⚙️ Tooling
Improving maintainability and increasing maintainer joy : )
Comments
legoktm
added
the
⚙️ Tooling
legoktm
added a commit
that referenced
this issue
Feb 5, 2024
As part of our monorepo consolidation, we're moving the nightly package building from the securedrop-builder repository to here. The overall process is the same, we build the packages for bullseye and bookworm, then push buildinfo files and then push debs. Some changes: * nightlies will not be pushed if the bookworm job fails. This is largely to simplify the configuration and also because we're going to move to bookworm pretty soon. * Authentication will be done via a GitHub token, which will be configured by infra. Fixes #1776.
legoktm
added a commit
that referenced
this issue
Feb 5, 2024
As part of our monorepo consolidation, we're moving the nightly package building from the securedrop-builder repository to here. The overall process is the same, we build the packages for bullseye and bookworm, then push buildinfo files and then push debs. Some changes: * nightlies will not be pushed if the bookworm job fails. This is largely to simplify the configuration and also because we're going to move to bookworm pretty soon. * Authentication will be done via a GitHub token, which will be configured by infra. * Running `clean-old-packages` will happen via the securedrop-apt-test repository itself instead of during nightly builds. Fixes #1776.
legoktm
added a commit
that referenced
this issue
Feb 5, 2024
As part of our monorepo consolidation, we're moving the nightly package building from the securedrop-builder repository to here. The overall process is the same, we build the packages for bullseye and bookworm, then push buildinfo files and then push debs. Some changes: * nightlies will not be pushed if the bookworm job fails. This is largely to simplify the configuration and also because we're going to move to bookworm pretty soon. * Authentication will be done via a GitHub token, which will be configured by infra. * Running `clean-old-packages` will happen via the securedrop-apt-test repository itself instead of during nightly builds. Fixes #1776.
github-project-automation
bot
moved this from In Progress
to Done
in SecureDrop dev cycle
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should now be able to move nightlies out of the securedrop-builder repository and into this one. The basic workflow should be the same:
dchI think it should be possible to have github-actions do the push (instead of configuring sdcibot and provisioning an SSH key), but it may require an admin to give the job access to a token with write access to the apt-test repository.
The job also invokes the
clean-old-packages.pyscript; that should probably be moved to the apt-test repository itself.The text was updated successfully, but these errors were encountered: