Start using GitLab CI for non-ISO jobs
As per our roadmap session made during Summit 2020.
There are many ideas in the air, let's use this issue to gather them and start with something.
Public stuff, no credentials required
- #16712 (closed)
check_PO_master(Jenkins job definition,
check_PObuilder), that runs
lint_po, which itself uses
- It would be nice if translators could see the status of the CI check.
- This would allow us to run whichever version of
i18nspectorwe want, e.g. to benefit from new checks we've requested after translation mistakes caused bugs in Tails.
Checking PO files on any branch, currently done in
features/po.feature: same as
check_PO_master, it would be nice to be able to choose the version of
Check PO files with
msgfmt. We'll see if it catches errors that
i18nspectormisses: if not, we should consider dropping the
- WhisperBack's unit tests (added to our Cucumber test suite via tails#16936 (closed), but arguably this would be better suited for GitLab CI)
- The subset of tails#15330 that can be done without booting Tails
tails/gitlab-config, e.g. in dry-run mode and then a step to manually confirm and run the deploy.
- Issue triaging with
gitlab-triage(currently run manually by intrigeri)
- Weblate integration scripts (could improve reporting, collaboration and overall design)
- We don't need the registry as long as we don't need store any built container images in it. (We have no registry at the moment.)
- For the simple non-ISO jobs we consider here, the Docker runner should work.
- In production we'll want to trust sufficiently the runners: humans make decisions based on CI output. Possibly during initial dev work we can use less trusted runners, and tell developers they shall not trust the results (yet).
- Let developers try the CI out and gather feedback.
- Sysadmins: make the GitLab CI runners into production.
Clean up once GitLab CI is in production
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information