Update set best practice - general question

[Dubz]

Hi All,

Just a general question on how best to move update sets from dev to prod:

I have dev, test and prod instances. i think the best way to move update sets is to move from dev to test and then move the set from test on to prod. This way each instance only interacts with only one other.

Is this the best way? What is the best process to follow if my move to test reveals issues and i need to go back to dev to add config? Do i reopen the update set on dev or work on the set on test? If i reopen on dev the set can't be moved again to test as it has already been committed there, do i need to roll it back on test?

It's a procedural point but i want to avoid bad habits!

[raves12]

This is what I do:

1. Create the update set in dev and do my configuration changes and after final testing from my side move it to test for others to test.

2. If any issues persists, create a new update set name it "Part-2" make all you changes and again move it to test.

PS: It is not recommended to open a closed update set(not under Service Now best Practices).

From my side:

Always follow dev-->test--> prod when you will retrieve update sets in prod both from dev and test after previewing one you will get a lot of warnings with "Found an update in other uncommitted update". Avoid this.

[Aakash Shah4 · Accepted solution]

Hi David,

Never open a completed update set.

Once the update set is commited it should never be changed.

If you have deployed the change on TEST and you need to make change again, i would recommend to create a new update set in DEV name it patch 1 or v_1.

Make the necessary change in the update set and then close it and the again deploy it on TEST.

Now when you want t deploy this on PROD deploy them in order

1. first update set

2. patch 1

3. patch 2... and so on.

Additionally Check these links

Discussion - Update sets - Some useful tips and best practices

Update Sets Super Guide — ServiceNow Elite

http://www.snc-blog.com/2011/04/06/update-set-deployment-best-practices/

[Dubz]

Thanks for your input guys. I definitely need to stop being so lazy and opening new update sets rather than reopening completed ones

[Harish KM]

You always create a new update set in DEV and move it to QA. No matter how many times the test fails. do the same