summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2018-04-13Merge "bugfix: run doctor tests parallelly"Serena Feng1-17/+1
2018-04-13Merge "Doctor job bugfix: fix the scenario"Serena Feng1-4/+9
2018-04-13Merge "Enable all yardstick tasks on baremetal for daisy"Serena Feng2-3/+5
2018-04-13Merge "[daisy] Move more CI resource to Fraser branch"Serena Feng1-4/+4
2018-04-13Enable all yardstick tasks on baremetal for daisyJulien2-3/+5
currently only master job is enabled. Change-Id: I7da6a1a3a8e8faf08cde34d9a20219346070151b Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
2018-04-12APEX: Fix gate check scenario detectionFeng Pan3-39/+11
- Change scenario parsing to allow k8s scenarios in gate jobs. - Remove scenario detection in shell scripts. Also changes network setting file for fd.io scenarios as we don't use separate config files any more. Change-Id: Icbcc6cb7b6b66c7cc43f5d6c58dd97730e41ea5f Signed-off-by: Feng Pan <fpan@redhat.com>
2018-04-12Merge "Remove euphrates jobs"Aric Gardner1-4/+0
2018-04-12Merge "Remove euphrates jobs"Aric Gardner1-4/+0
2018-04-12Merge "Remove euphrates jobs"Aric Gardner1-4/+0
2018-04-12Merge "Remove euphrates from domino"Aric Gardner1-4/+0
2018-04-12Report Fuel Deployments to Testapi DashboardTrevor Bramwell2-0/+6
Using these macros for deployment jobs will report the deployment results of Fuel to the testresults database[1]. [1] http://testresults.opnfv.org/test/#/deployresults Change-Id: I353631f073578b4a2da0f08ffba4042931e65dca Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-04-12Merge "Move DEPLOY_SCENARIO out of testapi-parameters"Trevor Bramwell3-4/+38
2018-04-12Merge "Remove euphrates jobs"Aric Gardner1-4/+0
2018-04-12Merge "Remove euphrates jobs"Aric Gardner1-3/+0
2018-04-12Merge "Remove euphrates jobs"Aric Gardner1-5/+0
2018-04-12Merge "Remove Euphrates jobs"Aric Gardner1-4/+0
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 "Stop maintaining Euphrates (EOL)"Fatih Degirmenci4-24/+7
2018-04-12Merge "Create Xtesting Fraser jjobs"Fatih Degirmenci2-1/+4
2018-04-12Merge "xci: Log functest-kubernetes.log to console"Fatih Degirmenci1-1/+15
2018-04-12[daisy] Move more CI resource to Fraser branchZhijiang Hu1-4/+4
Temporary disable master branch job on zte-pod2 to make room for Fraser branch job. Change-Id: I9f2eea0e1c85eab741f80e6db6b773eec71c39f1 Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
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-12Doctor job bugfix: fix the scenariodongwenjuan1-4/+9
Use these scenario which can trigger doctor jobs running in functest Change-Id: I66df099c3923b9c47aab9f9f8685052bd33331f7 Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
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-12bugfix: run doctor tests parallellydongwenjuan1-17/+1
Currently doctor job uses multiple 'multijob' in builders to virify tests in different installers, these multijobs run in sequentially which will cost a long time. These jobs are not related to each other in different installer. Change-Id: Idce03920ec6244a9ce288c940a24d0707af1a694 Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2018-04-12container4nfv: add fraser branch in arm jobsYibo Cai1-11/+35
Change-Id: If5b4dfaef431570f65a321209a4fa4c94292d89f Signed-off-by: Yibo Cai <yibo.cai@arm.com>
2018-04-12Stop maintaining Euphrates (EOL)agardner4-24/+7
Change-Id: Ibd6a523aa9da3aa6c2622a5f183102ffdbc3ccb8 Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-04-11Remove euphrates jobsagardner1-4/+0
Change-Id: I167bbea911fb3aee6fa21b7ff28b18d7fae61bb9 Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-04-11Remove euphrates jobsagardner1-4/+0
Change-Id: I0a5a6d584b3740d88dc4f342ffc1d107962762e6 Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-04-11Remove euphrates jobsagardner1-4/+0
Change-Id: Icf57ec3e65e391207333bb8780ea215bcf4434a4 Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-04-11Remove euphrates jobsagardner1-4/+0
Change-Id: I21c5ab27243bd50dee76d8b10c10ae0fb8aa5f1d Signed-off-by: agardner <agardner@linuxfoundation.org>
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-11Remove euphrates from dominoagardner1-4/+0
Domino is not in the fraser release. This is part of a cleanup to remove euphrates jobs Change-Id: Ica789accd0148cf847c3498d151bd8ae0b59e8bd Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-04-11Remove euphrates jobsagardner1-4/+0
Change-Id: I63fdf2826d2077465f264f082dc1a15eafc2b05a Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-04-11Remove euphrates jobsagardner1-3/+0
Change-Id: I5e5f66b1226291934fecca6fcf83dd649fb82f0e Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-04-11Remove euphrates jobsagardner1-5/+0
Change-Id: Idbe3be3da5ddf0fb9b1649002d7cf6bd8babc817 Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-04-11Remove Euphrates jobsagardner1-4/+0
Change-Id: I8a223d7f9a0458f9cc01a2fedcb630b711b4465f Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-04-11Merge "Apex: Fix log collection for daily job"Tim Rozet2-2/+2
2018-04-11Move DEPLOY_SCENARIO out of testapi-parametersTrevor Bramwell3-4/+38
These have been moved back into installer-params.yml and added to the daisy jobs where 'testapi-parameters' is being used. Including this in the list of parameters would cause duplication as most installers already include 'DEPLOY_SCENARIO' as a parameter. The 'DEPLOY_SCENARIO' parameter is also sometimes defined through a macro, which could cause second declaration of DEPLOY_SCENARIO (defaulting to 'os-nosdn-nofeature-ha') to always be used. Documentation has been added to the parameter to explain the related macros and how they should be used. Change-Id: I9aef031dbcf523ae2db15695ce294bd85025530d Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-04-11Merge "docker build -f should use relative path to PATH, not working directory"Aric Gardner1-8/+8
2018-04-11Apex: Fix log collection for daily jobTim Rozet2-2/+2
The wrong job name was being triggered so no job was running to collect logs. Change-Id: Ib58b030ac24920fc7906bff92a481407587a39bf Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-04-11Create Xtesting Fraser jjobsCédric Ollivier2-1/+4
Change-Id: I761ec6f28ab4b2d7dc47250d49730dbe302221e0 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-04-11Merge "jjb: xci: xci-set-scenario: Drop errexit option"Fatih Degirmenci1-1/+0
2018-04-11Merge "Create Xtesting stable/fraser"Fatih Degirmenci1-0/+3
2018-04-11Merge "Stop verifying Functest Euphrates"Fatih Degirmenci1-4/+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-11Merge "xci: Enable Functest Healthcheck for Kubernetes scenarios"Fatih Degirmenci1-6/+0