Is there a way to prevent deliveries from a stream?
My customer would is getting ready to have several dozen new developers start using RTC. They have all of their code imported into about 20 components. They would like to have the new developers 'practice' for a week or so before making real changes to the code. I told them that we could configure a stream (or another project) that could hold the 'practice' change sets and baselines - but - I recommended that they not do this because of the chances of having an accidental delivery from the 'practice' stream to the real stream later. Is there any way to guarantee that there's no chance of the 'practice' code getting delivered accidentally to the real code in the future? If we delete the 'practice' stream, my understanding is that the change sets and baselines still exist in the component and could be accessed in the future. Can this be done? Or is there a better way that I haven't thought of? Thanks in advance. |
2 answers
If you have implemented Team Area Structure and assigned team's as stream owners, you wouldn't have any problems. But if you haven't set team areas as owner to "the real streams" those users will be able to chek-in&deliver to those streams.
Example: Stream Name ->Owner Team Area Real Stream -> Company's Dev Team Real Stream II -> Company's Dev II Team Practice Stream -> Company's New Recruit Team Besides that, I have nothing in my mind. |
Hi Francis, you could also configure a precondition to prevent deliveries to a certain stream. In the process configuration > Team Area > Operation behavior section you can configure it in a variety of ways to meet your needs. What I think might be easiest would be to keep the practice users out of the production team area and only allow the production team permissions to deliver to that stream.
|
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.