Draft: Packaging: Add apt repository (pre-v19.1 packages)
What
This MR was split in smaller MRs for easier reviewing
This MR stores the pre-v19.1 debian packages in a apt repository and then use this repository to run the installation tests. For the moment we only tests debian bookworm and ubuntu focal
I also found a small problem in the postinst script related to systemd.
Why
To allow a better user experience and re-enable the installation tests.
How
We use cloudstorage to the apt repostory. This use the tag gcp_dev at the moment.
Before merging we should use the production tag instead.
A minor modification to CIAO was necessary to use the dev tag.
-
Old packages from the storage are never removed. This should be fixed before merging. Done. I've added an expiry policy of 30 days. -
The secret key used to sign the release file is not associated to a protected branch and therefore not secure. -
the pubkey is stored in the storage itself. This should not be the case as at the moment, anybody can push packages in the storage and replace fake the signature. -
Anybody in the nomadic-labs group can push in the storage. The rights to upload packages in the storage must be restricted to protected branches.
Manually testing the MR
Check if the release pipeline run correctly. Ex : https://gitlab.com/nomadic-labs/tezos/-/pipelines/1238137127 Check if the installation tests run correctly.
Checklist
-
Document the interface of any function added or modified (see the coding guidelines) -
Document any change to the user interface, including configuration parameters (see node configuration) -
Provide automatic testing (see the testing guide). -
For new features and bug fixes, add an item in the appropriate changelog ( docs/protocols/alpha.rstfor the protocol and the environment,CHANGES.rstat the root of the repository for everything else). -
Select suitable reviewers using the Reviewersfield below. -
Select as Assigneethe next person who should take action on that MR
Edited by pietro