Update naming convention of tag and publish dynamic pipeline classes
What does this MR do and why?
Describe in detail what your merge request does and why.
To enhance clarity in the patch release automation process for tagging and publishing stages, this MR updates the class name used for generating the dynamic pipeline for these stages.
This is following the MR review feedback for the refactoring of the release tagging: !3491 (comment 2112858559)
Testing
This is to test if the creation of the dynamic pipeline jobs will still work as expected. This is done in a test branch in the ops
instance and in DRY-RUN
mode.
Note: Other jobs in the tag-ci
and publish-ci
are disabled to focus only on the dynamic child jobs. Testing commit
- Tag
Step | Screenshot |
---|---|
After security_release:tag:start is completed successfully, it starts security_release:tag stage which creates and triggers the dynamic child jobs to tag the three patch versions |
- Publish
Related Issue: gitlab-com/gl-infra/delivery#20528 (closed)
Changes
- Update naming convention of tag and publish dynamic pipeline jobs classes from
Jobs
toDynamicPipeline
- Update class name of the
Security:Jobs
class toSecurity::DynamicPipelineBase
- Update security rake tasks for creating dynamic pipeline for both tag and publish stages to
generate_dynamic_pipeline
Author Check-list
-
Has documentation been updated?
Edited by Mawreen Dela Cruz