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.
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!
We’ve been building a plugin to integrate Bitbucket Server and Jenkins CI, and I’m excited to announce that our alpha is ready to download and install. It lets you seamlessly configure a Jenkins job ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events