Forcing snapshot/baseline creation
![]()
We have 11 components that may be the recipient of changes for a given sprint. At the end of the sprint, a baseline/snapshot is created to mark the state of the codelines in the components but only those with changes not already associated with a previous baseline will be marked with the new one.
This sometimes cause confusion because developers might be instructed to get "Baseline 5" but for some components they can only see "Baseline 3". Is there a way to force all components in a workspace to be marked with the intended baseline name regardless if they have new changes or not? I am thinking something along the lines of SVN wherein you can say "update to revision 5" and the files will be updated to the that revision or the most recent. This might not be a perfect analogy since SVN does a directory-based tagging. ciao! |
One answer
![]()
Hello
This is not possible w/the current UI (although possible through API). An alternative would be to have users "replace with snapshot" (assuming they have nothing outgoing). JohnC SCM Server ramfree17 wrote: We have 11 components that may be the recipient of changes for a given |