Project

Profile

Help

Task #6899

Task #5529: [Epic] Automate parts of the release process

Automate the redmine steps of the release process

Added by daviddavis over 1 year ago. Updated about 1 year ago.

Status:
CLOSED - COMPLETE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
CI/CD
Sprint:
Sprint 76
Quarter:

Description

This would handle step 8 of the Release Guide.

Design

Update the publish pypi job with the following changes:

First, add a check at the beginning of the script that checks for a milestone in the redmine project with the name == version being deployed. Also, all issues that are part of the release should be at MODIFIED. The job should fail if these conditions are not met.

After the package has been released to pypi, associate all the issues to the milestone and then set their status to CLOSED - CURRENT RELEASE. Lastly, the job should close out the milestone.

Open Questions

How does the job determine the issue numbers? One possibility is to parse the changelog but this seems difficult and error-prone.

Associated revisions

Revision 1cf2de4a View on GitHub
Added by Fabricio Aguiar about 1 year ago

Validate redmine milestone and close issues

https://pulp.plan.io/issues/6899 closes #6899

History

#1 Updated by daviddavis over 1 year ago

  • Description updated (diff)

#2 Updated by fao89 about 1 year ago

  • Groomed changed from No to Yes

the release script already get the issue numbers, I believe we could add it in the release commit and parse the release commit:

the commit could be: query: https://pulp.plan.io/issues?set_filter=1&status_id=*&issue_id=5707,5894,5896,5941,5955,5955,5833,5867,5870,5873,5706,5941

#3 Updated by bmbouter about 1 year ago

This is a great idea! Here are a few questions:

How is the stage/script re-run/resumed when all issues are not at MODIFIED?

How is the stage/script re-run/resumed when CLOSED - CURRENT RELEASE fails due to Redmine blocking that from being changed?

#4 Updated by fao89 about 1 year ago

release script can check for the statuses, so if one issue is not MODIFIED it will fail, so the script will fail before you open the PR

#5 Updated by daviddavis about 1 year ago

Also, it's possible to restart the release stage or even the entire build in Travis if it fails.

#6 Updated by fao89 about 1 year ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to fao89

#7 Updated by daviddavis about 1 year ago

  • Sprint set to Sprint 76

#9 Updated by fao89 about 1 year ago

  • Status changed from ASSIGNED to NEW

#10 Updated by fao89 about 1 year ago

  • Status changed from NEW to ASSIGNED

#11 Updated by fao89 about 1 year ago

  • Status changed from ASSIGNED to POST

#12 Updated by Anonymous about 1 year ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

#13 Updated by daviddavis about 1 year ago

  • Status changed from MODIFIED to CLOSED - COMPLETE

Please register to edit this issue

Also available in: Atom PDF