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 »

5 tips for great code reviews

In almost every organization, team members collaborate to get work done. Software teams typically transition issues between people for different functions like code development, code review, and testing (even if they are all on the same team). When transitioning an issue from one team member to another it’s important to minimize the amount of ramp up required for the receiver to fully understand the issue. Transferring issues can be extremely expensive as it requires time from not only one,

Continue reading »

Today's best software is made not by lone hackers coding in solitary basements, but by teams of "makers" working together to build the next great thing. But without shared workflows, rigorous testing, and proper communication, the path to release day can look more like a Gordian knot. Enter the Git Essentials solution from Atlassian: planning, tracking, source code management, builds, and deploys–all in a single integrated suite. With these powerful tools, teams can coordinate their work

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 »

As Git solidifies its position as the version-control-of-choice in the workplace, Stash is delighting those workplace Git users. And it's no surprise: Stash is fantastic for organizing repos, digging into the code, and managing the flow of code from branch to branch. But... If you're not using Bamboo for continuous integration and delivery in combination with Stash, you're not maximizing Stash's full potential. Here's why. Efficient use of time & build resources One thing nearly all

Continue reading »