How to integrate my continuous integration system with my bug tracking system?

Question

I use cruisecontrol.rb for CI and FogBugz to track errors, but the more general the answers, the better.

Firstly, this is a technical problem: is there an API for FogBugz? Are there any good tutorials or, even better, pre-written code?

Secondly, this is a procedural problem: what exactly, should CI put errors in the tracker when the assembly breaks? Maybe:

Title: "# {last committer} violated the assembly!"

Body: "# {error tracing}"

I guess this suggests the answer to this question: should I even put CI in my bug tracking?

Answer 1

All the CI settings I worked with sent an email (to the list), but if you want it, especially if your team uses FogBugz as a todo system, you can simply open the case in FogBugz 6. It has an API that allows you to open business. In this case, you can simply configure it to send email to the FogBugz email address, but the API can allow you to do more, for example, assign a case to the last committer.

Brian answers me, if your CI detects a commit failure with a number number, you can even just open an existing case. However, like field coding for every little thing, there is a point where CI automation can be "too smart" to make mistakes and just annoy. Opening a new business can be a lot.

And thanks: it makes me wonder if I should try integrating our Chimps with our FogBugz!

Answer 2

At my company, we recently adopted an (commercial) Atlassian kit - including JIRA for problem tracking and Bamboo for assembly. As in the Microsoft world (I assume we are a Java store), if you get all your products from one vendor, you get a bonus to tight integration.

For an example of how they interacted, view the page.

Enough shilling. Generally speaking, I can generalize their general approach as:

• Create problems in your error tracker (for example: PROJ-123 key).
• When you execute the code, add "PROJ-123" to the commit comment to indicate which error is being fixed.
• When your CI server checks the code, scan the diff commit comments. Record all lines that match the regular expression of the release keys.
• When the assembly is complete, create a report on which keys were found.

In particular, your second problem:

Your CI should not put anything into your error tracker. Bamboo does not invest in JIRA. Instead, Atlas people provided a JIRA plugin that would make a remote api call in Bamboo by asking the question "Bamboo", which lines am I associated with (JIRA problem)? ". This is probably best explained by the screenshot .

Answer 3

CC comes with a utility that warns you of build failures, you probably shouldn't write a failed build to FogBugz — you don’t need to keep track of problems that are fixed immediately (since most broken builds will be)

To go the other way (FogBugz shows the checks that fixed the problem), you need a web repository browser - FogBugz is easy to configure so that it displays the correct changes.