Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>At my company we've recently adopted the (commercial) Atlassian stack - including JIRA for issue tracking and Bamboo for builds. Much like the Microsoft world (I'm guessing - we're a Java shop), if you get all your products from a single vendor you get the bonus of tight integration.</p> <p>For an example of how they've done interoperability, view their <a href="http://www.atlassian.com/software/bamboo/features/interoperability.jsp" rel="nofollow noreferrer" title="interoperability">interoperability page</a>.</p> <p>Enough shilling. Generally speaking, I can summarize their general approach as:</p> <ul> <li>Create issues in your bug tracker (ex: issue key of PROJ-123).</li> <li>When you commit code, add "PROJ-123" to your commit comment to indicate what bug this code change fixes.</li> <li>When your CI server checks out the code, scan the commit comments of the diffs. Record any strings matching the regex of your issue keys.</li> <li>When the build completes, generate a report of what issue keys were found.</li> </ul> <p>Specifically to your second problem:</p> <p>Your CI doesn't doesn't have to put anything into your bug tracker. Bamboo doesn't put anything into JIRA. Instead, the Atlassian folks have provided a plugin to JIRA that will make a remote api call into Bamboo, asking the question "Bamboo, to what builds am I (a JIRA issue) related?". This is probably best explained with a <a href="http://confluence.atlassian.com/display/BAMBOO/Bamboo+2.1+Release+Notes#Bamboo2.1ReleaseNotes-LinkIssuesandBuilds" rel="nofollow noreferrer" title="screenshot">screenshot</a>.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload