Actions
Task #8119
closedStory #8093: [EPIC] Release automation
Automate the pre-release steps
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
Extend the current release workflow in Github Actions. Change the trigger to a manual one[0][1] that takes a version argument (eg 3.11.0). This workflow should be idempotent so that if any step fails, it can be re-run.
This workflow will:
- Check to ensure there is a corresponding milestone in redmine
- Run the release script and push commits to master
- Assign the issues from the release script to the milestone in redmine
- Create a new tag and Github release
- Run the rest of the steps of the current release workflow (which should publish pypi package, docs, etc)
[0] https://github.blog/changelog/2020-07-06-github-actions-manual-triggers-with-workflow_dispatch/
[1] https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow
Updated by dkliban@redhat.com almost 3 years ago
- Release branch must exist to create a release
- pulpcore lower and upper bounds must be already present on the release branch
- release engineer starts the release flow on a release branch
- the workflow generates the changelog, removes .dev from version, bumps the version to the z.dev, creates a release from the release commit
Updated by dkliban@redhat.com almost 3 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to dkliban@redhat.com
Added by dkliban@redhat.com almost 3 years ago
Updated by dkliban@redhat.com almost 3 years ago
- Status changed from ASSIGNED to MODIFIED
- % Done changed from 0 to 100
Applied in changeset plugin_template|cc4df914e59fe2265207dc2ac3b42a4f97a60554.
Updated by daviddavis almost 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Automates pre-release steps for release workflow
fixes: #8119 https://pulp.plan.io/issues/8119