Consider migrating from Jenkins to GitLab CI
(for now this is a placeholder to take notes)
General benefits
- This could allow developers (FT) to do stuff that otherwise requires involving sysadmins, e.g. adding a new dependency for the build or automated test suite.
Test suite
We could split the test suite into several jobs:
- fragile
- slow
- not release blockers
- everything else
Expected benefits:
- It is easier for developers to tell at a glance which sort of tests failed, e.g. to ignore known-fragile ones.
- Smaller latency of CI when our systems are not overloaded.
- Compared to splitting into 1 job / Cucumber feature: we still benefit from the performance boost provided by our snapshots system.
Other notes
- Probably needs quite some FT work together with sysadmins.
- For S11, this fits in
D.1 - Make Tails development process more efficient
: Moving from Jenkins to GiLab CI would make it easier for developers to process failures and decrease latency of CI results.
Resources
- fd.o CI templates can greatly help setting up and maintaining container images, including those that will be run on KVM-enabled runners
Edited by intrigeri