Story #8093: [EPIC] Release automation
The release script does not associate a milestone if there are no issues, causing the release workflow to fail
It looks like the
.ci/scripts/update_redmine.sh script expects a match for "Redmine Milestone: .*" in the release commit message. (See: https://github.com/pulp/pulp_deb/runs/1708897755?check_suite_focus=true)
This was not the case for the release generated using the command
python .ci/scripts/release.py minor --lower 3.7 --upper 3.11, thus causing the job to fail.
It is possible this is related to the fact that the release milestone contains no issues (pure pulpcore compatibility release):
The pipeline nevertheless continued with the rest of the release.
It looks like the pulp_file pipeline hit the same issue for the 1.5.0 release:
Please register to edit this issue