Closed
Milestone
CI update push
This milestone summarizes the present issues and TODOs related to our CI setup and proposes a prioritized order of execution.
Issue Board: https://gitlab.cern.ch/cta/CTA/-/boards?label_name[]=Continuous%20Integration
This is an attempt at ordering the present issues in terms of dependencies, priority, etc.
Gitlab broke mermaid rendering specifically for Milestones, so here is an svg (with clickable links):
Ongoing Issues (open and assigned)
4
Completed Issues (closed)
30
- Buildtree replacement proposal
- Add HTTPS support in CTA CI
- Run CTA Kubernetes with Eos5 using CTA RPMs
- Alma 9 CI runners
- CI publish_tagged_rpm stage succeeds in spite of failure to update the EOS repo
- Repackage MVHTL with common CTA tape configuration
- Add eosreport in CI artifacts
- Support different tpsrv/drive setups in Kubernetes
- Make CI pipeline run for CTA with PostgreSQL Scheduler DB
- Add sonarcloud static analysis to the gitlab-ci, like is done for cppcheck.
- Buildtree corrections for public dev setup
- Migrate catalogue visualisation to catalogue submodule
- Option to remove fflush in mhvtl code.
- Propose adoption of feature toggles in CTA project
- Remove references to ".cern.ch" from CI
- Update CI to k8s infra
- Fix system tests performance.
- Adding alma9 runners to CI
- Write HTTP Tape REST compliance tests for CI
- Simple schema version consistency check in CI
- Test EOS 4.8.101 in CI
- Use cta-release to manage public release
- Test rollback Catalogue Version
- Simplify build procedure to improve portability and not to depend on platform specific tools like yum and rpm
- Create CI machine to test repackaging of MHVTL
- Avoid rebase after updating ReleaseNotes
- External access to CTA CI workflow
- Review CTA CI workflow
- Write scripts to test resilience under server failures
- CI environment explodes if `cta-frontend` crashes or too many errors
Loading
Loading
Loading