Best practice for installing plugins

[peterraeves]

My usual procedure when it comes to installing plugins, is:

1) Install on DEV

2) Check all skipped records in the upgrade logs and revert if needed into an update set

3) Set update set to TEST

4) Install on TEST

5) Check all skipped records in the upgrade logs and revert if needed into an update set

6) Merge both update sets and put them to PROD

7) Install on PROD

I made this procedure by myself, so it might not be perfect, so that's why I'm here. I noticed that despite reverting records, they still come up as skipped. Though when I click 'Resolve Conflicts', it states at the top 'There are no differences found'. So what's the deal here? I had it reverted before the install of the plugin (through the update set) and there are no differences, yet it still shows up as skipped... What's going on here? And how can I fix this? It's a waste of time to have to check the same records multiple times 😕

PS: So one of my uncertainties is whether I should set the update set before I do the install again or after?

[brian_degroot]

Hi Peter,

It's best to make separate requests for the plugin activations on each instance rather than trying to move the files via update set. There's several issues you might run into by doing it this way.

-Plugins can have certain dependencies on other plugin components that may not be present in the target instance.

-Plugins can create records on data tables which is not able to be captured in an update set.

-Plugin may not be flagged as 'active' on target instance, resulting in changes made to the associated application files not being loaded in subsequent upgrades.

It's best to have the plugin activated on both your source and target instance, and use update sets to push any development work your organization does afterwards between the two.

Best regards,

Brian

[peterraeves]

Yes of'course. That's what happens in steps 1, 4 and 7

[KKrabbenhoft]

@peterraeves  I too was looking for a best practice. I like your list and agree with @brian_degroot that the initial read implies you are updating in DEV and setting an update set to move from DEV to TEST. 

Steps 3 and 6. 

An update-set is not required before or after. 

---

[Lenny Williams]

This is great information on best practices. Does anyone have a document on it or even ServiceNow White page? We have started with possible ownership of plugins so SME of the plugin can test it and move to TEST, Then PROD. There are so many Plugins so organization in updating is key. We are also looking into testing when we upgrade to new version- Utah Etc., we are testing before upgrade. Thoughts on Best Practices via ServiceNow Docs.