Jesse Gibbs

Atlassian's build and release infrastructure uses dozens of build agents to run hundreds of builds every day. Needless to say, it's a critical part of how we deliver great software to our customers!

Jim Severino is a member of the internal systems team at Atlassian who is responsible for our build infrastructure. At Summit 2010, he gave a 10-minute lightning talk about Atlassian's best practices for maintaining and continually improving our builds.

Canary Builds


One of the coolest practices that Jim highlights are what he calls "canary builds". These are builds that should always pass, and will only fail if there is a problem with the build infrastructure. By running canary builds to identify when there are infrastructure issues (and then quickly fixing those issues when they do arise), Atlassian's developers have more confidence in the correct-ness of build results.

To learn more about canary builds and other best practices at Atlassian, check out this 10-minute recording of Jim's talk:

Want to check out the slides?


Jim's presentation, as well as all the other great presentations from Atlassian Summit 2010 are available at the Summit 2010 website.

1 Comment(s)

Did Jim purposefully choose a bad name that is nearly identical to "canary releasing", a concept put forward in the recently released book, "Continuous Delivery"?

I'm more than a little upset that the CI and build industry can't get their terminology lined up.

The book gave several nods to Atlassian, but it appears that your lead build guy doesn't know what is actually going on outside of his own little world.

By Andre Gironda at August 10, 2010 9:02 AM

Post a comment

If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.





Remember personal info?

Type the characters you see in the picture above.