Age | Commit message (Collapse) | Author | Files | Lines |
|
* Update docs/submodules/releng from branch 'master'
- Merge "jjb: xci: bifrost-verify-jobs: Disable OPNFV bifrost jobs"
- jjb: xci: bifrost-verify-jobs: Disable OPNFV bifrost jobs
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Remove euphrates jobs"
- Remove euphrates jobs
Change-Id: Icf57ec3e65e391207333bb8780ea215bcf4434a4
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Report Fuel Deployments to Testapi Dashboard"
- Report Fuel Deployments to Testapi Dashboard
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Apex: remove non-released scenarios for Fraser
We will not support RT KVM and IPv6 scenario.
Change-Id: Iabd52f3ff803488e1ac68e8946001a7c04f5ca7f
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
* Update docs/submodules/releng from branch 'master'
- APEX: Fix missing bash command in verify job
Change-Id: I055ec261368b341c5dd9f2ab5082c8ced15ad6e5
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Create CI job for network testing"
- Create CI job for network testing
JIRA: QTIP-297
Change-Id: Ie3002ab4eae57d79d0edeb9c39c2ab273c5c3915
Signed-off-by: Taseer Ahmed <taseer94@gmail.com>
|
|
* Update docs/submodules/releng from branch 'master'
- [qtip] enable fraser ci jobs
Change-Id: Ic9bf36c63592eac60406d362bedf1c6bd352ab9c
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "bugfix: run doctor tests parallelly"
- bugfix: run doctor tests parallelly
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Doctor job bugfix: fix the scenario"
- Doctor job bugfix: fix the scenario
Use these scenario which can trigger doctor jobs running in functest
Change-Id: I66df099c3923b9c47aab9f9f8685052bd33331f7
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Enable all yardstick tasks on baremetal for daisy"
- Enable all yardstick tasks on baremetal for daisy
currently only master job is enabled.
Change-Id: I7da6a1a3a8e8faf08cde34d9a20219346070151b
Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "[daisy] Move more CI resource to Fraser branch"
- [daisy] Move more CI resource to Fraser branch
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>
|
|
* Update docs/submodules/releng from branch 'master'
- APEX: Fix gate check scenario detection
- 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>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Remove euphrates jobs"
- Remove euphrates jobs
Change-Id: I167bbea911fb3aee6fa21b7ff28b18d7fae61bb9
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Remove euphrates jobs"
- Remove euphrates jobs
Change-Id: I0a5a6d584b3740d88dc4f342ffc1d107962762e6
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Remove euphrates jobs"
- Remove euphrates jobs
Change-Id: I21c5ab27243bd50dee76d8b10c10ae0fb8aa5f1d
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Remove euphrates from domino"
- Remove euphrates from domino
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Move DEPLOY_SCENARIO out of testapi-parameters"
- Move DEPLOY_SCENARIO out of testapi-parameters
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Remove euphrates jobs"
- Remove euphrates jobs
Change-Id: I63fdf2826d2077465f264f082dc1a15eafc2b05a
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Remove euphrates jobs"
- Remove euphrates jobs
Change-Id: I5e5f66b1226291934fecca6fcf83dd649fb82f0e
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Remove euphrates jobs"
- Remove euphrates jobs
Change-Id: Idbe3be3da5ddf0fb9b1649002d7cf6bd8babc817
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Remove Euphrates jobs"
- Remove Euphrates jobs
Change-Id: I8a223d7f9a0458f9cc01a2fedcb630b711b4465f
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
* Update docs/submodules/releng from branch 'master'
- jjb: xci: xci-run-functest: Escape the 'var' variable
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>
|
|
* Update docs/submodules/releng from branch 'master'
- jjb: xci: xci-run-functest.sh: Ensure env vars are quoted during reload
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Stop maintaining Euphrates (EOL)"
- Stop maintaining Euphrates (EOL)
Change-Id: Ibd6a523aa9da3aa6c2622a5f183102ffdbc3ccb8
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Create Xtesting Fraser jjobs"
- Create Xtesting Fraser jjobs
Change-Id: I761ec6f28ab4b2d7dc47250d49730dbe302221e0
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "xci: Log functest-kubernetes.log to console"
- xci: Log functest-kubernetes.log to console
Change-Id: I9576417cd2c47fd10153d841dddb334cb47c666e
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
* Update docs/submodules/releng from branch 'master'
- jjb: xci: xci-set-scenario.sh: Fix conditional for default scenario
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "jjb: xci: Set XCI_PATH for bifrost jobs"
- jjb: xci: Set XCI_PATH for bifrost jobs
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "jjb: xci: Only set default scenario if no scenario is set"
- jjb: xci: Only set default scenario if no scenario is set
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Apex: Fix log collection for daily job"
- Apex: Fix log collection for daily job
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "docker build -f should use relative path to PATH, not working directory"
- docker build -f should use relative path to PATH, not working directory
Change-Id: I6b35a5b36b1cc7b8ce2298388b9bb5caf9e44fc9
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "jjb: xci: xci-set-scenario: Drop errexit option"
- jjb: xci: xci-set-scenario: Drop errexit option
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Create Xtesting stable/fraser"
- Create Xtesting stable/fraser
Xtesting is not directly part of Fraser but this stable branch could
be required for bugfixes.
stable/pike could have been selected instead but it would have raised
side effects when syncing requirements or building containers.
Change-Id: I407f651ba09e27a7c87cc76f7b8ccbd6c0784a48
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Stop verifying Functest Euphrates"
- Stop verifying Functest Euphrates
Functest Euphrates is now EOL (jjobs creating containers has already
been removed)
Change-Id: I668137b2701d073ce95856fa20dc54135a6cc111
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
* Update docs/submodules/releng from branch 'master'
- jjb: xci: xci-run-functest.sh: Reload XCI environment for functest
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "xci: Enable Functest Healthcheck for Kubernetes scenarios"
- xci: Enable Functest Healthcheck for Kubernetes scenarios
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "[QTIP] Enable QTIP fraser docker build job"
- [QTIP] Enable QTIP fraser docker build job
- enable fraser docker build job
- disable euphrates docker build job
Change-Id: Ieeaec7ed36ee8d77a250c0f584ea9e5985a41c8f
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
* Update docs/submodules/dovetail from branch 'master'
- Add functest healthcheck test suite
- Add Functest healthcheck tier to Dovetail as new test suite
- Intention is that these test cases are not part of mandatory
test cases in compliance program
- Use for debug and SUT pre-flight check
- May consider running tc001 (connection_check) at other
test execution stages to determine if SUT is still functioning, as
this test takes < 10 sec (more important as test complexity increases
such as in vnf test tier)
- Replacement for patch:
https://gerrit.opnfv.org/gerrit/#/c/52461/
- Removed CI filters, as suggested
Change-Id: I2e72931b27e43359d6250f6959a17af8526c5094
Signed-off-by: Eddie Arrage <eddie.arrage@huawei.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "create Stable Branch Jobs for nfvbench"
- create Stable Branch Jobs for nfvbench
Same for docker
Change-Id: I48650881f5c0c8e7b4664b87b1b1a4a37c22cc8d
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
* Update docs/submodules/releng from branch 'master'
- Apex: Update master daily scenarios
As part of our new XCI effort, we only enable upstream ODL scenarios
initially.
Change-Id: I737bbffce14b6c5c69dfbbb653659c7e693cb4fb
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "[yardstick] enable fraser docker"
- [yardstick] enable fraser docker
Change-Id: I47ae73da7240ee4c4e3902baa7320412a28ada6c
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Enable Apex Fraser Jobs"
- Enable Apex Fraser Jobs
Change-Id: Ie7bd0d3299fbbb8bc3e865612026ad479c48392d
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Create Stable Branch Jobs for calipso"
- Create Stable Branch Jobs for calipso
Change-Id: I2117807b8af3ee248b30747830e32b1661a23d6f
Signed-off-by: jenkins-ci <jenkins-opnfv-ci@opnfv.org>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "[opnfvdocs] Create stable/fraser Branch"
- [opnfvdocs] Create stable/fraser Branch
Change-Id: I1a506b327c125d61088277d8e92b5b6ce08f4e87
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
* Update docs/submodules/dovetail from branch 'master'
- Decoupling Yardstick Docker config items from source code
There are some special Docker setting items when creating
Yardstick Docker Containers.
1. Remove the extra settings which are required by Yardstick Danube.
2. Remove the settings for pushing results to DB because Dovetail
plan to disable this function.
3. Move the other special Functest settings to config files.
JIRA: DOVETAIL-640
Change-Id: Ic2d90393e227d7886b14d805eaa307b7aef56e4a
Signed-off-by: xudan <xudan16@huawei.com>
|
|
* Update docs/submodules/dovetail from branch 'master'
- Support to specify docker image for each test case
1. Currently each type of test cases will use one docker image.
2. For example,
Functest test cases use opnfv/functest-restapi:euphrates
Yardstick uses opnfv/yardstick:opnfv-5.1.0
3. It needs to support to specify the docker image for each test case.
4. For example,
vping test cases use opnfv/functest-smoke:euphrates
sdnvpn uses opnfv/functest-features:euphrates
5. The benefit of this is that these docker images are well verified
by Functest CI and from Functest plan, they may not support
functest-restapi docker image in its future release.
JIRA: DOVETAIL-638
Change-Id: I8a30eea2233aeff809af2e241b6c939194397832
Signed-off-by: xudan <xudan16@huawei.com>
|
|
* Update docs/submodules/releng from branch 'master'
- [doctor] clean pep8 job
The global 'lint-all-code' job is already enabled for doctor repo,
so there is no need to keep this verify job which only run pep8.
JIRA: DOCTOR-120
Change-Id: I6eb95590b97c3bd2c2daa80a6ae3bcfe4a4119a4
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "delete 'opnfv-build-ubuntu-defaults' parameters for doctor verify job"
- delete 'opnfv-build-ubuntu-defaults' parameters for doctor verify job
Currently it will pass all the 'opnfv-build-ubuntu-defaults' parameters
to the child jobs which include the node 'label', so all the doctor jobs
will be running in the nodes with 'opnfv-build-ubuntu' label.
Change-Id: If01f1f777c30c421f063c05fdd3c939f8758226c
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Create Stable Branch Jobs for container4nfv"
- Create Stable Branch Jobs for container4nfv
Change-Id: If4c4305faaa74cfd87feb4f1a8e403abd419d7a1
Signed-off-by: jenkins-ci <jenkins-opnfv-ci@opnfv.org>
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "[daisy] Enable functest daily jobs on zte-pod9 for stable/fraser branch"
- [daisy] Enable functest daily jobs on zte-pod9 for stable/fraser branch
This PS is trying to solve errors like occured in [1].
[1] https://build.opnfv.org/ci/job/daisy-os-nosdn-nofeature-ha-baremetal-daily-fraser/5/console
Change-Id: Ie4e023794d54cf0e236e9094fabf8362e17d9c8a
Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
|