[Lucene-java Wiki] Update of "JenkinsReleaseBuilds" by SteveRowe

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Lucene-java Wiki" for change notification.

The "JenkinsReleaseBuilds" page has been changed by SteveRowe:
https://wiki.apache.org/lucene-java/JenkinsReleaseBuilds?action=diff&rev1=10&rev2=11

Comment:
modernizify

  How to set up ASF Jenkins jobs to test a release branch.  In order to perform these steps, you need to have an ASF Jenkins admin account and be logged in.
  
   * Delete all old release branch jobs. (When there are multiple active release branches -- rare for Lucene/Solr -- be cautious about this.)
-  * For each non-Clover stable branch job (as of this writing, this is {{{Lucene-Artifacts-6.x}}}, {{{Lucene-Solr-Maven-6.x}}}, {{{Lucene-Solr-NightlyTests-6.x}}}, {{{Lucene-Solr-SmokeRelease-6.x}}}, {{{Lucene-Solr-Tests-6.x}}}, and {{{Solr-Artifacts-6.x}}} - see all Lucene/Solr jobs here: [[https://builds.apache.org/computer/lucene/]]):
+  * For each non-Clover stable branch job - see all Lucene/Solr jobs here: [[https://builds.apache.org/view/L/view/Lucene/]]
+    * as of this writing, the set of jobs to do the following for is:
+      * {{{Lucene-Artifacts-7.x}}}
+      * {{{Lucene-Solr-Maven-7.x}}}
+      * {{{Lucene-Solr-NightlyTests-7.x}}}
+      * {{{Lucene-Solr-SmokeRelease-7.x}}}
+      * {{{Lucene-Solr-Tests-7.x}}}
+      * {{{Solr-Artifacts-7.x}}}
+      * {{{Solr-reference-guide-7.x}}}
-    * Copy the job (Jenkins|New Item|Copy existing job), and name the new job by substituting the release version for the version in the copied job's name, e.g. s/6.x/6.0/.
+    * Copy the job (Jenkins|New Item|Copy existing job), and name the new job by substituting the release version for the version in the copied job's name, e.g. s/7.x/7.5/.
     * It's a good practice to create the job as initially disabled (check the checkbox next to "'''Disable Build (No new builds will be executed until the project is re-enabled.)'''"), and then enable them all at once after you've finished creating them.
-    * Switch the '''Branch Specifier''' under '''Branches to Build''' in the '''Source Code Management''' section to point to the release branch, e.g. {{{*/branch_6x}}} -> {{{*/branch_6_0}}}
+    * Switch the '''Branch Specifier''' under '''Branches to Build''' in the '''Source Code Management''' section to point to the release branch, e.g. {{{*/branch_7x}}} -> {{{*/branch_7_5}}}
     * All jobs are scheduled to run periodically.  No changes should be required on the cloned jobs to handle this properly.
   * If you created the new jobs in the disabled state, enable them all now.