summaryrefslogtreecommitdiffstats
path: root/jjb/xci
AgeCommit message (Collapse)AuthorFilesLines
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>
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 Degirmenci2-3/+1
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-23xci: Skip jobs if the scenario is not supported on a distroFatih Degirmenci4-0/+28
Change-Id: I22d2327558ee1d19d04775da6abf1b3eed5b357a Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-01-22xci: Do not clone and checkout scenario repo if it is releng-xciFatih Degirmenci1-1/+1
Change-Id: I48cdbfbd5b7746e75565d318616e9c580b5ba156 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
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 Degirmenci2-0/+9
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 Degirmenci2-19/+34
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-22xci: Convert execute shell scripts to external scriptsFatih Degirmenci5-77/+128
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>
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>
2017-12-21xci: Create periodic jobs for upstream osaFatih Degirmenci2-84/+114
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-15Merge "xci: Use custom-url for readable CI reports"Fatih Degirmenci2-0/+2
2017-12-15xci: Use custom-url for readable CI reportsMarkos Chandras2-0/+2
Change-Id: I97d8fac47ec25414045a7761b651019f9f89224f Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-12-14jjb: xci: Use the correct SSH configuration fileMarkos Chandras1-4/+1
We need to use the XCI specific SSH configuration file so rsync can tranfer the working directory to the virtual machine. This also drop the ironic command like we do in the XCI jobs. Change-Id: I10ce38db6777d5dbfbe62961c88b3902de2160e2 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-12-05Merge "jjb: xci: xci-verify-jobs: Fix block on bifrost jobs"Markos Chandras1-2/+2
2017-11-30jjb: xci: bifrost-verify.sh: Do not build OS imagesMarkos Chandras1-1/+4
Use the images we provide in artifacts.opnfv.org instead of building new ones on every CI run. Moreover, enter the correct directory before executing the CI script. Change-Id: Iffa0080ab8f746344aa13bca6a26395a8a0953f2 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-30jjb: xci: bifrost-verify: Simplify bifrost jobMarkos Chandras2-8/+5
We no longer test OPNFV commits that affect bifrost since these are being tested as part of the XCI jobs. As such, simplify the job to only test incoming upstream patchsets. Moreover, we need to block when an XCI job is running since both jobs run on the same hosts and create the same VMs. Change-Id: I5c11ae5b6a4d719ec41a6e663ddf6ecbd71ac1a5 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-20jjb: xci: bifrost: Enable jobs and use XCI ssh configurationMarkos Chandras2-9/+14
Enable the 'bifrost' jobs and also make use of the XCI specific ssh configuration file. Change-Id: I04d15610b596191622cf028b3408b4d63ee7090b 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-07Merge "jjb: xci: xci-verify-jobs: Skip complete XCI deployments for ↵Markos Chandras1-2/+2
'skip-deloyment'"
2017-10-06Merge "jjb: xci: bifrost-cleanup-jobs: Disable cleanup bifrost jobs"Markos Chandras1-0/+1
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: bifrost-cleanup-jobs: Disable cleanup bifrost jobsMarkos Chandras1-0/+1
We no longer update logs in artifacts.opnfv.org so there is no point in running this job. We will enable it back when we start uploading logs for XCI. Change-Id: Icee15d346c32dff693b5c474a51fb79763841bb7 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-10-06Merge "jjb: xci: Refactor bifrost jobs to use the XCI clean VM"Markos Chandras2-150/+17