Spike: How to add a job that doesn't exist in .gitlab-ci.yml to a pipeline
Time-box: 3 days effort.
Topic to Evaluate
Requirements for #270880 (closed) call for mandatory security jobs running as part of a CI pipeline.
This cannot depend on a user's action to include the job(s) in the .gitlab-ci.yml
file. One must also be unable to skip the job, for example by disabling it in .gitlab-ci.yml
.
Tasks to Evaluate
-
Determine feasibility of the feature -
Create issue for implementation or update existing implementation issue description with implementation proposal -
Set weight on implementation issue -
If weight is greater than 5, break issue into smaller issues -
Add task -
Add task
Risks and Implementation Considerations
Team
-
Add workflowplanning breakdown feature and the corresponding ~devops::<stage>
and~group::<group>
labels. -
Ping the PM and EM.
Edited by Alan (Maciej) Paruszewski