summaryrefslogtreecommitdiffstats
path: root/jjb/xci/xci-merge-jobs.yml
AgeCommit message (Collapse)AuthorFilesLines
2018-05-16Rename files under jjb from 'yml' to 'yaml'Trevor Bramwell1-470/+0
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>
2018-05-11jjb: xci: Connect new releng-xci-scenarios repositoryMarkos Chandras1-1/+1
The scenarios have been moved from the releng-xci to releng-xci-scenarios repository so we should connect Jenkins to that repo as well. Change-Id: Ifcb4f02b8532dd94c8a622185328f7316e726c6b Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-22xci: Do not trigger merge jobs for INFO.yaml updatesFatih Degirmenci1-0/+2
Change-Id: I16eed2ec0ca1fa659fc449799813c02b19b08174 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-21xci: Disable merge jobs on centos until centos is fixed properlyFatih Degirmenci1-3/+4
Change-Id: Ieab479d257fb1922136eb343d1dd25f2006c2ac2 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-21xci: Make centos jobs non-voting for promotionFatih Degirmenci1-4/+10
Change-Id: I981b115bc37f034db991667a29f0ce66b239cbdf Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-20xci: Set CI_LOOP, FUNCTEST_MODE, and FUNCTEST_SUITE_NAME in jobsFatih Degirmenci1-2/+45
These variables are needed for displaying details of functest run. Apart from that and more importantly, FUNCTEST_SUITE_NAME will be important for adjusting the criteria for verifying and promoting scenarios. Change-Id: I7a3c82c6babc4d5e057b26fda697e9fc969c8526 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-20Merge "xci: Enable post merge promotion for generic scenarios"Fatih Degirmenci1-0/+15
2018-03-19xci: Make centos job non-voting for promotionFatih Degirmenci1-2/+2
verify-centos jobs do not vote for patch verification since things on centos are still shaky. Make merge-centos jobs non-voting for promotion as well by not allowing them to fail the entire promotion job or by stopping the promotion. Change-Id: Idf7b3c7586d94454ff94cd0bccf42f02954c722c Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-19xci: Enable post merge promotion for generic scenariosFatih Degirmenci1-0/+15
Change-Id: Iacbd6515de08e77e3874354fc8e23a6cf8f7bf61 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-19Merge "xci: Enable deployment and testing for post merge jobs"Fatih Degirmenci1-6/+7
2018-03-19xci: Fix envInject and remove scenario distro support checkFatih Degirmenci1-1/+1
envInject doesn't play well with variable expansion so it is fixed. [1] Scenario support check is not necessary for promotion since the promotion job is common for all scenarios/distros and check is done as part of earlier distro jobs accordingly. [2] gsutil upload is also made quiet. Fixed version can be seen from [3]. [1] https://build.opnfv.org/ci/job/xci-merge-promote-virtual-master/2/console [2] https://build.opnfv.org/ci/job/xci-merge-promote-virtual-master/4/console [3] https://build.opnfv.org/ci/job/xci-merge-promote-virtual-master/5/console Change-Id: Ie36394cab631826209dda4cea6daa456aca3c276 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-19xci: Enable deployment and testing for post merge jobsFatih Degirmenci1-6/+7
Change-Id: I61fdcf11cc8008bde1c4e26e7b4fd6f16b6e5a78 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-19xci: Store the metadata for promoted scenarioFatih Degirmenci1-8/+13
Change-Id: I1048be7e7a41c56d25c7689678d3811f0a5eae44 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-19xci: Make post merge job common across all scenariosFatih Degirmenci1-29/+20
It is difficuly to have post-merge jobs per scenario since we set the scenario during job runtime and having jobs per scenario makes things unnecessarily complicated. Apart from that, there is no reason to have scenario specific merge jobs either since this is some kind of verify job and everything is same except the scenario name itself which we extract via set-scenario script. Daily and further jobs will be scenario specific since they will be run on timer and we will have ability to specify the scenario. Change-Id: I3bf6d5ce0fbc48b2d2b2b9695e198bad229ce08d Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-14xci: Create post merge jobs to promote scenariosFatih Degirmenci1-68/+205
This change lays down the basic job structure for post merge promotion jobs. The job structure will be - a top level multijob job that is scenario specific and can not run concurrently. This job runs distro deploy and test jobs for all the distros in the first phase concurrently, followed by a common promote job. - the deploy and test jobs are same as the xci-verify jobs except the trigger. They are triggered by top level multijob. - the promote job is run once all the deploy & test phase jobs successfully completed, uploading promotion metadata to artifacts.opnfv.org. The builders except set-scenario are left empty in order to try the basic job setup first. Followup changes will get real things in. Once the basics are in place, the first promotion will be done using functest healthcheck and then we will start working on gating scenarios for promotion using functest smoke and perhaps feature test cases. Change-Id: Ib91ffe0f3003b86841a62537c52fde176cafa70f Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-12jjb: xci: Drop the VM cleanup step from the functest jobsMarkos Chandras1-2/+0
We do the VM cleanup as part of the postbuild process so we do not need to have it in the functest jobs anymore. Change-Id: I64e4b58837090df33ae529232ef15a19de8f198a Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-07jjb: xci: Add postbuild publisher script to remove clean VMMarkos Chandras1-0/+8
The clean VM normally stays around after the job is completed or killed due to timeout. Unless a job for the same distro is scheduled on the same node, that VM will state around for a while consuming valuable system resources. As such, we should remove it after the job finishes to free up resources for the new jobs. Change-Id: I88b5e32797969d9378588199a7ddb013bbe740c9 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-02-21jjb: xci: Fix bifrost blockers for XCI jobsMarkos Chandras1-3/+2
The bifrost regexp was wrong leading to conflicts betwen the XCI and bifrost jobs. Moreover, we need to add the same restrictions for jobs/node on bifrost jobs similar to the XCI ones. This finally fixes the 'throttle' property to use the 'xci-verify-virtual' category. Change-Id: I6d3f8fdd82738c1d079b1a3fdef134753eb4281a Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-02-15jjb: xci: Add missing job blockers for XCI merge jobsMarkos Chandras1-0/+7
We shouldn't allow the merge jobs to run in parallel with the verify ones when both are testing the same distro since one may wipe the 'clean VM' of the other one. Moreover, we should restrict the number of jobs allocated on nodes in order to avoid overloading them. Change-Id: I9c0b9b5061e41b21c01789fc4676e72e0e082f17 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-01-22xci: Clone releng-xci repo for phase jobs as wellFatih Degirmenci1-1/+6
Forgotten to fix phase jobs. Change-Id: I50c525089d6d3b4f28650ad78b8810817aaf150e Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-01-22xci: Clone the repo and checkout the patch for testingFatih Degirmenci1-0/+3
Change-Id: Ie1c2f76b6043133c3821272040b1a2a38de29035 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-01-22xci: Always clone releng-xci into WORKSPACE for merge jobsFatih Degirmenci1-1/+6
The cloning of the correct version of the repo which the scenario resides in will be handled by get-opnfv-scenario-requirements.yml for all the scenarios. The change proposed for merge jobs will be reflected to verify jobs as well once it is verified with this. Change-Id: Icaa99a8b9e981c839969ce556e5af6a9ef6d9da8 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-01-22xci sfc: Enable post merge deploymentFatih Degirmenci1-19/+11
This change enables the deployment upon merge of a change. Followup patches will incorporate functest smoke and promotion which the promotion will most likely be the first one as functest parts are a bit tricky due to failures while running testing in VMs. Apart from the enablement of the deployments, job concurrency is disabled as well since we should only test one change at a time and attempt promotion for any scenario in order to ensure we keep the promotion consistent. Change-Id: Ib4b5754b6b88f42eab83c656e03773c83068016f Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-01-10RFC: Set the basic structure for post merge jobsFatih Degirmenci1-0/+252
This change proposes structure for post-merge jobs for the scenarios that are onboarded to XCI. The idea with these jobs is to verify the sanity of impacted scenario to find out if the version that is tested should be promoted to the next level in XCI; daily on baremetal. If it succeeds, the metadata regarding the scenario needs to be stored somewhere (artifact repo, etc.) so daily jobs can poll that location to see if there is any scenario that is worth testing on baremetal. If it fails, the scenario could be demoted instead which still requires further discussion and thinking. We might perhaps leave the metadata of the version of the scenario with previous sha as the candidate for testing instead of demoting it since we need to have working version of the scenarios at all times. Change-Id: I85d7176b16d0d6da45cd2462b0cdb990485b6b0d Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>