Moving multiple update sets to PROD

terp
Giga Contributor

‎01-08-2018 07:03 AM

Hi Community,

I'm looking for suggestions or thoughts on moving update sets to PROD.   (Cloning the environment isn't an option).   Our team built an app and has 10+ update sets in TEST, I need to move them to PROD.   Is it best to move the updates sets one by one? or merge them into one update set?

If I move them one by one, I'm concerned about the collisions AND identifying the order of the update set configurations.   Any thoughts after loaded, on how to identify the order I should commit the update sets?

What kind of issues have you run into when merging into 1 update set?

Thanks.

Labels:
0 Helpfuls
  • 1,460 Views
5 REPLIES 5

Uncle Rob
Kilo Patron

‎01-08-2018 07:07 AM

The answer is it depends.   There's definitely times where you'll want to merge, and times when 1-by-1 is better.
Unfortunately the *best* thing to do is anticipate this problem and build a 'play book' for release as you develop... *especially* if you're working under a single application.


Most ServiceNow partners have established practices for this.


0 Helpfuls

terp
Giga Contributor
In response to Uncle Rob

‎01-09-2018 10:26 AM

Thanks for taking the time to respond Robert.   Unfortunately, I'm coming in on the tail end of the project and can't anticipate or implementing best practices for this rollout   but I'm trying to come up with a plan fwd with the cards I was dealt.      


0 Helpfuls

Uncle Rob
Kilo Patron
In response to terp

‎01-09-2018 04:02 PM

Any chance customer has a QA instance?   Meaning an instance that's NOT the test instance but also not Dev or Prod?


0 Helpfuls

Mike Allen
Mega Sage

‎01-09-2018 04:52 PM

We used merging pretty well at my old job.   We'd merge everything into a single set and didn't worry about the order because merging reconciles the records, keeping the latest change.   Especially if you have a large number of developers, it really helps.


0 Helpfuls