Create working master pipelines for staging enviroments
Background
When the infrastructure team upgrade infrastructure, Big Bang, VAT, or Ironbank Front End we need to have confidence that the pipelines still work. However pipelines staging are in various states due to staging being used for pipeline testing and experimentation. The infrastructure team does not have consistent pipelines to test wether changes break something.
We need pipelines that we know will pass 100% if there is nothing wrong with a Big Bang and and infrastructure related changes.
Acceptance Criteria
-
Create a repository in code-mario.staging.dso.mil and code-ib-zelda.staging.dso.mil that mirrors of the master branch of the ironbank-pipeline repository under the ironbank-tools group for each gitlab server. Name this repository "ironbank-pipeline-golden" -
Create repositories that under the ironbank-containers group that mirrors these repositories respectively, they should be placed in a group called "golden-test". -
https://repo1.dso.mil/dsop/redhat/ubi/ubi8 -
https://repo1.dso.mil/dsop/redhat/ubi/9.x/ubi9 -
https://repo1.dso.mil/dsop/redhat/openjdk/openjdk17 -
Run the pipeline against the master branch of these images, and make sure they all pass. -
Go into gitlab ci and re-create the same variables that these repositories have with their production counterpart. ONLY at the repository level.
In the CI/CI settings of these container repositories, set the CI setting to use the trigger.yaml file from the ironbank-pipeline-golden image that you use.
Definition of Done
- [ ]
- [ ]
Edited by Ryan Flynn