summaryrefslogtreecommitdiffstats
path: root/jjb/xci
AgeCommit message (Collapse)AuthorFilesLines
2018-05-09jjb: xci: xci-start-new-vm: Fix gerrit variable for git SHAMarkos Chandras1-2/+2
The gerrit variable for the git SHA is GERRIT_PATCHSET_REVISION instead of GERRIT_CHANGE_ID. We also need to export the XCI_ANSIBLE_PARAMS variable. Change-Id: I206820f1155a4876fb7d87cc0b5ae1b8afb06bd6 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-05-08jjb: xci: xci-start-new-vm: Create scenario overrides fileMarkos Chandras1-3/+12
Pass scenario information using the new override mechanism. This patch depends on the matching releng-xci change https://gerrit.opnfv.org/gerrit/#/c/56643/ Change-Id: Ib8473249e424f259f5757ebdaed7d73fa4b0adce Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-04-16Merge "jjb: xci: bifrost-verify-jobs: Disable OPNFV bifrost jobs"Markos Chandras1-3/+3
2018-04-12jjb: xci: xci-run-functest: Escape the 'var' variableMarkos Chandras1-1/+1
Commit 33073c5a3426c1867411db446bc9e5d84d2a7747 ("jjb: xci: xci-run-functest.sh: Ensure env vars are quoted during reload") added support for reloading the OPNFV host environment in a safe way but that didn't work because the internal '$var' variable was not escaped so it was evaluated on the local host instead of the remote one. This fixes the problem by properly escaping the variable. Change-Id: I7c90ae18f77aca076579f70c7c0e9a72aaaad7c8 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-04-12jjb: xci: xci-run-functest.sh: Ensure env vars are quoted during reloadMarkos Chandras1-1/+1
The output of the 'env' command does not use quotes when printing the env variables so trying to source the xci.env file will lead to problems like the following one: /home/devuser/releng-xci/.cache/xci.env: line 17: PROFILEREAD: readonly variable /home/devuser/releng-xci/.cache/xci.env: line 20: 50340: command not found /home/devuser/releng-xci/.cache/xci.env: line 40: controller00: command not found /home/devuser/releng-xci/.cache/xci.env: line 48: on: command not found /home/devuser/releng-xci/.cache/xci.env: line 55: Francisco/O=IT/CN=xci.releng.opnfv.org: No such file or directory /home/devuser/releng-xci/.cache/xci.env: line 75: a: command not found /home/devuser/releng-xci/.cache/xci.env: line 88: -I: command not found /home/devuser/releng-xci/.cache/xci.env: line 90: 50340: command not found /home/devuser/releng-xci/.cache/xci.env: line 92: -e: command not found /home/devuser/releng-xci/.cache/xci.env: line 95: fg: no job control /home/devuser/releng-xci/.cache/xci.env: line 101: fg: no job control As such, we need to ensure that variables are properly quoted when exported. Change-Id: Ie98d8c921bae849d6bffd3858f67708f417b1d0f Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-04-12Merge "xci: Log functest-kubernetes.log to console"Fatih Degirmenci1-1/+15
2018-04-12jjb: xci: bifrost-verify-jobs: Disable OPNFV bifrost jobsMarkos Chandras1-3/+3
The jobs are unmaintained and broken for months. Upstream already has jobs for all 3 distributions so there is little value to test a similar scenario on the OPNFV side. As such, lets disable them and save some hardware resources for XCI. Change-Id: I0ab7d51f44bdeb6f630671e8d05dd2baf67d756c Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-04-12jjb: xci: xci-set-scenario.sh: Fix conditional for default scenarioMarkos Chandras1-1/+1
We only set default scenario if there is not one set already so we need to check if the array is empty. Change-Id: Ic5019fb68349adaf52d669aed43574bc5eaeddc3 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-04-12xci: Log functest-kubernetes.log to consoleFatih Degirmenci1-1/+15
Change-Id: I9576417cd2c47fd10153d841dddb334cb47c666e Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-04-11Merge "jjb: xci: Set XCI_PATH for bifrost jobs"Fatih Degirmenci1-0/+3
2018-04-11Merge "jjb: xci: Only set default scenario if no scenario is set"Fatih Degirmenci1-7/+11
2018-04-11Merge "jjb: xci: xci-set-scenario: Drop errexit option"Fatih Degirmenci1-1/+0
2018-04-11jjb: xci: xci-run-functest.sh: Reload XCI environment for functestMarkos Chandras1-2/+3
We should reload the XCI environment before running functest in order to ensure that playbooks have the correct information from the XCI deployment. Change-Id: Ieadeca61d3ea3e504e21aa96945ad067f20d1489 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-04-11xci: Enable Functest Healthcheck for Kubernetes scenariosFatih Degirmenci1-6/+0
This change enables Functest for kubernetes scenarios but any change that impacts kubernetes scenarios will fail and block the change from merging until the prepare-functest playbook and role are fixed in releng-xci. Change-Id: I046e3a0fb9a211cf9d629899017922288d466b0c Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-04-10jjb: xci: xci-set-scenario: Drop errexit optionMarkos Chandras1-1/+0
Commands may exit with non-zero exit code but this could be normal (for example grep does than when it doesn't match anything). As such, lets not fail on everything but rather capture such failures and handle them appropriately. Change-Id: Icc16d0ccd09fd6f262600ae514161bfdf0c593f1 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-04-06jjb: xci: Set XCI_PATH for bifrost jobsMarkos Chandras1-0/+3
The bifrost jobs are using some scripts from the releng-xci repository so we need to set the XCI_PATH variable appropriately. Change-Id: Ibfd139d2401029b2ea577c4797b68f29362356ec Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-04-06jjb: xci: Only set default scenario if no scenario is setMarkos Chandras1-7/+11
Previously, the code was already setting the default scenario if we had changes outside the xci/scenario directory. However, this is somewhat problematic since scenarios may touch other files which do not necessary affect other scenarios such as anything in xci/playbooks etc. As such, lets only set a default scenario if no scenario was set up to that point. However, since installers and scenarios need to match, we also need to consider installer changes because we fallback to the default scenario. Finally, since we are filtering results with 'uniq' we can simply drop the bash regexps prior to adding the scenario to the array. Change-Id: Ie961071b3e93d04a860bb6655513654208b1a9d4 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-04-06jjb: xci: Fix functest exit codeMarkos Chandras1-5/+3
There is not reason to grep the logs for failures because we can simply preserve the functest exit code and use that to determine whether the job passed or not. Change-Id: I9f027960fd3d9d452d417b95e9dac66bbb314a47 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-04-06jjb: xci: xci-set-scenario: Allow automatic detection of generic scenariosMarkos Chandras1-10/+10
The list of supported scenarios is hardcoded and this makes it difficult to test new scenarios. As such, lets determine the scenario and the installer based on the actual files that have been changed on every patchset. Change-Id: I4868a1da08d58cd6ff37347a0c0bc5c5e28b15bb Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-26xci: Set content-type of promotion properties file to text/htmlFatih Degirmenci1-1/+2
Change-Id: I609b796c629c68df214634ced5e9e6bda8ac2607 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-24xci: Run ansible within venvFatih Degirmenci1-1/+4
Change-Id: I20eb3c89c199b09ce839ae4ef6dfdcdd34dc58cf Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-23Merge "xci: Do not trigger merge jobs for INFO.yaml updates"Fatih Degirmenci1-0/+2
2018-03-22xci: Record promotion time in UTCFatih Degirmenci1-1/+1
Change-Id: Id6ea4f8124bdfe8c4233400d216d503fa101b0cb Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-23Merge "xci: Record additional promotion metadata for further use"Fatih Degirmenci1-0/+4
2018-03-22xci: Set additional variables in CI test scriptFatih Degirmenci1-0/+3
We need the variables CI_LOOP, BUILD_TAG, and NODE_NAME passed to the deployment to display during functest execution. Change-Id: Ib6709678d760d43927d3cd9f606d2c7e74e724d0 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
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-22xci: Record additional promotion metadata for further useFatih Degirmenci1-0/+4
It would be good to point to the link of the job that promoted certain scenario and display promotion date/time so we know when was the last time the scenario has successfully been promoted. Change-Id: I8099cf48f0ba5000cbf7622aa084f863f123eb15 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-22jjb: xci: bifrost-verify: Update location for XCI bifrost scriptsMarkos Chandras1-1/+1
Change-Id: I55e5042fda4bf5662a90f0065fa427a50bc76bfa Signed-off-by: Markos Chandras <mchandras@suse.de>
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 Degirmenci2-4/+61
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 Degirmenci2-9/+2
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 Degirmenci2-9/+34
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-17xci: Adjust the recorded scenario metadata for promotionFatih Degirmenci1-15/+21
PROJECT_NAME is added into scenario metadata to use for promotion and xci dashboard. Also, the metadata collected is aligned across different type of patches including the skipped ones. Change-Id: I3751884b48f5d9306d0cae35c757b976484b26a3 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-17Merge "xci: Log functest output before failure"Fatih Degirmenci1-2/+5
2018-03-16jjb: xci: xci-run-functest: Fix functest executionMarkos Chandras1-1/+1
We need to enter the $HOME/releng-xci/xci directory instead of /root/relneg-xci/xci since we are ssh'ing as 'devuser'. Change-Id: Id05d5012d58443c7f415a58f9f3d1ae16fd25b55 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-16xci: Revert change moving prepare-functest to opnfv vmFatih Degirmenci1-1/+1
Change-Id: Ic9801a2f1282b695025a6dce70e662765ce4296b Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-16potential fix for running prepare-functest playbookPeriyasamy Palanisamy1-1/+1
Change-Id: Id1ac133782e6b90929ddc055efbc6997ff63adc2 Signed-off-by: Periyasamy Palanisamy <periyasamy.palanisamy@ericsson.com>
2018-03-15Merge "xci: Skip the deployment for upstream and prototype changes"Fatih Degirmenci1-0/+4
2018-03-15Merge "run prepare-functest on opnfv vm"Fatih Degirmenci1-1/+1
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-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>