Open Dojo #5 – Is DevOps the end of QA?

Thursday October 24th, 9am Pacific We all know that the DevOps approach brings developers and operators into closer collaboration. We also know about the emphasis on automation - especially around testing. Do these factors combine to spell the end of the QA department? Is there a place for QA specialists in a DevOps world, and if so, what is it? Join us for a discussion about the challenges QA'ers face in this brave new era, and how teams are making it work. Our esteemed panelists will

Continue reading »

Sharing artifacts between plans, and other best practices

We spend a lot of time on the Bamboo team thinking about how to make really excellent continuous integration (CI) as easy and accessible as possible. Today I'm delighted to share some progress we've made on that front, in two ways. Artifact sharing between plans Yes! You asked for it (Atlassians have been asking for it, too), and now it's here. For the benefit of Bamboo newbies (Bam-noobs?), let's back up and look at what's changed. Bamboo has always been able to pass build artifacts

Continue reading »

Hello again! Glad to see you've come back for more tips on making Bamboo awesome for Git and Hg teams. Today we'll talk all about tests. Grab a chocolate and get comfortable. Comparing test status against upstream When we left off last time, we were talking about slick ways to manage merges to upstream branches. Here's another scenario: let's assume that in your team sometimes a bad code hits the upstream. For example people do commit small fixes directly to the upstream branch. Or there is necessity

Continue reading »

In this post I'd like to highlight various features in Bamboo that were developed separately during the past year or so. If you combine these little pieces together you can make your Bamboo to be a powerful friend in DVCS-oriented software development. This time I'll focus mostly on doing CI on dev branches and merging. Next time I'll cover areas like test failures, quarantining, and a bit about JIRA. One of the main purposes of Bamboo is to build your code, run the tests against it and notify

Continue reading »

We've been thinking a lot about releases in Bamboo Land recently. And I'd noticed a while back that releases of Bamboo are generally down-tempo events for the development team. None of the death marches, mandatory Saturdays, or tension I'd experienced at other companies — just another day at the office. So I asked James and Mark, our product manager and dev lead, respectively, "What's your secret recipe for wrangling releases?" Their answer surprised me. "Having developers own each of the story

Continue reading »

6 steps toward stress-free releases with JIRA & Bamboo

If you've been around agile development long enough, you've heard time and again that doing agile 'right' means making releases a non-event. Sounds great, but how does one get to this magical place? Ever a fan of lists, I put together the top six ways to avoid an ulcer at release time using the combined powers of JIRA and Bamboo. If you're on a team that already maintains steady blood pressure and a resting heart rate of less than 60 bpm in the days leading up to a release, congratulations! Enjoy

Continue reading »