lucene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Lucene-java Wiki] Update of "JenkinsReleaseBuilds" by SteveRowe
Date Wed, 30 Dec 2015 15:02:39 GMT
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:

New page:
= Jenkins Release Builds =

How to set up ASF Jenkins jobs to test a release branch.

* 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-5.x,
Lucene-Solr-Maven-5.x, Lucene-Solr-NightlyTests-5.x, Lucene-Solr-SmokeRelease-5.x, Lucene-Solr-Tests-5.x-Java7,
and Solr-Artifacts-5.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/5.x/5.4/.
** Switch the Repository URL in the Source Code Management section to point to the release
branch, e.g. s/branch_5x/lucene_solr_5_4/.
** If this job kicks off another job (look under Post-build Actions|Build other projects),
make sure you rename the job to kick off (Projects to build) by substituting the release version
for the version in the job's name, e.g. s/5.x/5.4/.  Currently, Lucene-Solr-NightlyTests-<version>
kicks off Lucene-Artifacts-<version>, and Lucene-Artifacts-<version> kicks off
** Except for the jobs triggered by other jobs, (see above), all jobs are scheduled to run
periodically.  No changes should be required on the cloned jobs to handle this properly.

View raw message