Give ability to record expanded pipeline definition file as job artifact
Problem to solve
As a gitlab pipeline maintainer, I would like to archive the contents of the pipeline definition file(s) (perhaps in a flattened format?) with the associated pipeline/job artifact (especially when using an external pipeline definition per #14376 (closed)), so I can track changes, verify pipeline configuration, and inspect expanded pipeline definition content
Intended users
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
- Rachel (Release Manager)
- Simone (Software Engineer in Test)
User experience goal
User should be able to understand the gitlab pipeline definition file contents associated with a gitlab pipeline run, even when using an external pipeline definition.
Proposal
Include a keyword under 'artifacts' to record the expanded pipeline definition? artifacts, i.e.:
artifacts:
expanded_pipeline_definition:<path-to-file-destination>
Permissions and Security
User with permission to modify pipeline definition would be able to specify this feature.
Documentation
Add documentation to .yml regarding additional artifact definition per potential implementation above?
Availability & Testing
What does success look like, and how can we measure that?
Can view expanded pipeline definition file in recorded artifacts within a pipeline.