Tasks #63548
openChange jenkins job to not push release tag to the ceph repo
0%
Description
Currently, the Ceph jenkins job pushes the release tag from the ceph-releases repo to the ceph repo straight away. However, it would be better to let developers do this part manually in case the release needs to be rebuilt.
Updated by Laura Flores 6 months ago
To be clear, the flow is such:
- The build lead starts the build job, as defined in https://docs.ceph.com/en/latest/dev/release-process/#starting-the-build
- This job builds the distros, then leads to the jenkins tag job.
- The tag job (https://jenkins.ceph.com/job/ceph-tag/) creates the version tag commit and pushes it to https://github.com/ceph/ceph-releases/tags and https://github.com/ceph/ceph/tags.
The issue with this flow is that if we ever get to the point where we need to redo a part of the release (as with v18.2.1), we don't want the tag to be pushed right away to https://github.com/ceph/ceph/tags. The ideal result would be to preserve the action that pushes the tag to https://github.com/ceph/ceph-releases/tags, and then let a Ceph developer manually push the tag from ceph-releases to https://github.com/ceph/ceph/tags once we're sure the release is ready.
The fix would involve modifying one or more of the ansible role definitions, which I believe are defined here: https://github.com/ceph/ceph-build/tree/main/ansible/roles/ceph-release/tasks