doc: add note about non-pipeline jobs to jenkins upgrade guide (adopt…

…ium#3699)

Signed-off-by: Stewart X Addison <[email protected]>

README.md

@@ -111,17 +111,19 @@ to do an out-of-bound patch if a sufficientl sever issue is identified.
 ### Jenkins
 
 1. Ensure off-machine backups are working!
-2. Check for plugin updates that will apply to the current version of
+1. Ensure that no non-pipeline jobs are running on the server as they
+ will often hold up restarts
+1. Check for plugin updates that will apply to the current version of
  jenkins (Each plugin should be checked for potential issues in the readme)
-3. Repeat step 1 if necessary until jenkins does not offer any more plugins
-4. Identify new LTS level - check [the release notes](https://www.jenkins.io/doc/upgrade-guide/)
+1. Repeat step 1 if necessary until jenkins does not offer any more plugins
+1. Identify new LTS level - check [the release notes](https://www.jenkins.io/doc/upgrade-guide/)
  to identify any potential problems. Allow jenkins to upgrade itself
-5. Redo step 1/2 so that any plugins that were unable to be updated due to
+1. Redo step 1/2 so that any plugins that were unable to be updated due to
  the older jenkins level can update themselves.
-6. If necessary, and the remediation cannot be performed within the
+1. If necessary, and the remediation cannot be performed within the
  maintenance window, identify potentially risky plugins that were held
  back and create an issue to deal with them in the next cycle.
-7. Backup the main war in /usr/share/jenkins to a name with a version suffix
+1. Backup the main war in /usr/share/jenkins to a name with a version suffix
  in case of corruption to the main jar.
 
 ### Backups