Update set best practice - general question

Dubz · ‎10-13-2017

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!

Aakash Shah4 · ‎10-13-2017

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/

View solution in original post

Community Alums · ‎04-20-2023

You can reopen your Update Safely using this Utility:
https://developer.servicenow.com/connect.do#!/share/contents/3673648_copy_update_set?v=1&t=PRODUCT_D...