Branching – A basic branching strategy

As you get more developers on your team you will probably need to think about branching in your source repository.

In a recent project the team were using GIT as a source repository and Jenkins for Build, Unit Testing and Integration Testing.

Sprints were managed in Jira and branch names were mapped directly to Jira card numbers. (The format was feature-x where x is the numerical id of the card. So, If I was working on card DCAP-123 my branch would be called feature-123.)

The diagram shows the process with a ‘Spike’ branch under construction to allow the team to work on experimental features.



Published by

Adam Scoot

After the consultancy, its all about the agile, a little bit of scrum and delivery. Other than that; Ski hard, Ski fast or go home.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s