Safer branching

October 06, 2016 < 1 min read
Tim Pettersen
Tim Pettersen

A comic in which a developer commits directly to master, temporarily breaking the build. Another developer has the misfortune to fetch master whilst broken, and creates a feature branch from the broken commit. This causes confusion later on when the tests fail in an area of the code that they had not modified on the branch. Had the developer created the branch via the Bitbucket UI, they would have been warned that the branch they were creating a commit from was currently failing the tests.

Try Bitbucket Pipelines

Tim Pettersen
Tim Pettersen

I'm a veteran Atlassian developer with almost a decade of service across the JIRA and Bitbucket teams. I speak and blog about developer workflows, Git, CI/CD, Java, and Atlassian's developer tools. Talk to me about plugin architecture, Node.js, Java, DVCS, or anything cool that you're hacking on!

Links in Bitbucket Pipelines logs

Here’s a small but useful improvement we added last month to Bitbucket Pipelines. You no longer need to copy and paste…
May 23, 2017 < 1 min read
Joshua Tjhin
Joshua Tjhin

New guides for Bitbucket Pipelines

Community Guides Since Bitbucket Pipelines launched back in October 2016, we’ve heard a tremendous amount of positive feedback and excitement about the new…
February 15, 2017 < 1 min read
Claire Maynard
Claire Maynard

Rest assured with Pipelines build notifications in HipChat

Every time you trigger a build in Bitbucket Pipelines, whether by pushing commits or creating a pull request, you have to…
March 06, 2017 < 1 min read
Claire Maynard
Claire Maynard