How to lock a baseline/snapshot and a build results
![]()
Andrea Toncelli (27●4●9)
| asked Sep 25 '14, 3:19 p.m.
edited Oct 10 '17, 1:10 p.m. by David Lafreniere (4.8k●7) Hello,
Not all the builds, snapshots and baselines are created equal.
If I run an automation process, I have hundreds of builds during the week. I would like to lock the build that I send once a week to the Quality team and with that build, the baseline and snapshot associated with it. I noticed that all the build results can be deleted as well as the snapshots. For the baselines I can rename them. I like that functionality up to a point. I would like to mark one of them as 'released' (I am using here a Rational Synergy term). In Synergy I can release a baseline, at that point, NOBODY can touch, rename or delete that baseline and the version associated with that baseline (in RTC would be the baseline name) is locked, no other baselines can be created wit that that exact name.
I do realize RTC is different, so.... how can I do something similar to that in RTC?
Same question applies to the stream in similar circumstances. At the end of my 'release' cycle I want to ship the product, so I need to lock the stream. Everybody needs to be able to see it as a record but nobody should be able to add change sets to it, or rename it.
Thanks
|
Accepted answer
![]() This post/question actually has a few questions in it. Geoffrey explained some of them, but I'll provide an 'answer' here as well, with a summary of what was already answered plus answers to other questions. Feel free to open up enhancement requests or RFEs for any behavior that is not present and you feel would be beneficial.
Michael Valenta selected this answer as the correct answer
Comments I find it really interesting how this site is ..... "It's all about the answers!"
It only took 3 years to get an answer to some simple questions.
FYI: based on the quality of the product and the quality of the support (see above) I have moved on to better tools.
Best Regards
![]() FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
So an answer is given about 3 hours after the original question, and then 3 years later someone from the development team expends the effort to provide updates to the answer based on enhancements that have released since the original question, and somehow this is an indictment of the forum and the quality of support? |
One other answer
![]()
Geoffrey Clemm (30.1k●3●30●35)
| answered Sep 25 '14, 5:29 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The content (set of versions) referenced by a baseline is immutable, so you do not have to be concerned about that being changed by anyone. You currently cannot lock the name of a baseline, but through access control, you can restrict who can change it. A baseline has a Unique ID, so to have a reliable reference to a baseline, store its ID in addition to its name.
If you want an immutable reference to the state of a stream, just create a snapshot of that stream. If you want to reproduce that state of the stream (including its history), just use that snapshot. Comments Hi Geoffrey,
Thanks for the info.
It sounds like I cannot lock a build result and snapshot from being deleted or a baseline from being renamed beyond project permission.
Would it be possible to request an enhancement to give the opportunity to "release/lock" some build results/baselines/snapshots?
Thanks ![]() FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Yes, you are always welcome to submit an RFE.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.