Bamboo Saves JIRA a Headache

By Anton Mazkovoi, Senior Development Manager
About Developer
On February 20, 2007

Last Friday a code check-in was made that made JIRA functional tests fail only in Standard and Professional editions.
If it was not for Bamboo, we would not have picked that up until midnight on Friday (for a while we have had a nightly build that does a lot of automated testing). Which means that it would not have been fixed until Monday, and as the author of the change is off on holidays for the next 3 weeks, some one else would have had to get clued in on why the build failed, before they fixed it.
Luckily, not too long ago, we have configured Bamboo to run tests for all JIRA Editions after every check-in.
Overall, I think Bamboo just saved us at least 3 hours of precious dev time.

Comments (5)

is this the start of the return to the jira marketing model? Bambambam? This blog usually has interesting material without managing to explicitly ‘sell’, so is enjoyable to read on the whole. An entry saying ‘we used one of our own products and we love it’ is a little bit too kitch, don’t you think?
How about that time you filed an issue when you found a bug in confluence, and it resulted in a developer assigning the issue and then someone else fixing it, thus saving you hours of conversation with customers about how broken the feature is in the next release? Is that the next blog entry?

By Hani Suleiman on February 21, 2007 / Reply
Come on… name the offending party. That’s what makes it fun! I looked at Bamboo. It looks nice, except the reports don’t really make it easy to correlate unsuccessful builds with checkins and ideally a “shame” report that tracks how many times a committer checked in just before an unsuccessful build. Meaning it can’t tell if it was my checkin or your checkin or a weird combination (but it can do trend analysis.

By Andy on February 21, 2007 / Reply
Hani,
I see your point.
> is this the start of the return to the jira marketing model? Bambambam?
I hope not. The thing is, that our nightly build used to fail quite a lot due to the differences in JIRA Editions. Putting Continous Integration in place really saved us dev time.
> Is that the next blog entry?
Nah. I’ll save it until the time they actually start fixing bugs I report

By Anton Mazkovoi on February 21, 2007 / Reply
Just to chyme in… Anton had blogged about this internally at Atlassian (except for the title of the blog, the content as it appears here is identical to what he wrote for employee reading), I thought it was cool and suggested he blog about it here. The developers here frequently blog about the ways we use, modify, or write our software, and I didn’t feel it should be different for Bamboo.
All that said, maybe it would have been better if it had been on the news blog or in our newsletter?
I rarely see negative feedback on the developer blog, so if this was outta line you can blame me. Sorry, folks.

By Jon Silvers on February 21, 2007 / Reply
I personally see no problems with this kind of blog posts. You give people like me ideas on how to improve our development procedures. When I come to your blog I know you’re the developers and you have a positive attitude towards your products.

By dharana on May 10, 2007 / Reply

Atlassian Blogs

Bamboo Saves JIRA a Headache

Comments (5)

Post a Comment or Cancel Reply

Developer

Popular Posts

Popular Tags

Products

Resources

Company

Community

Connect