without any add on create development, staging environment

I am not sure if I am doing right or not. I want to create development, staging and production environment for my repository.

We got different hosting server for staging and live.

I am thinking to create branch staging and development branch from master.

So i can clone only staging branch to my staging server.

I am thinking to keep these two branch permently. 

Is this right? Also how feature branch will work in this case.

Hope to hear from anyone soon.


1 answer

0 votes

Hi Ashish, there are different types of workflows; having a branch for each environment is common but there are some risks (it can originate conflicts between the different branches). In many cases, it's better to have just one branch in all of them, as you should never have commits in production that are not in staging. The history should be linear, so when you have a change in production, you know this change is present in all the previous environments.

You can read more information about different types of workflows (including theFeature Branch workflow) at Comparing workflows.

There's also a discussion about that at Git with development staging and production branches, it might interest you.

Hope that helps!


Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

1,944 views 7 10
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you