It's all about the answers!

Ask a question

Best practice to handle flow of stream and changesets


Kiran A (31122) | asked Oct 30 '19, 10:44 a.m.

Hi Team, 


We have Dev, SIT, UAT and the Production stream. As a process we defined the work flow that after development the CS's should go through SIT, UAT and then the final Production stream. But incase, we want to deliver the CS's from direct Dev to the Production stream and we know it as only limited CS's with no fixes and we are good to go to the Production at that time just need to set the flow to the Production stream.The scenario which we have is, there might be a chance of mishandling the CS's along with other CS's which is already present in the SIT and UAT means there might be a chance or mistake to pick a wrong CS's to the next stream. 

To avoid this confusion, we need to know the best practice to handle streams and delivery of the changesets.

Regards,
Kiran

One answer



permanent link
Geoffrey Clemm (30.1k23035) | answered Oct 31 '19, 6:48 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

For those change sets that you want to deliver directly from Dev to Production, you can do so if you also deliver them to SIT.  When those change sets finally get delivered from UAT to Production, RTC will notice that they already are in Production, and will do the right thing (i.e. not duplicate the delivery).


If those change sets depend on change sets that you don't want to deliver, RTC will warn you, and will not let you deliver them directly to Production without their dependent change sets also being delivered.

Your answer


Register or to post your answer.