summaryrefslogtreecommitdiffstats
path: root/jjb/fuel/fuel-verify-jobs.yml
AgeCommit message (Collapse)AuthorFilesLines
2017-03-15jjb: Set disable-strict-forbidden-file-verification to 'true'Markos Chandras1-0/+1
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>
2017-03-14Enable Danube JobsAric Gardner1-1/+1
Here are the projects that were branched: I will double check against this list that these changes make sense and that no one is missing as I go forward. wiki page of participating projects, and their jobs: https://wiki.opnfv.org/display/SWREL/Milestone+Compliance+for+Danube apex - already enabled armband - done availability - already enabled barometer - done bottlenecks - already enabled compass4nfv - done copper - already enabled daisy - (not participating -- keep jobs disabled?) doctor - already enabled domino - already enabled fds - N/A fuel - done functest - already enabled ipv6 - already enabled joid - done kvmfornfv - already enabled models - already enabled multisite - done netready - NOT DONE opera - NOT DONE opnfvdocs - done orchestra - Not participating onosfw - done ovsnfv - done parser - N/A promise - already enabled qtip - already enabled sdnvpn - N/A snaps - done securityscanning - N/A sfc - N/A storperf - done ves - already enabled vswitchperf - already enabled yardstick - already enabled Change-Id: I803662faf05c8554cfe7fa5f85da9521f72b03ff Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
2017-02-01merge GIT_BRANCH and GERRIT_BRANCH into BRANCHRyota MIBU1-6/+4
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>
2017-01-20[macro] property logrotateRyota MIBU1-0/+2
This patch defines 'logrotate-default' property and replace 'logrotate' by it, as 'logrotate' is deprecated on jenkins>=1.637 . Change-Id: I900975e5b3f590bb7a4d430e2f623931ae782bf4 Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
2017-01-19fuel: Remove colorado jobs and create danube jobsFatih Degirmenci1-2/+2
Obsolete plugin jobs and scripts are also removed. Change-Id: I16f8d932a492fdd1d8eb2caa5f8bc4aa9183327b Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-12-27fuel: Move fuel-verify jobs to ubuntu build serversFatih Degirmenci1-4/+4
lf-build1 is experiencing issues. Change-Id: I2253765d9db2e4603b776bbf5841f61da1bb89fe Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-12-19clean scm defenitionsRyota MIBU1-14/+4
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>
2016-12-01Restrict Gerrit Triggers to OPNFV Gerrit ServerTrevor Bramwell1-0/+1
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>
2016-08-24fuel: Rearrange slave assignments for verify jobsFatih Degirmenci1-13/+6
Change-Id: Iaf83ba8bc96189e9ef7749bd367197857c3e656a Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-08-23fuel: Create jobs for ColoradoFatih Degirmenci1-1/+1
This change contains updates that impact compass and joid jobs due to updates in functest and yardstick that remove brahmaputra branch. Please note that the triggers for colorado haven't been created yet. It will be done once the basics in place. Change-Id: Id5eb8c406d34ff9f3ac59f73243034cbf49b23f0 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-07-20fuel: Adjust build throttlingFatih Degirmenci1-2/+1
Change-Id: I4eab4e87e145881912fcc5570cbb04606f0514fb Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-07-19fuel: Fix jjb escapingFatih Degirmenci1-2/+2
Change-Id: I5cc33f949b7db0c17b92a01777cb57b16a05b637 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-07-18fuel: Update verify jobs and introduce Multijob and verify phasesFatih Degirmenci1-0/+273
This is the first step towards improved Commit Gating and this change does not impact the current way of working for Fuel. This means that no additional verification activities will be done for changes/patches coming to Gerrit for Fuel as of yet and only builds will be used for patchset verification Because of this, the new execute shells contain nothing but simple echos. Functest job hasn't been created/connected either since we don't do full commit verification. This change - switches verify job to Multijob project type since Freestyle does not support aborting all the downstream jobs when a new patch for same change comes to Gerrit for existing change. When Gerrit Trigger aborts the upstream verify job that was triggered for the previous patch of the same change, Multijob then aborts the downstream phase jobs, not leaving orphaned phase jobs behind. - creates phase jobs to do limited verification activities in order to provide more granular feedback. Earlier phases fail the patch verification in order to provide feedback for the failed phase rather than whole basic, deploy, and smoke test. Change-Id: I053db2a54020139d57d74d254a25ed0480767267 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>