Use of batch vs already closed and moved updated sets.

[c_d_mitchell]

Question, 

Once an update set is closed in DEV and already moved to your next instance (I.E. QA / TEST).

Can a batch be created in DEV and those update sets moved into the batch?    

Reason I ask, we have a bunch of individual update sets we did and thinking about the process when it comes to PROD move, not wanting to move them all individually.    A batch would help quite a bit.  

If the answer is yes you can.    Can I then move that batch to QA/TEST without causing issues or duplicate update sets?

[Allen Andreas · Accepted solution]

Hello,

Yes, you can move those update sets into a batch and then move them to Prod.

If you put them in a batch on Dev and then move them again to QA/Test and those sets already went up and were committed...you're going to have duplicative update set names (which is a finding on HealthScan, by the way, so you don't want to do that). And then those changes get recommitted again and could cause issues.

So you can batch them on the next in stack instance and then move them to Prod.

Or batch them on Dev, since they've already gone up the stack, and then take that batch directly to Prod.

Either one of those paths is usually determined by your organization and the guidance given by your CoE or something to that effect. You'll hear opinions from both camps on which way you should go, but I'm mentioning both for full transparency.

Please mark reply as Helpful/Correct, if applicable. Thanks!