Say hello to JIRA Agile and JIRA Capture Learn More »

Archives for the tag: branching

Our recent webinar featuring product rock stars Jens Schumacher and Ken Olofsen gave a great overview of git workflows. Branching workflows go from bare and simple, to complex, robust, and defensive. What is the level of complexity and safeguard needed by your organization? This post covers the compromise between nimbleness and robustness, with some guidelines to choose your own git adventure and lessons learned inside Atlassian. The aim of this article is to give you the insight and

Continue reading »

Stash 2.8: branch-based workflows simplified

Last week, we unveiled tight integrations between Atlassian software development tools that guide your entire branch-based workflow from JIRA issue all the way to merge. Branches are a fundamental component of Git workflows. But choosing a good branch model is the key to making sure your Git workflow is a successful one. Just as the right cheese is crucial for a perfectly creamy mac n' cheese, streamlining how your team creates, names, and merges branches can affect how the team uses a workflow. In

Continue reading »

One question that every team faces when moving to Git is what development workflow to use. Since every team is different and has different requirements, there is no one-workflow-fits-all approach. However, there is one rule all teams should follow when looking for a new workflow to adopt: Keep it simple. Doing so will reduce the number of mistakes people can make, and will help with adoption. On the Stash team, we've adopted one of the simplest Git workflows possible. And since so many of you

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 »

New Release Offers Plan Branches, Quarantined Tests and Easy-to-Use UI SAN FRANCISCO & SYDNEY, March 29—Atlassian, the leading provider of collaboration software for product teams, today announced Bamboo 4, the newest release of its continuous integration and delivery server. Bamboo 4 enables software developers to automatically test code on development branches before merging with the main code line. It provides automatic plan branching and merging for distributed version control systems

Continue reading »