We're in the process of finalizing a release for our product, which is now version-controlled by Vault.
When we think the code is "good to go", we apply a label. It then goes to the testing team - if they find bugs which need to be fixed then changes are made & we use "Label Promotion" to include the changes under the label. Wash, rinse and repeat until the product is released.
There's a couple of problems with this:-
Firstly, once we've used Label Promotion, Vault no longer gives us a means of retrieving the repository as it was prior to the promotion taking place. We can't see in History that the promotion's happened either.
Secondly, anyone can do the promotion. When you've got quite a few developers making fixes and enhancements on the tip, some will happily sneak them in under the Label via Promotion in order to get them into the Release - there's no way to prevent this via permissions, nor is there any record of it happening. We can't seem to intercept it via a server plugin either. This results in chaos when the test team suddenly find new bugs that were totally unexpected - or worse, that slip through to customers.
Is there any chance Vault could address the above? The way it currently manages labels is really causing us some grief :\
More fun with labels
Moderator: SourceGear
I'd like to add that triggering the server plugin when a label action occurs would be a good start to resolving the issue for us. At least then we could log label changes.
Still, setting permissions on each user for assigning/moving labels and in fact on all actions seems to be a large omission from our perspective.
Still, setting permissions on each user for assigning/moving labels and in fact on all actions seems to be a large omission from our perspective.
Not sure if any Vault folk have seen this thread, so I thought I'd summarise in the form of a "feature request". If possible, could a future version of Vault:-
1. Record Label actions, such as creation, promotion, deletion and renaming somehow. If a label undergoes half a dozen promotions we'd be able to see where they happened, what files were involved, and retrieve the labelled repository at each stage in its promotion history.
2. Allow assigning of permissions to control who can create & modify labels.
3. Report label actions to any server plugins.
thanks
1. Record Label actions, such as creation, promotion, deletion and renaming somehow. If a label undergoes half a dozen promotions we'd be able to see where they happened, what files were involved, and retrieve the labelled repository at each stage in its promotion history.
2. Allow assigning of permissions to control who can create & modify labels.
3. Report label actions to any server plugins.
thanks