How do Atlassian tools work together, especially with the recently acquired Fisheye, Crucible and Clover?
You’re not the only one mulling this over. In fact, that’s exactly what reporter Jonathan Erickson of Dr. Dobbs Portal was wondering during a recent interview with Pete Moore, Clover Product Manager. Pete explains the integration through real-life scenarios:
To give you a feel about how all the products are going to come together, here’s a couple of examples of the very cool kind of things that are on the cards:
- A developer checks in.
- Bamboo automatically kicks off a build.
- Thanks to Clover 2, Bamboo only runs the tests that exercised the classes that were changed.
- The build breaks.
- Bamboo sends a notification to the author including a diff of the couple of lines that most likely broke the build.
- Bamboo can then create a Crucible code review for the commit that broke the build. Thanks to FishEye, it can include the author of the change, the tech lead(s) responsible for that source, and the last couple of developers that worked near that code.
- Finally it can add a comment to any JIRA issues that the commit is related to. Any of these artifacts can be easily included in Confluence wiki pages.
And there you have it — a few of the many ways Atlassian products work well together.
For more details and an entertaining read, check out the entire interview, Collaboration Goes Down Under to Meet Testing.
Looking for more specifics on how Clover, Fisheye and Crucible are being updated and integrated? Read Pete’s recent blog entitled Releases, releases, releases.