Archives for the tag: continuous integration

Guest post: Keeping master clean with Bamboo and LEDs

This is a guest post from David Cook–growth hacker at Jut, Atlassian alumnus, and possibly the fastest man on earth. A few months ago, we realized we had a problem with our automated builds in Bamboo. There were some tests that only ran on master, and developers would sometimes merge in a branch that had passed locally, but would break on master. Then other developers would merge to master when it was broken–making it more difficult to figure out why the builds had broken in the first place.

Continue reading »

Whether you're deep into CI or just getting started, planning for scale should always be considered. So today we're excited to announce Bamboo 5.7 with new features to help you manage your servers as you scale up CI. Expiry has been extended to Deployments The biggest benefit to using a CI system is how frequently you can build and deploy your applications.  Of course, over time many artifacts, results, and logs are created that build up and become a space hog on your servers. Bamboo has helped

Continue reading »

If you follow Atlassian, you know we're big on continuous integration ("CI") and Git–separately, sure: but even bigger on the power that the two offer in combination. Today I want to share some tips for getting your CI system to interact optimally with your repository, which is where it all begins. 1: Avoid tracking large files in your repo One of the things you often hear about Git is that you should avoid putting large files into your repository: binaries, media files, archived artifacts,

Continue reading »

Last week we gathered up several hundred of our fellow software makers and talked about four development practices you can use to keep from getting your wires crossed: feature branching, continuous integration, pull requests, and information radiators. These are practices that teams at Atlassian have been really successful with, and–to the surprise of exactly nobody–we've baked support for them into the Git Essentials solution. ICYMI In case you missed it, here are the key points we covered: Feature

Continue reading »

What the heck is the quiet period? The quiet period is a optional setting on each repository connected to Bamboo. After seeing that a commit has been made to the repo, the quiet period (if enabled) tells Bamboo how long to wait before actually kicking off the build. It lives under the Advanced options in the Linked Repositories configuration screen. Here's what the configuration looks like: Fun Fact! The quiet period was originally invented to cater for the fact that CVS commits are

Continue reading »

Last week, Tim Pettersen and I held a webinar on optimizing your CI system for Git. We had a great time putting it together, and attendees asked some truly excellent questions, so I think we can safely call this one a success. To sum up, we covered... Why branch-and-merge workflows are so effective (and easier in Git than in SVN, et al) Strategies for reducing build times How to reap the benefits of "pure" CI without piling changes willy-nilly onto a central branch Git hooks that reinforce

Continue reading »