summaryrefslogtreecommitdiffstats
path: root/jjb/xci
AgeCommit message (Collapse)AuthorFilesLines
2018-03-15run prepare-functest on opnfv vmPeriyasamy Palanisamy1-1/+1
Change-Id: Ide49917687ed583497ca089969fd2c7e7e00e548 Signed-off-by: Periyasamy Palanisamy <periyasamy.palanisamy@ericsson.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 Degirmenci3-70/+226
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-14xci: Log functest output before failureFatih Degirmenci1-2/+5
When functest fails, the job exits directly without us logging the functest output to console. [1] Grepping functest log for FAIL for determining the result helps us to cat the log before exiting with right exit code. [1] https://build.opnfv.org/ci/job/xci-verify-ubuntu-healthcheck-virtual-master/509/console Change-Id: I01e3dcc51321e935b1722b749e8caf7ec5ad755b Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-13Merge "xci: Allow specifying scenario and installer in commit message"Fatih Degirmenci1-20/+68
2018-03-13xci: Allow specifying scenario and installer in commit messageFatih Degirmenci1-20/+68
It is not always practical to try determining scenario and installer to run jobs programmatically. This change adds possibility to do that by parsing commit message and skipping the automatic scenario and installer extraction. Change-Id: I10c9620fe8bb69a2d69fceb31d08084265aa1d75 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-13jjb: xci: Ensure GERRIT_TOPIC is always setMarkos Chandras4-0/+12
Fixes the following problem [description-setter] Description set: Scenario: os-nosdn-nofeature | Node: intel-virtual14 [xci-verify-ubuntu-healthcheck-virtual-master] $ /bin/bash /tmp/jenkins7521920744845291696.sh /tmp/jenkins7521920744845291696.sh: line 21: GERRIT_TOPIC: unbound variable Build step 'Execute shell' marked build as failure Change-Id: Iddf82e6ae6c6c433d941c461953c11935bc45269 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-13jjb: xci: Allow CI to run when multiple components are affectedMarkos Chandras1-0/+7
Sometimes we make global changes that affect multiple components at once and splitting that is not possible because it needs to be shipped as an atomic change. As such, allow topics with 'force-verify' to run the CI using the default installer and scenario. Change-Id: Ie4753822111b20c4f479886a55fe569c9b91ccd0 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-12xci: Combine vars setting installer type in INSTALLER_TYPEFatih Degirmenci2-5/+5
Change-Id: I5312ac784b1621ce968bbdfb1532859dada0e790 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-12Merge "xci: Set installer type for the tested scenario"Fatih Degirmenci2-4/+1
2018-03-12xci: Set installer type for the tested scenarioFatih Degirmenci2-4/+1
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: Skip functest healtcheck if it is Kubernetes scenarioFatih Degirmenci1-0/+6
We need to work on functest healthcheck for Kubernetes scenarios. Until we get it working, healthcheck is disabled. Change-Id: If470dbe956c5859825f0829d1f8d022bdafcc242 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-12xci: Determine impacted generic scenarioFatih Degirmenci1-15/+39
Change-Id: Ifbe676cd347c2d3c68f04b5137f3ccaa83a95894 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-12xci: Set the installer and move scenario extraction into functionsFatih Degirmenci2-33/+65
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-12Merge "jjb: xci: Drop the VM cleanup step from the functest jobs"Markos Chandras2-4/+0
2018-03-12Merge "xci: Set options in run-functest.sh"Markos Chandras1-0/+3
2018-03-12jjb: xci: Drop the VM cleanup step from the functest jobsMarkos Chandras2-4/+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-12Merge "jjb: xci: Add postbuild publisher script to remove clean VM"Markos Chandras5-2/+36
2018-03-08xci: Set options in run-functest.shFatih Degirmenci1-0/+3
Functest healthcheck job actually fails but due to not setting options properly in run-functest.sh, we failed to notice this. Please note that this patch will enable changes to be blocked since creation of external network and associated subnet fail, due to an upstream issue. This causes functest healthcheck to fail which in turn results in Verified-1 on Gerrit. Change-Id: I32eeb422895930d039d3289ffb65e10763db9c4b Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-08jjb: xci: xci-start-new-vm: Switch to pre-built bifrost OS imagesMarkos Chandras1-0/+1
Change-Id: I19e60eea65b01ec22bb32c0efcdc6b071b22ca34 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-07jjb: xci: Add postbuild publisher script to remove clean VMMarkos Chandras5-2/+36
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-03-02jjb: xci: Use core OpenStack installation by defaultMarkos Chandras2-0/+2
We do not need all the components installed when deploying OpenStack so we can speed up the jobs by removing some of them. Change-Id: I19120915d0ef7c59b8b470c5fb87e9c0aa3e3673 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-02xci: Cat functest log until the log upload is enabledFatih Degirmenci1-0/+4
Change-Id: I883e6e29cf102d1069e3760ab95dd24d76d0a222 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-01xci: Do not fail the job if virsh command failsFatih Degirmenci2-4/+4
Change-Id: Ie5fae322f98ec6c9c2236486642c0d71c6a04aae Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-01xci: Fix scenario name extractionFatih Degirmenci1-1/+1
Change-Id: Ifcea3d364b73d0d19d46aaf2bd2210ec6440f383 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-02-28xci: Use distro specific ssh config while sshing to xci vmsFatih Degirmenci2-2/+2
Change-Id: I9366639570315f879a662ca9e65a1894cd905a92 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-02-28xci: Use distro specific ssh config while sshing to xci vmsFatih Degirmenci3-4/+4
Change-Id: I231488cd9de58a9051bd289c3d584841e7335417 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-02-28xci: Use distro specific ssh config while sshing to xci vmsFatih Degirmenci1-2/+2
Change-Id: I5e8b738d4293040b2792a926cd13708180590bbb Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-02-28xci: Move run-functest.sh execution out of ansibleFatih Degirmenci1-1/+3
Change-Id: I40195f08012774c22178a27f146c402b33ecd8fc Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-02-27xci: Set the scenario to os-nosdn-nofeature if the verify is skippedFatih Degirmenci1-4/+6
The envInject complains due to nonexistent scenario.properties so we set the scenario to os-nosdn-nofeature to suppress the failures since there is nothing to fail. Change-Id: Ic259ec53e77cf8afe62638a1b447c8e58863b419 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
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-26Merge "xci: Set appropriate permissions for the key"Fatih Degirmenci4-0/+4
2018-02-26xci: Set appropriate permissions for the keyFatih Degirmenci4-0/+4
Change-Id: I6387ca1f7eaf107f735eab82917d77b2f3a3d90a 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: Move out of WORKSPACE before wiping it out and log scenario to consoleFatih Degirmenci4-8/+19
Change-Id: Ia2caeef24a199580a9eeb2ba6214fa2008f65c1c Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-02-26xci: Fix the Gerrit Trigger clone issue for external scenariosFatih Degirmenci4-8/+41
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 Degirmenci2-16/+21
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 Degirmenci2-5/+89
2018-02-23jjb: xci: xci-start-new-vm.sh: Set pipefail optionMarkos Chandras1-0/+1
In commit I77d5d66c0146f943d805612ca5b47e2eed3ffc41 the 'ts' utility was added in order to print timestamps for deployment. However, this breaks the exit code since 'pipefail' was not set so every job was returning 'success'. Change-Id: I2625a655a7334b1e43b690618821e69377075ed1 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-02-21jjb: xci: Use the 'ts' utility to print timestamps on executed steps.Markos Chandras2-2/+2
We can use the 'ts' utility to print timestamps on every executed command so we can keep track on the duration of each task and the job overall. Change-Id: I77d5d66c0146f943d805612ca5b47e2eed3ffc41 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-02-21Merge "Rename var XCI_LOOP to CI_LOOP to align with Functest"Fatih Degirmenci4-9/+9
2018-02-21Merge "jjb: xci: Fix bifrost blockers for XCI jobs"Markos Chandras3-5/+10
2018-02-21jjb: xci: Fix bifrost blockers for XCI jobsMarkos Chandras3-5/+10
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-19jjb: xci: bifrost-verify-jobs: Increase build-timeout valueMarkos Chandras1-1/+1
The bifrost jobs could run in parallel with the XCI ones so it may take longer than 90 minutes to complete. Lets double the timeout value in order to ensure that we don't fail due to a Jenkins timeout. Change-Id: I53a442f434d839d891bf03e41ba1a6a4459fd878 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-02-15jjb: xci: Add missing job blockers for XCI merge jobsMarkos Chandras2-0/+8
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 Degirmenci2-5/+89
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-14Rename var XCI_LOOP to CI_LOOP to align with FunctestFatih Degirmenci4-9/+9
Change-Id: If5c5b828312dc588515589b8075b9754537b8f86 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-02-08jjb: xci: bifrost-verify.sh: Respect bifrost test failuresMarkos Chandras1-0/+5
Make sure that failures during bifrost deployments are being reported properly on Jenkins. Change-Id: I333d27147caf7598665157c703907572e48041c0 Signed-off-by: Markos Chandras <mchandras@suse.de>