Age | Commit message (Collapse) | Author | Files | Lines |
|
* Update docs/submodules/releng from branch 'master'
- Add docker push job for arm
Change-Id: Id7e9e0b3a28102b6efa1e4fbd4c648eca10d9456
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "yardstick: enable euphrates docker"
- yardstick: enable euphrates docker
Change-Id: I745287911eab7414adccd99e9e2385bf5b7438f7
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Remove Restriction on Total Docker Builds per Node"
- Remove Restriction on Total Docker Builds per Node
The docker build script will only allow one docker build at a time. As
docker builds are now restricted to one per-node by project through the
throttle-build plugin, this restriction can be lifted.
JIRA: RELENG-315
Change-Id: I4c430f99eaaed831fa0c49284280a8fa9fbe13c8
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
* Update docs/submodules/releng from branch 'master'
- jjb: xci: xci-verify-jobs: Fix clean VM job
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "jjb: xci: Create XCI test script"
- jjb: xci: Create XCI test script
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "run for E release."
- run for E release.
As JOID do not have access to any other POD so changing from
master to E release for E release build.
Change-Id: I1ba9b92be0c3056023eac0e5869de041cf429344
Signed-off-by: Narinder Gupta <narinder.gupta@canonical.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Monitor all .ipynb for notebook preview"
- Monitor all .ipynb for notebook preview
JIRA: QTIP-273
Change-Id: I8d192c70b881cc826fa37d15eec7eb4173a51e35
Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
|
|
* Update docs/submodules/releng from branch 'master'
- [Functest] Avoid reporting results for suite job
Change-Id: I182962570fc88e181f312ad432daf774b79e44f1
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
* Update docs/submodules/releng from branch 'master'
- [Functest] Fix syntax error in alpine job
Change-Id: I1bb751e1df37bb00347f5597c95066041b37ead2
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Throttle Docker Builds to 1 Per-Node"
- Throttle Docker Builds to 1 Per-Node
Docker builds are currently timing out when multiple builds are running
on the same node. Builds start in parallel but Docker only allows one
to run at a time. By throttling builds to 1 per-node Docker builds will
run sequentially, as they are currently, but not timeout.
JIRA: RELENG-315
Change-Id: Ib64252f9449cccdc35856debafd3bcb8796f1100
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Fix Yamllint violations for jjb/securedlab"
- Fix Yamllint violations for jjb/securedlab
JIRA: RELENG-254
Change-Id: Iaf0c4a23f5d9b6117ec7a455ee1650e68893f4b3
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "securedlab: Use Pharos git sub for PDF validation"
- securedlab: Use Pharos git sub for PDF validation
- drop obsolete file pattern matching.
- drop duplicate check-jinja2.sh from releng, use securedlab script;
While at it, s/danube/euphrates/ to enable stable/E verify.
Depends-on: I9d6807f3d24cee8d9a03955112a8c179d9ea7d14
Change-Id: Ia88140d872f2b64ff013f22ef0f43bd2cb31bd4f
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
* Update docs/submodules/releng from branch 'master'
- jjb: xci: xci-verify-jobs: Fix XCI VM names
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Only Allow ASCII Characters in JJB Scripts
Since Jenkins job builder doesn't support unicode yet, any non-ascii
character will break the releng-merge-jjb job.
Change-Id: Idc50c258c9c00c8d594717364907e701d9fee385
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "jjb: xci: xci-verify-jobs: Use clean vm to verify XCI jobs"
- jjb: xci: xci-verify-jobs: Use clean vm to verify XCI jobs
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Enable daisy euphrates jobs of daily and functest"
- Enable daisy euphrates jobs of daily and functest
Change-Id: I8c0c088c5b6879033e1d369488b589271e741a68
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
* Update docs/submodules/releng from branch 'master'
- [Functest] Fix unicode issue
Change-Id: I40e00a1abfc383bb5f13a8ec140294d3a67e5cbf
Signed-off-by: Jose Lausuch <jalausuch@suse.com>
|
|
* Update docs/submodules/releng from branch 'master'
- [Functest] Fix nits in alpine jobs
And add debug information for the suite jobs
Change-Id: I478a09c689b54f82246a72c19726576ff5aeaffd
Signed-off-by: Jose Lausuch <jalausuch@suse.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Restrict functest running with k8 deployment
Also, improve suite job with alpine images.
Change-Id: I1367dea6b09361641c38ef91652acec5be4fbebb
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "cloudify_ims reporting fixes"
- cloudify_ims reporting fixes
+ minor fixes
* unknown => real test case names
* pylint corrections
Change-Id: I75446e4006d41fe1bb25106420910025afa01489
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Build euphrates iso for deploy
Change-Id: I68e3caede7b209a7d1afe9ea46e49686daf83147
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Apex: Fixes iso verify depending on previous build workspace
There is a bug where if there are multiple builds queued and daily build
completes, the following iso verify job will try to use the workspace of
the completed daily build to get the iso file. However, if another
build job has already started it may clean and overwrite the workspace
of the daily build job, and the iso verify job will fail because the
file is now gone. This makes the build job copy the iso to a tmp
directory for apex iso verify to consume.
This should be safe since only one daily can run at a time on the host
and daily jobs build and iso verify have to always execute on the same
node.
Change-Id: Ie8e32c4abefbc311e505688d6da2b26ae08ed98f
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Dovetail Add huawei-pod7 to run Compass danube job"
- Dovetail Add huawei-pod7 to run Compass danube job
Compass will use huawei-pod7 to run all danube jobs.
Dovetail add this pod.
Change-Id: Id184d33665e19a8469e600df04759b43005df157
Signed-off-by: xudan <xudan16@huawei.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "compass4nfv: Enable Euphrates jobs & triggers"
- compass4nfv: Enable Euphrates jobs & triggers
Change-Id: Ic5b88c7581879dbf0b72eaf6dbe3ad9c86b17f3c
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
* Update docs/submodules/releng from branch 'master'
- nfvbench: Enable docker image builds for stable/euphrates
Change-Id: I23ea156d9bbfa42c7bbf8dada344ded96b41e2e4
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "fuel-deploy.sh: Fix unbound variable for stable/E"
- fuel-deploy.sh: Fix unbound variable for stable/E
Change-Id: I5a8f02944e346319d6c5d4fca10ddc54503e82d7
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "[Functest] Support functest-suite with Alpine containers"
- [Functest] Support functest-suite with Alpine containers
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "kvmfornfv: Disable jobs running on intel-pod10"
- kvmfornfv: Disable jobs running on intel-pod10
Change-Id: I418f4f2b5f4b28acb9ed39f4f512dc59a4a6f012
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Bugfix: Change http_pass to proxy_pass"
- Bugfix: Change http_pass to proxy_pass
http_pass is wrong for nginx, we need to change it to proxy_pass
Change-Id: Ib679b36a4a139c02647564719e1cfc49a9f376a2
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Run CI Security Gate Check on all OPNFV Builders
Enable the security gating check to run on all machines labled
'opnfv-build'. This will allow the job to run as long as one of these
machines are online.
JIRA: RELENG-313
Change-Id: Icc792f7732c6cc3ca49bd8db32027fc146f8b1cd
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
* Update docs/submodules/releng from branch 'master'
- Change Anteater Report Directory Permissions
Setting this to allow all users to read/write the permissions enable the
container to write to the volume mounted reports directory even though
it is owned by the Jenkins user.
JIRA: RELENG-313
Change-Id: Ib26e9b98cd17607c98a180888593c42376458f7f
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "bugfix: autoupdate failed due to mingle with watchdog"
- bugfix: autoupdate failed due to mingle with watchdog
1. In the original design, if the auto-job starts soon after
the watchdog starts, the auto update might be mingled with
connectivity check, which may lead to update failure. so instead,
the connectivity is checked first, if failed and module is not in deploying,
restart module.
2. only automate-docker-deploy job will impact the container status during
auto-job, so substitue auto-job status check with automate-docker-deploy's
3. the watchdog is not only for testapi, but also for reporting, and
all docker container server deployed in testresults.opnfv.org, so move it under
utils/test/opts, which is leveraged to store tool-sets employed for testing tools.
Change-Id: I766f3a534a3d510ce7509d4e742150150ccd8f54
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "refactor one click deployment in testapi"
- refactor one click deployment in testapi
substitue docker-compose.template with string description,
so that user can wget deploy.py and execute directly.
Change-Id: I9703a1c8dfbdc46470561d54c6663e3728540162
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Functest: Introduce building image job for euphrates"
- Functest: Introduce building image job for euphrates
To build apline images for euphrates
Change-Id: I63d77c99306aed263e220c2a0cd27ee2cca1ecb9
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "[QTIP]Enable qtip validate jobs for euphrates"
- [QTIP]Enable qtip validate jobs for euphrates
Change-Id: I8a138d6cdcfa055260fc25fa909b28d192d5c98f
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "fuel, armband: Enable Euphrates jobs & triggers"
- fuel, armband: Enable Euphrates jobs & triggers
Change-Id: Id47f61c950e1cc036e32e8efe2e2b55193e7c49e
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "add one click deployment of testapi and reporting"
- add one click deployment of testapi and reporting
leverage docker compose to deploy testresults set
testapi/reporting/mongo
usage:
python one_click_deploy.sh -tp 8082 -rp 8084 -tl http://host_ip:8082
Change-Id: I8dfb868637749b82ec86e58220376b03ad50664d
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Add functest return status in Alpines"
- Add functest return status in Alpines
So far we had 2 approaches:
* return Functest CI status: can be OK even if tests are FAIL
* return Functest Test status: can be FAIL even if all Functest tests are OK
(Fail in onboaraded tests)
A 3rd way is possible thanks to [1].
We consider only Functest status and Functest tests for the return statement
the return will be FAIL only if
* error in the framework
* error in Functest Tests
So concretely, if promise, Doctor can be FAIL, if Functest tests are OK, the
return will be PASS
[1]: https://gerrit.opnfv.org/gerrit/#/c/42245/
Change-Id: I6c7fbe99d888e43700ddb2dfc9bfd6cc9bfbaed6
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Reset the trigger time of Apex danube job on huawei-pod4
The old time is "0 12 * * *", need to set it to "0 1 * * *".
Change-Id: Id568dcb638202612ef8d7a9464d71952a95bffe8
Signed-off-by: xudan <xudan16@huawei.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Add Euphrates pages for reporting"
- Add Euphrates pages for reporting
Change-Id: Iee4c54801d839be949495360141d4ae9353e5ecc
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Functest: Introduce building image job for euphrates"
- Functest: Introduce building image job for euphrates
Change-Id: I9e4aab444490b7a85d2fd24344045452a62a0bcc
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Bug Fix: Using library for urlencode"
- Bug Fix: Using library for urlencode
Changes to method call _set_query
Change-Id: I95837df57cc98c21ff5d95d9753269490c025dd3
Signed-off-by: utkarshrai98 <utkarshrai98@gmail.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Dovetail will not trigger apex test on huawei-pod4"
- Dovetail will not trigger apex test on huawei-pod4
1. Jobs to deploy Apex danube has been merged.
This job will deploy Apex and then run Dovetail.
2. So Dovetail don't need to run test on huawei-pod4,
because it will be triggered by Apex deploy job.
JIRA: DOVETAIL-503
Change-Id: I49850a6c45e977ee3e5e8ad246b90a3dbd16884c
Signed-off-by: xudan <xudan16@huawei.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Introduce Euphrates Jobs
Adds stable/euphrates branch for StorPerf ARM jobs that were
enabled for existing master
Change-Id: I4f16097575367e8921e1f25201e57c3af5cd9d19
Signed-off-by: mbeierl <mark.beierl@dell.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "fuel-deploy.sh: mv lab-config repo to TMPDIR"
- fuel-deploy.sh: mv lab-config repo to TMPDIR
Change-Id: Id942f7d2e6e1bbbdb9b15a7c6951ca2f0ba437db
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
* Update docs/submodules/releng from branch 'master'
- [QTIP] Enable qtip docker build image job in euphrates
Change-Id: I01eb67919aa489c47d34976f9587f3187059d2b3
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Apex: Renables async builds and fixes blocking bug"
- Apex: Renables async builds and fixes blocking bug
Previously we had apex-verify-master running multiple instances on
virtual-slaves. Apex-verify-master would kick off a build on our build
server, and then apex-verify-master would execute deploy multijob and
then functest multijob. However we found a bug where jenkins build
blocker would see that a deploy finished on the virtual slave, and then
execute functest multijob as well as deploy multijob (for the next
verify job) at the same time.
This patch adds a parent job apex-virtual-{stream} which calls deploy
and functest multijob and will block correctly. It also renables having
more than 1 apex-verify job running at a time on the virtual slaves.
Change-Id: Id15b2415407fc3318f333e3dfc59076d04db4ffb
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Fix Yamllint violations for jjb/armband"
- Fix Yamllint violations for jjb/armband
JIRA: RELENG-254
Change-Id: I1c658e0af40d2973301b33f760d7fd420e80f253
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Create jobs for euphrates"
- Create jobs for euphrates
Change-Id: Ia705bd9c16ca934bc781e558b27feafa89b3bff0
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Create jobs for euphrates"
- Create jobs for euphrates
Change-Id: Iff9bd7601a59d7e1bad259c74fc792081505f679
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|