| name | Set Release Blocker |
| description | Set the Release Blocker field on a JIRA issue |
Set Release Blocker
Sets the "Release Blocker" custom field on a JIRA issue. Component Readiness regressions are treated as release blockers, so any bug filed for a regression should have this field set to "Approved".
See the release blocker definition for details on the criteria and process.
Prerequisites
- JIRA_API_TOKEN: Environment variable must be set with a valid JIRA API token
- JIRA_USERNAME: Environment variable must be set with your Atlassian account email
Usage
python3 plugins/ci/skills/set-release-blocker/set_release_blocker.py OCPBUGS-76523
python3 plugins/ci/skills/set-release-blocker/set_release_blocker.py OCPBUGS-76523 --value Approved
python3 plugins/ci/skills/set-release-blocker/set_release_blocker.py OCPBUGS-76523 --value Proposed
python3 plugins/ci/skills/set-release-blocker/set_release_blocker.py OCPBUGS-76523 --value Rejected
python3 plugins/ci/skills/set-release-blocker/set_release_blocker.py OCPBUGS-76523 --value ""
python3 plugins/ci/skills/set-release-blocker/set_release_blocker.py OCPBUGS-76523 --format json
JIRA Field Details
- Field ID:
customfield_10847
- Field name: Release Blocker
- Type: Select dropdown
- Options:
Approved (option ID: 16772)
Proposed (option ID: 16773)
Rejected (option ID: 16774)
Output
Text format (default)
Release Blocker set to 'Approved' on OCPBUGS-76523
https://redhat.atlassian.net/browse/OCPBUGS-76523
JSON format
{
"success": true,
"issue_key": "OCPBUGS-76523",
"value": "Approved",
"url": "https://redhat.atlassian.net/browse/OCPBUGS-76523"
}
Error Handling
- If
JIRA_API_TOKEN or JIRA_USERNAME is not set, the script exits with an error message
- If the API call fails, returns
success: false with the HTTP error details
- The script verifies the update after setting it and reports the confirmed value