add release-please JIRA integration#254
Merged
Merged
Conversation
6cff861 to
d14fb8e
Compare
2527995 to
f704656
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
AAI-812: Extends release-please to add tagging JIRA tickets with fixed version when making a release.
Changed
notify-jirajob to the release-please workflow that automatically tags JIRA tickets with a fix version on every releaseAAI-*ticket IDs from commit messages, PR titles/bodies, and branch namesDetails
When a release is created by release-please, the new job:
AAI-*ticket references from git log and the GitHub API (PR title, body, branch name) to catch tickets not mentioned in commit messagesRequired secrets
Two repository secrets (already added) must be set for this to work:
JIRA_USER_EMAIL— currently set asamanda@biocommons.org.auJIRA_API_TOKEN— Atlassian API token with project and issue read/write access. This token will be expired on 17th April 2026. A BioCloud team calendar event is set one day prior to the expiration date (April 16 2027).Test plan
v1.4.0— correctly identified AAI-796 and tagged it with fix version v1.4.0 in JIRAChecklist