Most Stash settings on the repository level are in our case for all repositories for a devision (Project in Stash) identical. Do we have to set the settings for each repository separately? We are speaking about:
Unfortunately the settings are stored against a repository, so there just isn't any way of doing it out-of-the-box. You would either have to do it via REST, or alternatively write a plugin.
Just out of curiosity, is this (mostly) about setting up the repository in the beginning, or would it need to be permanent? I guess I'm asking, if we provided a repository 'blueprint' feature would that be good enough, or do you really need cascading settings?
In my eyes a template configuration (is this what you meant as a blueprint?) for setting up new repositories would be enough (at least in a short distance)
But I fear, as soon this will be available there will be voices which want to have this repsoitory settings enforced from project level. ;-)
In that case you both might be interested in this feature:
Blueprints is what we call project templates. That's probably your best bet. I'm not sure if or when we'll do project-level configuration (although I agree that would be nice too).
For our purpose kind of a project-level configuration would be the wished feature. However, for the moment we can work with the REST.
We are migrating from SVN to Git. It does not often happen that we create a repository from scratch, therefore there is no big need for some sort of a blueprint repository. However, I think this feature could be useful.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot