summaryrefslogtreecommitdiffstats
path: root/jjb/xci/xci-verify-jobs.yml
AgeCommit message (Collapse)AuthorFilesLines
2018-05-16Rename files under jjb from 'yml' to 'yaml'Trevor Bramwell1-303/+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-20xci: Set CI_LOOP, FUNCTEST_MODE, and FUNCTEST_SUITE_NAME in jobsFatih Degirmenci1-2/+16
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-15xci: Skip the deployment for upstream and prototype changesFatih Degirmenci1-0/+4
Changes coming to these do not impact the framework so there is no need to run full verification for these. Change-Id: Ia9f8f4772a94cb0761c49ff27933798265831fa4 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-15xci: Do not run deployment for doc updatesFatih Degirmenci1-0/+2
Change-Id: Ic914bc5bf11e2246f214990353c804688d6e43d9 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-14xci: Create post merge jobs to promote scenariosFatih Degirmenci1-1/+1
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-12xci: Set installer type for the tested scenarioFatih Degirmenci1-3/+0
Variables injected by envInject are set after the job variables which results in not setting the variable correctly. The Jenkins test script now uses the variable injected by envInject to set the INSTALLER_TYPE to XCI_INSTALLER. Change-Id: Id79281a2ee22d407ffb1bd7c4be1471f6f329803 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-12xci: Set the installer and move scenario extraction into functionsFatih Degirmenci1-1/+1
The scenarios named os-* are deployed by osa and the ones named k8-* are deployed by kubespray. This change determines the installer to use by looking into the scenario name. The installers are currently hardcoded within xci-set-scenario.sh script and this needs to be fixed for other installers when they onboard to xci. Apart from setting the installer, extraction of generic and external scenarios are moved into corresponding functions. Change-Id: I19882bcd2a1260765e601ecbe517551c60401d74 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/+9
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-26xci: Enable functest healthcheckFatih Degirmenci1-0/+2
Change-Id: I261bfafefcd1fb5dcfead20697759e46d3556b46 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-02-26xci: Correct the gerrit project name for sdnvpnFatih Degirmenci1-1/+1
Change-Id: Ied1014546f6bd4d80896f29f86374a2865f95dca Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-02-26xci: Do not set DEPLOY_SCENARIO manuallyFatih Degirmenci1-3/+0
Change-Id: Iccd7ef674c9b80daba511f45cc48f403ca0f3e0b Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-02-26xci: Fix the Gerrit Trigger clone issue for external scenariosFatih Degirmenci1-8/+8
When a patch comes in for an external scenario, Gerrit Trigger injects refs for that patch for the corresponding project. With the previous configuration, job attempts to get that patch for releng-xci instead of the actual project. But switching to the right project causes Jenkins jobs to fail since the releng-xci will not be checked out to WORKSPACE. This change makes the clone for the repo/patch work and then it wipes out the WORKSPACE and clones releng-xci there to get the actual script parts to work. Change-Id: Ide31c21a209dff953118f51e9b09de1d206a3085 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-02-26xci: Fix extracting scenarios for generic scenariosFatih Degirmenci1-2/+5
Change-Id: Ib58ff1a8b093af550f86d337327114df50da4ae7 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-02-26xci: Change project name matching to REG_EXPFatih Degirmenci1-1/+1
Change-Id: Ic706c120ac879741d5562427a6c3e90162223762 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-02-26Merge "Enable verify jobs for external scenarios"Fatih Degirmenci1-5/+25
2018-02-21jjb: xci: Fix bifrost blockers for XCI jobsMarkos Chandras1-2/+1
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/+1
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-02-15Enable verify jobs for external scenariosFatih Degirmenci1-5/+25
This change extracts the scenario that is impacted by the patch which triggered the verify jobs and saves the scenario name into java properties file. This file will then be used by envInject plugin to inject the scenario name into the build environment. If the triggering change impacts multiple scenarios, the build will result in failure and the developer will be informed about a possible way to rectify the issue. Support for generic scenarios will be introduced in subsequent changes. Change-Id: I6406299c1352b6e9b8a9297c5441adf03445be33 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-02-06xci: Disable voting for CentOS jobsFatih Degirmenci1-4/+4
CentOS jobs started failing which requires troubleshooting. In order not to block things, the voting is disabled for CentOS jobs. Change-Id: Idc14b00cf09f0ee75bac17e993dc9f7724a1ad88 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-02-01xci: Enable voting for CentOS jobsFatih Degirmenci1-4/+4
CentOS is now supported by os-nosdn-nofeature scenario and it is time to enable voting for it. For scenarios that do not support CentOS yet, the jobs will skip running real stuff by exit 0 in order not to fail the patch. Change-Id: I86c9e1bb4d66ea84ccfc864186a7ca7c696f8663 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-01-25xci: Run functest as part of xci-merge jobsFatih Degirmenci1-2/+0
This is yet another messy work to get functest run for xci as part of merge jobs. The script is removed from xci-verify jobs in order not to block patches by -1ing them. Change-Id: I57254bcfbada7a51da89aba0e7a88f907eb9a525 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-01-22xci: Convert execute shell scripts to external scriptsFatih Degirmenci1-77/+8
The scripts used by verify jobs to create VMs, start deployments, run functest, and do cleanup for CI can be reused by other jobs as well so they are moved out of the yaml file. Apart from that, if we decide to change the way we run CI (not using VMs for performance reasons), we don't have to make big changes to yaml either. Change-Id: I2df1f2d60f999bcd7d53a5cd879112a5b2b0ca05 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2017-12-21xci: Create periodic jobs for upstream osaFatih Degirmenci1-2/+2
This change takes xci-verify-jobs as base and adjusts osa-periodic jobs to ensure they do what they are supposed to. The structure of periodic jobs is pretty similar to xci-verify-jobs and the differences comparing to them are - OPENSTACK_OSA_VERSION is set to master. - SCM type changed to git-scm from gerrit - Voting is removed. - Triggering will be done using pollscm to ensure we only run jobs when something changes upstream. Triggers are not enabled yet until the basics are verified working. This change requires https://gerrit.opnfv.org/gerrit/#/c/49275/ in order for periodic jobs to work as expected. Further changes are needed to finalize the structure. Change-Id: I8f6519ccce93e6b8b65509638294419459fd36e8 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2017-12-20Merge "jjb: xci: xci-verify-jobs: Do not trigger on forbidden paths"Aric Gardner1-9/+1
2017-12-20xci-verify: Remove flavor from the scenario nameFatih Degirmenci1-3/+3
Change-Id: Ief47cd60d45f2cc35c74a9e8430d6602210bbba1 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2017-12-19jjb: xci: xci-verify-jobs: Do not trigger on forbidden pathsMarkos Chandras1-9/+1
We should set 'disable-strict-forbidden-file-verification' to 'false' to really prevent any changes to the forbidden paths to trigger a CI job. When this option is set to 'True', then a patchset that modifies both allowed and forbidden paths will trigger a job. However, in order to be on the same side in regards to the start-new-vm.sh script, we really shouldn't trigger the job. Moreover, we drop the rest of the forbidden paths since we can use the 'skip-verify' topic name to skip the deployment. Change-Id: I2a89e51861c7fb8541fe774b128ea4049e91df43 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-12-15jjb: xci: Do not trigger the CI when patchset modifies the CI VMMarkos Chandras1-5/+2
The scripts in xci/scripts/vm are used to manage the VM on the CI so we shouldn't blindly test a patch that modifies them. It's better to use manual inspection since that script rarely changes anyway. Change-Id: I48d81f984a1a8d1500be2cc74ea79420962b9a15 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-12-15xci: Use custom-url for readable CI reportsMarkos Chandras1-0/+1
Change-Id: I97d8fac47ec25414045a7761b651019f9f89224f Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-11-30jjb: xci: xci-verify-jobs: Fix block on bifrost jobsMarkos Chandras1-2/+2
The bifrost jobs are normally named 'openstack-bifrost-...' so fix the regexp to look for proper bifrost job patterns. Change-Id: Ie1823e942a201485aa5fbad4bde27653823d849b Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-11-28Revert "jjb: xci: xci-verify-jobs: Enable tempest for XCI"Markos Chandras1-1/+0
This reverts commit 130a166b57d708cadba8a5917eadf0025fc17c6b. It was very optimistic to enable tempest in the CI jobs so disable it until we understand the problems. They are most likely related to limited HW resources but we need to confirm that. Change-Id: Id9ff9a4ca047140341c98411c0c57243d47001a9 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-11-23jjb: xci: xci-verify-jobs: Enable tempest for XCIMarkos Chandras1-0/+1
Set RUN_TEMPEST=true so we can tempest when running XCI CI jobs. Change-Id: I3f7617e20dc4f4c1ba9a1e9016eef125c924e7b7 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-10-10Merge "jjb: xci: Make use of alternative ssh configuration file"Markos Chandras1-1/+1
2017-10-07jjb: xci: xci-verify-jobs: Fix regexp for GERRIT_TOPICMarkos Chandras1-2/+2
Drop the single quotes to regexp works as expected. Change-Id: I2ea09be14bc83effdd5860fd35dda540b412cf59 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-10-06jjb: xci: xci-verify-jobs: Skip complete XCI deployments for 'skip-deloyment'Markos Chandras1-2/+2
When we want to test patches affecting the start-new-vm.sh script, sometimes we only want to test whether VM is operational without having to run the entire XCI deployment on it. As such, skip XCI deployments when the topic matches the 'skip-deployment' regexp. Change-Id: I4242ac09a9e65c939a06ad47eb26a62af39128c8 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-10-06jjb: xci: Make use of alternative ssh configuration fileMarkos Chandras1-1/+1
The script now creates an XCI specific ssh configuration file so we need to use that when trying to connect to the host. Change-Id: I34cb39636b95de9ab97cb5d2ca250b4218e9a7f7 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-10-05jjb: xci: xci-verify-jobs: Export clean vm variables properlyMarkos Chandras1-2/+3
The variables are meant to be used by the start-vm-new.sh script instead of the XCI test so they need to be exported properly before we run the script. Change-Id: I224ec7bfced5eb51f01de46bd042274bcf3ec86b Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-10-04jjb: xci: Use pre-built dib images for CI runsMarkos Chandras1-0/+2
We make use of the pre-built dib images hosted on artifacts.opnfv.org instead of building a new one on every CI build. This makes the CI jobs somewhat faster since we start with the XCI deployment straight away This patchset depends on https://gerrit.opnfv.org/gerrit/#/c/44049/ Signed-off-by: Markos Chandras <mchandras@suse.de> Change-Id: Id2ccee8882cd20590a4cd27d4e512dc414d7b40e
2017-10-03Fix Yamllint violations for jjb/xciTrevor Bramwell1-265/+266
JIRA: RELENG-254 Change-Id: Iaf58cc822eb616711c0dc081f5b0154fe881646c Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2017-09-28jjb: xci: Make SUSE a voting jobMarkos Chandras1-4/+4
XCI CI now works for SUSE distributions so allow job to vote. Change-Id: I2c8bf8394a2fb1c1008f470486280a0e30922e28 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-09-27xci: Switch to multijob for verify jobsFatih Degirmenci1-36/+40
Change-Id: Ic059a0eff23b203056cdb54cdd1ae2f17f01a09c Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2017-09-27xci: Fix skip-vote for distro jobsFatih Degirmenci1-11/+20
Change-Id: I6dd25dca121dd6531bc2f0862da65497582bb407 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2017-09-27xci: Skip voting from Centos and OpenSUSE jobsFatih Degirmenci1-7/+7
Change-Id: I263417a7c2ae7a185a75a53e0352112ae5900afe Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2017-09-27xci: Pass project parameter to downstream jobs and adjust build blockerFatih Degirmenci1-2/+5
Change-Id: I25a8eb8606134255cc77d0b3d5c387e2cf4ee082 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2017-09-27xci: Switch to freestyle for xci-verify jobsFatih Degirmenci1-1/+1
Change-Id: I7a2fa9e3e2bb78ccc2dc6f26be7848019e6de6b8 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2017-09-27xci: Switch to freestyle for xci-verify jobsFatih Degirmenci1-28/+36
Change-Id: I0e1d922ec303bf71e0683b624c51a254da0b9c88 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2017-09-27xci: Enable multi-distro verifyFatih Degirmenci1-2/+2
Change-Id: I82e5db83092b5f4d6f4ea25464f416ce879d4709 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2017-09-27xci: Enable multi-distro verifyFatih Degirmenci1-0/+8
Only ubuntu job votes. The rest is still non-voting. Change-Id: I0fa2398d3a3d3c5e6e9570488f9e2c15db1c371c Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2017-09-26jjb: xci: xci-verify-jobs: Fix clean VM jobMarkos Chandras1-6/+7
According to https://docs.openstack.org/infra/jenkins-job-builder/definition.html#macro-notes we only need to use ${{x}} when the macro has parameters. However, none of our macros has so the correct way to use the shell variable is ${x}. Moreover, we set the missing execute bit in the jenkins test script. Additionally, we fix the OPNFV_RELENG_DEV_PATH parameter to point to the directory inside the VM where the releng-xci repo is located. Finally we fix the parent directory in which the test is executed. Change-Id: Ic6157caa5042274a3a3d0de276bdacc15a90a82d Signed-off-by: Markos Chandras <mchandras@suse.de>