</tr>
<tr>
<td colspan="2">
- This job builds a distrbution against your patch, passes distribution sanity test
+ This job builds a distrbution against your patch, tiggers distribution sanity CSIT jobs
and reports back the results to Gerrit. Leave a comment with trigger keyword above
to activate it for a particular patch.
<p>
Running the "test-distribution" trigger will cause Jenkins to
remove it's existing vote if it's already -1 or +1'd a comment.
- You will need to re-run your verify job (recheck) after running
+ You will need to re-run your verify jobs (recheck) after running
this to get Jenkins to put back the correct vote.
</p>
</div>
</td>
</tr>
+ <tr class="warning">
+ <td><b>Job Template</b><br/>{project}-distribution-check-{stream}</td>
+ <td><b>Gerrit Trigger</b><br/>recheck | redistcheck</td>
+ </tr>
+ <tr>
+ <td colspan="2">
+ This job runs the PROJECT-distribution-check-BRANCH job which is
+ building also integration/distribution project in order to run SingleFeatureTest.
+
+ The <b>redistcheck</b> trigger is useful in cases where a project's
+ other jobs passed, however this job failed due to infra problems or
+ intermittent issues. It will retrigger just this job to save time.
+
+ BEWARE: If there were other failed jobs, redistcheck could lead
+ to false Verified+1 vote, risking a merge which breaks other projetcs.
+ Redistcheck is only for committers who are familiar with the risks involved.
+ If in doubt, use the safe trigger word: recheck.
+ Recheck triggers every job involved in verifying latest patch set in the Change.
+ </td>
+ </tr>
+
<tr class="warning">
<td><b>Job Template</b><br/>{project}-integration-{stream}</td>
<td></td>
</tr>
<tr>
<td colspan="2">
- The Merge job template is similar to the Verify Job Template except
- it will trigger once a Gerrit patch is merged into the repo. It
- also automatically runs the Maven goals <b>source:jar</b> and
- <b>javadoc:jar</b>.
-
- This job will upload artifacts to OpenDaylight's
+ This job will trigger once a Gerrit patch is merged into the repo.
+ It will build HEAD of the current project branch and also run the Maven goals
+ <b>source:jar</b> and <b>javadoc:jar</b>.
+ Artifacts are uploaded to OpenDaylight's
<a href="https://nexus.opendaylight.org">Nexus</a> on completion.
+
+ Running the "remerge" trigger is possible before a Change is merged,
+ in which case it will cause Jenkins to remove it's existing vote
+ if it's already -1 or +1'd a comment.
+ You will need to re-run your verify jobs (recheck) after running
+ this to get Jenkins to put back the correct vote.
</td>
</tr>
<tr class="warning">
<td><b>Job Template</b><br/>{project}-validate-autorelease-{stream}</td>
- <td><b>Gerrit Trigger</b><br/>recheck | reverify</td>
+ <td><b>Gerrit Trigger</b><br/>recheck | revalidate</td>
</tr>
<tr>
<td colspan="2">
features that do not exist in the current release.
The <b>revalidate</b> trigger is useful in cases where a project's
- verify job passed however validate failed due to infra problems or
- intermittent issues. It will retrigger just the validate-autorelease
- job.
+ other job passed, however this job failed due to infra problems or
+ intermittent issues. It will retrigger just this job to save time.
+
+ BEWARE: If there were other failed jobs, revalidate could lead
+ to false Verified+1 vote, risking a merge which breaks other projetcs.
+ Revalidate is only for committers who are familiar with the risks involved.
+ If in doubt, use the safe trigger word: recheck.
</td>
</tr>
</tr>
<tr>
<td colspan="2">
- The Verify job template creates a Gerrit Trigger job that will
- trigger when a new patch is submitted to Gerrit.
+ The Verify job template creates a Gerrit Trigger job that will
+ trigger when a new patch is submitted to Gerrit.
+ The job only builds the project code (including unit and integration tests).
+
+ The <b>reverify</b> trigger is useful in cases where a project's
+ other jobs passed however this job failed due to infra problems or
+ intermittent issues. It will retrigger just this job to save time.
+
+ BEWARE: If there were other failed jobs, reverify could lead
+ to false Verified+1 vote, risking a merge which breaks other projetcs.
+ Reverify is only for committers who are familiar with the risks involved.
+ If in doubt, use the safe trigger word: recheck.
+ Recheck triggers every job involved in verifying latest patch set in the Change.
</td>
</tr>
<tr class="warning">
<td><b>Job Template</b><br/>{project}-verify-node-{stream}</td>
- <td><b>Gerrit Trigger</b><br/>recheck | reverify</td>
+ <td><b>Gerrit Trigger</b><br/>recheck | renode</td>
</tr>
<tr>
<td colspan="2">
{nodever} containing the directory relative to the project root
containing the nodejs package.json and version of node you wish to
run tests with.
+
+ The <b>renode</b> trigger is useful in cases where a project's
+ other jobs passed, however this job failed due to infra problems or
+ intermittent issues. It will retrigger just this job to save time.
+
+ BEWARE: If there were other failed jobs, renode could lead
+ to false Verified+1 vote, risking a merge which breaks other projetcs.
+ Renode is only for committers who are familiar with the risks involved.
+ If in doubt, use the safe trigger word: recheck.
+ Recheck triggers every job involved in verifying latest patch set in the Change.
</td>
</tr>
<tr class="warning">
<td><b>Job Template</b><br/>{project}-verify-python-{stream} | {project}-verify-tox-{stream}</td>
- <td><b>Gerrit Trigger</b><br/>recheck | reverify</td>
+ <td><b>Gerrit Trigger</b><br/>recheck | retox</td>
</tr>
<tr>
<td colspan="2">
The 2 template names verify-python & verify-tox are identical and are
aliases to each other. This allows the project to use the naming that
is most reasonable for them.
+
+ The <b>retox</b> trigger is useful in cases where a project's
+ other verify jobs passed, however this job failed due to infra problems or
+ intermittent issues. It will retrigger just this job to save time.
+
+ BEWARE: If there were other failed jobs, retox could lead
+ to false Verified+1 vote, risking a merge which breaks other projetcs.
+ Retox is only for committers who are familiar with the risks involved.
+ If in doubt, use the safe trigger word: recheck.
+ Recheck triggers every job involved in verifying latest patch set in the Change.
</td>
</tr>
Code Review / releng / builder.git / commitdiff