Age | Commit message (Collapse) | Author | Files | Lines |
|
GERRIT_REFSPEC is always passed by the gerrit-trigger plugin when a job
is triggered by Gerrit. Because it is not explicily defined, there is no
way to manually trigger jobs, as the git clone looks up the list of refs
by GERRIT_REFSPEC.
Being able to manually trigger jobs (with node parameters so they can be
restricted) is very helpful in debugging CI issues.
Change-Id: I8a1d9ea380902fc95f30482e5acb616347709ab1
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
This value is usually passed by parent jobs (daily, verify, etc), but
exposing it as parameter should allow us to build from JJB GUI.
Change-Id: I294fbcd200ff5d8bbfca77681296c6e59d7f0063
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
We dont have other pods so no reason to make extra labels
Change-Id: Ib701ae25d6cd08035930773219f691c7dc1b156e
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I2f6dbe545c1c1adaa0a7020440f17f6f0cf37973
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Since these jobs don't deal with scenarios they can safely be moved to
another file without the need to duplicate the scenario listings.
Fixes a bug with 'concurrent-builds' not being set due to missing
quotation marks.
JIRA: RELENG-287
Change-Id: Icce39620521c7d25476553115efbaa9063ca2e17
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|