summaryrefslogtreecommitdiffstats
path: root/jjb/xci
AgeCommit message (Collapse)AuthorFilesLines
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
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: Refactor bifrost jobs to use the XCI clean VMMarkos Chandras2-150/+17
We no longer run opnfv/bifrost jobs so drop all the references from the configuration file. Moreover, make use of the releng-xci XCI clean VM virtual machine to run the tests on a clean environment. Finally, we drop the support for uploading logs to the artifacts.opnfv.org. This needs to be done for XCI as well so we will bring it back when we develop a universal solution. Change-Id: I9bad17508ab8ee6594aec444ab864b99331b616d 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 Bramwell6-1024/+1044
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>
2017-09-26jjb: xci: Create XCI test scriptMarkos Chandras1-3/+25
We need to respect the environment during testing so we need to create a proper test script which exports all the variables that matter for our tests. We do that before we create the VM so the VM creation script can rsync the test for us. We also properly escape the DISTRO variable when destroying the VM. Change-Id: Ic3fff40868155af31762e458c1faee24354c0712 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-09-25jjb: xci: xci-verify-jobs: Fix XCI VM namesMarkos Chandras1-2/+2
The XCI script now uses more accurate VM names, so replace the VM name in the destroy job as well. Change-Id: Ia4c8ea204ecaa6ae765ce67aff3923dabab6d5f0 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-09-25jjb: xci: xci-verify-jobs: Use clean vm to verify XCI jobsMarkos Chandras1-16/+33
Per Idec0fc06c82435adc1a4d569b8e578616998de5f it's now possible to use a clean virtual machine to verify XCI so lets make use of it. Moreover this patch updates the distro parameter to use more accurate names and bring it inline with what dib expects. Change-Id: I18c88637819884fef07d0bfa0dc2c1077a26c2f1 Signed-off-by: Markos Chandras <mchandras@suse.de> Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2017-09-21[Functest] Support functest-suite with Alpine containersJose Lausuch3-2/+13
Updated all the jobs that use functest-suite. For single test cases, we need to know to which docker image the test belongs to. Change-Id: If7db231ccc891233423f2f2bc3aa5b95d048b30a Signed-off-by: Jose Lausuch <jalausuch@suse.com>