Stream Strategy Implementation in RTC
Hello All,
The below scenario I want to implement in RTC. Anyone aware of this scenario?
Under development stream: (all are checked in )
Work Item 1 – Project 1 – File 1 - Version 1
Work item 2 – Project 2 – File 1 – Version 2
Work Item 3 – Project 3 – File 1 – Version 3
To be delivered to UAT stream: ( following 2 work items in same deliver)
Work item 2 – Project 2 – File 1 – Version 2
Work Item 3 – Project 3 – File 1 – Version 3
To be delivered to Production stream: (only following work item)
Work Item 3 – Project 3 – File 1 – Version 3
Regards,
BalaMurugan S
2 answers
You can do this kind of cherry picking e.g. by having a repository workspace for each of the streams and accepting the changes you want in there from the work item. You can also deliver change sets selectively from a repository workspace.
This capability relies on the fact, that you have to make sure not to introduce a gap between the change sets. This means, you can not have changes to the same file in any one of those change sets.
If you have a change set cs1 that modifies file 1.txt and 2.txt and later a change set csn that modifies 2.txt and 3.txt, you can not deliver csn independently from cs1 any more as this would introduce a gap.
This capability relies on the fact, that you have to make sure not to introduce a gap between the change sets. This means, you can not have changes to the same file in any one of those change sets.
If you have a change set cs1 that modifies file 1.txt and 2.txt and later a change set csn that modifies 2.txt and 3.txt, you can not deliver csn independently from cs1 any more as this would introduce a gap.
Yes it is possible but with some complexity, only if you maintain completely three different versions of a files in a project.
Maintain three components say C1, C2, C3. Share the same project for all the three components with workitems 1 ,2 and 3 respectively.
In Development Stream Have all the three components.
In UAT Stream, Have only components C2, C3.
In Production Stream, Have only Component C3.
Later you can link(as flow targets) one stream to other, and deliver the things that are only needed.
Caution: Only deliver the changes from stream to stream, but not the components.
Comments
Comments
Vijay Reddy Gaddam
May 06 '15, 6:01 a.m.Balamurugan Selvarasu
May 06 '15, 7:41 a.m.