question Upgrade Best Practices - Reverting Skipped Files in Upgrades and Patching forum

Upgrade Best Practices - Reverting Skipped Files

Tyson3 — Fri, 03 Jun 2022 17:13:32 GMT

Hi,

I'm looking for some quick best practice guidance on the upgrade from Quebec to San Diego which we are currently working on. We have two sub instances ("Dev" and "Test") which we have already upgraded to San Diego. We are planning on upgrading our production instance to San Diego in July.

We are currently reviewing skipped files in our lowest instance "Dev" and are wondering about the best practice way to handle "Reverting to Base System" option. If we choose to revert a business rule for example, this change is tracked via an update set and then we can move the update set to the next sub environment "Test". Should this update set be moved before or after we have upgrade our next instance?

I have read some community posts with mixed signals with some saying you should move the update set to the next instance, and then upgrade. Other ones say you should upgrade and then move the update set.

Our assumption is the best practice is to track the skipped file in an update set first in your lowest environment and then move this update set to the next environments after it's already been upgraded.

Any clarification on this would be much helpful. Thanks!

Re: Upgrade Best Practices - Reverting Skipped Files

Allen Andreas — Fri, 03 Jun 2022 17:16:35 GMT

Hi,

The update is moved AFTER the upgrade is done.

So essentially, only Dev would have been upgraded (this is so multiple environments aren't misaligned with the version and allows you to work on the fixes in the lowest environment first).

I wouldn't have had both Dev and Test upgraded and Test just sitting there while you all are working through your changes in Dev.

Only Dev should have been upgraded, you work through skipped changes, verify ATF and application functionality, full regression, etc.

Then, once everything appears good to go, Test is upgraded and right after that update set is moved from Dev to Test and committed. Then double-check things again in Test, you wouldn't work through the skipped changes all over again, as you've already done that in Dev.

Once Test is good, if anything is caught there, return to Dev, fix it, if applicable, make a second update set for those things, and then upgrade Prod, this time promote your main skipped changes fix AND the other update set (if applicable), and this time, lightly check things in Prod as best you can.

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

Re: Upgrade Best Practices - Reverting Skipped Files

Terri Kouba — Fri, 03 Jun 2022 19:00:03 GMT

UC Berkeley Telecom Catalog instance does it in a similar way as expressed by Allen. Note: We have another instance which has a different process.

we have 3 instances: dev, test, prod
Run pre-clone ATFs in dev and test
clone dev and test at the same time. Do post-clone activities
run post-clone ATFs in dev and test
upgrade dev
in dev, do skip/revert/merges (some of which go into an update set)
in dev, run post-upgrade ATFs
in dev, validate system, post-upgrade
in dev, export skip/revert decisions, close update set
upgrade test
in test, apply dev skip/revert decisions
in test, apply post-upgrade update set
in test, handle any extra skip/reverts
in test, run post-upgrade ATFs
in test, validate system
in test, export skip/revert decisions
upgrade prod
in prod, apply test skip/revert decisions
in prod, apply post-upgrade update set
in prod, handle any extra skip/reverts
in prod, non-invasive smoke-test to validate system

If you have any questions, please don't hesitate to ask.

Thanks,

Terri

---

Terri Kouba, ESM Service Manager
University of California, Berkeley
Berkeley Information Technology | Enterprise Service Management
Email: kouba@berkeley.edu
We champion diversity. We act with integrity. We deliver. We innovate.

Re: Upgrade Best Practices - Reverting Skipped Files

Allen Andreas — Mon, 13 Jun 2022 22:17:52 GMT

Hi Tyson,

Just wanted to check-in and see how you're doing.

If my reply above helped guide you Correctly, please also mark as Correct.

Thanks and take care! 🙂

Re: Upgrade Best Practices - Reverting Skipped Files

cliff11 — Tue, 15 Nov 2022 16:50:49 GMT

Hi Terri - thanks for sharing this. I can't seem to wrap my head around how applying the update set with the Replace on Upgrade after the prod upgrade helps. Shouldn't these be set first, so that the upgrade replaces them with current and then gets them off the future Skip list.

Thoughts?

Re: Upgrade Best Practices - Reverting Skipped Files

Terri Kouba — Mon, 21 Nov 2022 20:18:01 GMT

Hi Cliff11,

We haven't tried applying the update set to production BEFORE the upgrade in production. In our upgrade update set, we often have 'reverts' and 'merges' in the same update set, and the latter definitely need to be done after the upgrade because the new code this is in the merge is provided during the upgrade.

I think of it as when I'm painting a wall. The big brush is the upgrade and allows you to apply a wide swath of changes (or paint a wide swath of a wall a new color). The post-upgrade update set is a tiny touch-up brush that includes only a few tweaks (or a thin brush to do touch-up work on the wall).

I hope that helps.

Thanks,

Terri