... | ... | @@ -20,7 +20,10 @@ Each stage of the pipeline has its own folder within this directory containing a |
|
|
The `base.yaml` file dictates the actions and requirements needed for the stage to execute.
|
|
|
Additional `.yaml` files can be present within the stage directories in order to separate the jobs which occur within that particular stage.
|
|
|
|
|
|
<details><summary>
|
|
|
|
|
|
## Contributor project requirements for ironbank-pipeline use
|
|
|
</summary>
|
|
|
|
|
|
### Adding a project pipeline in settings
|
|
|
|
... | ... | @@ -42,7 +45,12 @@ The other approved template is `templates/distroless.yaml@ironbank-tools/ironban |
|
|
|
|
|
Please review templates/README.md for more information on which template your project needs.
|
|
|
|
|
|
</details>
|
|
|
|
|
|
<details><summary>
|
|
|
|
|
|
## Pipeline artifacts
|
|
|
</summary>
|
|
|
|
|
|
To access artifacts for each job, select the job in the UI on the `CI/CD -> Pipelines` page by clicking on the button for that job.
|
|
|
In the top right hand corner of the screen, there is a box which says "Job artifacts" and contains buttons which say "Keep", "Download", and "Browse". Select the button which corresponds to the option you want.
|
... | ... | @@ -50,6 +58,8 @@ In the top right hand corner of the screen, there is a box which says "Job artif |
|
|
Job artifacts are retained for the latest pipeline, removed after one week in most cases.
|
|
|
A new pipeline run will need to occur in order to produce job artifacts after this period of time.
|
|
|
|
|
|
</details>
|
|
|
|
|
|
<details><summary>
|
|
|
|
|
|
### Pipeline Stages
|
... | ... | |