-
Type: Improvement
-
Status: Open
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: GitHub
-
Tags:
For now, the connection between Jira and GitHub relies on Jenkins builds and the Jenkins Jira Plugin .
This is not satisfying because:
- it requires a Jenkins job to "build" a revision for it being recorded into Jira ; reciprocally, it means that some commits may not be recorded
- in its current implementation, the Jenkins Jira plugin is performing a clone/checkout that is highly overkill, consuming time and disk space
Look for a direct integration between Jira and GitHub so that commit messages are parsed and recorded into Jira when referencing a Jira issue.
Most solutions seems tied to Jira Cloud:
- https://marketplace.atlassian.com/apps/1219592/github-for-jira?hosting=cloud&tab=overview
- https://github.com/integrations/jira
- https://github.com/marketplace/jira-software-github
Give a try with:
If satisfying, then ask for (and help with) removal of all dedicated jobs that are only cloning for the recording purpose, not building anything.
- is related to
-
NXBT-2862 Jenkins must be able to comment JIRA tickets
- Resolved
-
NXBT-3309 Add link in Jira to newly opened Pull Requests on GitHub
- Resolved
-
NXBT-3308 Improve GitHub comment on PRs linking to jira issues
- Resolved
-
NXBT-3310 Make some Captain Hook features available on private repositories
- Resolved