Besides allowing us to manage the permissions and pull request config independently for production vs sandboxes, the main advantage is the automated fork syncing that Stash offers.
The extent of the advantages vary depending on whether you have a branch per release vs feature-based releases via committing to master:
When I first started running automated deployments, I created a branch for each release. Stash's fork syncing would automatically propagate my new release branches down to my UAT and devsb repos - saved me from having to manually create a branch in each place. Changes in production to the metadata affected by a release could roll down to the same-named release branches in the forks, and each branch reflected the current state of the repo's corresponding instance.
Now we do smaller feature-based releases, so the fork syncing benefits are simply that changes made to production can be automatically deployed downstream when there aren't any more recent commits in our sandboxes.
It's officially Tuesday, which means it's officially time for another tip to help you better navigate this space we call the Atlassian Community. 😄 I got a great question from community member, Sa...
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!
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