Age | Commit message (Collapse) | Author | Files | Lines |
|
global-jjb only supports the .yaml file ending for jjb jobs. Instead of
waiting for a release we're going to rename the files.
Change-Id: Icf3339eacd2320c583333e02250998cf6b1881f7
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
I guess adding disabled true doesnt do anything.
Just going to neuter the job then..
Change-Id: Iff77f846b6c3eb15ea8c49cfa035449f7aaa1984
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Why is moon running against docs buids?
I don't know, but ts documentation release day.
Disabling moon
https://gerrit.opnfv.org/gerrit/#/c/45505/
Change-Id: Icb68bfc183347a98756f43073d6e5d9a0131144f
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Without a '|' after the shell builder declaration yamllint will think
the bash directive is a comment.
JIRA: RELENG-254
Change-Id: Ib4e9802dbceeac1356936510ffa2efeca648076d
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: Iff9bd7601a59d7e1bad259c74fc792081505f679
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
JIRA: RELENG-254
Change-Id: If7e19dfdaf3b9d5df79b4d22fd13578d64481cb1
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Previously, if an upstream patchset contained a change for a file
listed in 'forbidden-file-paths' the job would not be triggered. This
is not desirable since such a patchset may contain important changes so
we enable the 'disable-strict-forbidden-file-verification' option which
triggers the job unless the patchset only contains changes for the
files listed in 'forbidden-file-paths'.
Note: The diff was generated using the following script:
for i in $(grep -l -r forbidden-file-paths *);do sed -i "s/\(^.*\)forbidden-file-paths/\1disable-strict-forbidden-file-verification: \'true\'\n&/" $i; done
Please double check that the changes look sensible for each team's project.
Change-Id: Ifa86d3a39b36375b2fd52b449e29c8dc757499b4
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
GIT_BRANCH parameter is different; master or stable/danube in daily
jobs, but 'refs/changes/57/27657/6' in verify jobs. This breaks some
job builders triggered by the both types of jobs. We have GERRIT_BRANCH
parameter for verify jobs to identify stream and expected branch into
the patch will be merged after it got +2 and submitted.
To avoid further confusion and to have common job builders for daily
and verify jobs, this patch introduce BRANCH parameter.
GERRIT_BRANCH is now deprecated.
Change-Id: Ibcd42c1cd8a0be0f330878b21d3011f1ec97043b
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
This patch makes sure we use 2 types of scm, and allows us to specify
them by adding one line in job-templates.
- git-scm # for daily jobs and merge jobs
- git-scm-gerrit # for verify jobs [New]
Change-Id: Iddc8a5e0e115193c7081a6d6c53da209900e95c8
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
With the addition of ODL and OpenStack Gerrit servers, it's important we
don't generate additional noise by accidentally building against these
Gerrit servers when we don't intend to.
JIRA: RELENG-179
Change-Id: Ia163c6c3eaa58e8e21dc6548a839062fcbde39ed
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: If1a0e02b8eaba52b68501e6463b02b3a0547c2c9
Signed-off-by: WuKong <rebirthmonkey@gmail.com>
|
|
Change-Id: I72d21335f5cbff7dc630b1c2019bb7fa8b0d379f
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|