Issue #8112
closed
Story #8093: [EPIC] Release automation
The release script does not associate a milestone if there are no issues, causing the release workflow to fail
Description
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):
https://pulp.plan.io/versions/173
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:
https://github.com/pulp/pulp_file/runs/1571504921?check_suite_focus=true
Updated by quba42 about 3 years ago
I hit the same issue again with the 2.11.0 compatibility release: https://github.com/pulp/pulp_deb/runs/2227967516
Updated by quba42 about 3 years ago
- Subject changed from Update redmine job failed during pulp_deb 2.9.0 release pipeline. to The release script does not associate a milestone if there are no issues, causing the release workflow to fail
Updated by daviddavis almost 3 years ago
- Status changed from NEW to CLOSED - CURRENTRELEASE
We believe that this issue is fixed. If not, please open an issue at https://github.com/pulp/plugin_template/issues.
.