Stream Strategy Implementation in RTC
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
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.
Comments
In our case we are creating change sets from same file.. For eg file.txt file I am modifying and creating three change sets with respect to three bug fix.. And I want to deliver the two change sets with for two bugs to a maintenance stream.. From maintenance stream I want to deliver one change set to my production stream.
For your information.. We have only one component that has been shared among all three streams.
Comments
Vijay Reddy Gaddam
May 06 '15, 6:01 a.m.Are project 1, 2 and 3 are same projects but with three different versions
Balamurugan Selvarasu
May 06 '15, 7:41 a.m.Hi Vijay,