At my organisation, we use the Driessen branching model for all our projects, which is nearly the same as Stash's default branching strategy. However, the default branch and the production branch still need to be changed in all our repositories.
Is there any way to apply these new settings system-wide? And can we store them in, say, the stash-config.properties file so that the default settings are applied to new repositories as well?
I'm afraid there isn't any way at the moment. Your best bet at the moment is to script the configuration of each repository via REST, or alternatively add a plugin that automatically adds settings to newly created repositories.
It's something this is a general problem in Stash, ideally we have a way of inheriting settings from projects (or globally).
This is certainly something we've talked about internally, although I honestly couldn't give you a timeline as to when (or if?) that might happen.
This is one issue which is vaguelly linked, and may be worth watching/voting on for updates to this area.
The branching model REST API is read-only afaik, so how to do it via the REST API?
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
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