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 »

Like an ogre One of my colleagues had an opportunity to work closely with Clover's HTML code coverage report. After several days, he stated: "Do you know? Clover's HTML report is like an ogre from the Shrek movie - it is composed of layers. Every time I thought I already learned this report, I was discovering new, tiny but yet extremely useful detail in it. I don't even know if I reached the bottom already." Layers of code coverage As a Clover developer, I know these reports from the inside-out.

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 »

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 »