Upgrade Plan with plugins - how to identify skipped records from plugins on the Builder Instance?

Kristin J
Mega Sage

Tuesday

Hello! I consistently use upgrade plan both for family releases as well as patching. It has been an efficient way to manage plugin updates because I install them once on the builder instance after I apply the patch, then I use upgrade plan for the other instances to catch everything up.

 

However, the gap I have is with the builder instance. How do I manage records that were "invisibly" skipped when I installed the plugins individually? The scenario is:

  • Cloned all subprod instances.
  • Upgraded builder instance to Patch X. Say there are 10 skipped records.
  • Updated plugins on builder instance
  • Built plan and install/upgrade with other subprod instances
  • Now there are 25 skipped records on the instances that consumed the upgrade plan, because the upgrade process evaluates the plugin records as well.

I realise this has been happening forever, because before upgrade plan I used to put in plugins and just move on with testing. But now that I've noticed it, I am wondering if I've been doing something "wrong" all this time, or if I need to do something differently. Is this a rare case where I am resolving skipped records and moving an update set backwards in my instance order!?

I'd love to hear other people's practices here. 🙂
Cheers,

Kristin

0 Helpfuls
  • 283 Views
1 REPLY 1

ifti122
Giga Guru

Wednesday

Hi @Kristin J , 

 

The "invisibly" skipped records are still recorded in your sys_upgrade_history on the builder instance. The "invisibility" likely refers to the fact that their resolution isn't captured in an easily exportable update set that the Upgrade Plan can automatically leverage for other instances, unlike instance-level skipped records. You still need to manually review and resolve these on your builder instance to achieve your desired state.


Here's a brief solution or best practice you can say:

  • Builder Instance First & Completely upgrade your builder instance to Patch X.
  • Resolve all skipped records from the patch.
  • Install/Update all necessary plugins.
  • Resolve all skipped records generated by these plugin updates.
  • Ensure your builder is in its final desired state with all skips resolved.
  • Only after all skipped records (from both instance and plugin upgrades) are resolved on the builder, then create your Upgrade Plan.
  • Use Upgrade Preview on consumer instances before applying the plan.
  • Be prepared to manually review/resolve any remaining plugin-specific skipped records on consumer instances, as the plan's automation is primarily for instance-level skips.

Regards, 
Muhammad Iftikhar