summaryrefslogtreecommitdiffstats
path: root/jjb/xci/xci-run-functest.sh
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-13jjb: xci: Ensure GERRIT_TOPIC is always setMarkos Chandras1-0/+3
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-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-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-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-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-26xci: Set appropriate permissions for the keyFatih Degirmenci1-0/+1
Change-Id: I6387ca1f7eaf107f735eab82917d77b2f3a3d90a Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-02-26xci: Move out of WORKSPACE before wiping it out and log scenario to consoleFatih Degirmenci1-2/+2
Change-Id: Ia2caeef24a199580a9eeb2ba6214fa2008f65c1c Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-02-26xci: Fix the Gerrit Trigger clone issue for external scenariosFatih Degirmenci1-0/+11
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-01-25xci: Run functest as part of xci-merge jobsFatih Degirmenci1-1/+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 Degirmenci1-0/+7
Change-Id: I22d2327558ee1d19d04775da6abf1b3eed5b357a Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-01-22xci: Convert execute shell scripts to external scriptsFatih Degirmenci1-0/+23
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>