Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
CentOS is now supported by os-nosdn-nofeature scenario and it is
time to enable voting for it. For scenarios that do not support
CentOS yet, the jobs will skip running real stuff by exit 0 in
order not to fail the patch.
Change-Id: I86c9e1bb4d66ea84ccfc864186a7ca7c696f8663
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
|
|
Change-Id: I41aef4c9df47a076f8245cc1b466ff4297de0ae8
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
JIRA: COMPASS-579
Add a job to collect log and upload. what the job do
1. run collect-log.sh to get log from rsyslog container
2. copy log.tar.gz from compass-tasks to jumphost
3. upload the log.tar.gz to artifact
Change-Id: Ic2244e33e7ae4b7aa71e15af741191c850982053
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
|
|
|
|
Change-Id: Iebd8a9b558486927c25735d266d3557f91e26a15
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
Now that vPDF support landed in Pharos and Fuel repos, disable the
'virtual_kvm' generic override, so we can load POD-specific PDF/IDF.
JIRA: FUEL-322
Change-Id: I0964220a25d6fe30afcbeb3ad1f020ae76d38e5a
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Liniting is broken, last fix forgot to run linting concurrent
FATAL: The project is configured to NOT run builds concurrent, but the
node parameter [SLAVE_NAME] is configured to trigger new builds
concurrent!
Change-Id: I1eb4bf7279c7af4e01950b89c515e183fbc57b2d
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Linting was broken by this patch
https://gerrit.opnfv.org/gerrit/#/c/50737/
Also added sudo to pip installs, as they are not in a venv
Patch forgot to put linting on build server
so it defaulted to master.
Change-Id: Iba8c1f633fad6d5f3d097f4911f45100c3b43e30
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Change-Id: I310c4f2e46a26b35eeafef2dfc8670d70ace0575
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
|
|
|
|
Only Danube still uses this param, newer branches rely on IDF.
Going forward, the `-B` deploy arg will be deprecated in Fuel.
Do not yet remove BRIDGE slave params from non-CI PODs, as
other installers (or custom Danube jobs?) might still use them.
Change-Id: I6d259299d1e13e8a5da732aca60b1f56b8472af6
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
|
|
|
|
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>
|
|
Alex has extended the jinja checker to valiate the schema
uses jsonschema
Next step is to enable voting on this job.
Change-Id: I3c61eb3addbb3d41093ada486bf9d8b191fb2028
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Instead of cloning securedlab locally and passing it to Fuel deploy
script, rely on Pharos git repo, embedded as a git submodule in Fuel.
Keep old behavior (using securedlab) for stable/{danube,euphrates}.
Depends-on: Ib04e4fb384568a6efd9e78a080857b663521ae88
Change-Id: Ie30879292ae04b641257760de69c900a9eb4ef84
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
OPNFV has common coding style [1]. So, all repos shall be checked by
one generic checker builder/job, eventually.
This patch adds lint wrapper builder 'lint-all-code', and also
refactors all exisiting lint and syntax check builders, following
'lint-yaml-code' builder approach, which only checks modified files.
This approach is nice as it won't require immediate fixes of violations
in whole repo code right after the lint checker job is enabled.
Note that lint jobs are still configured to run against some project
repo, in order to seperate discussion; wheter we should apply this
lint job to all OPNFV repo or not immediately.
[1] https://wiki.opnfv.org/display/DEV/Contribution+Guidelines
Change-Id: Ib4ab3ba5dc08845f3016b8be772f4ed119f11b2d
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
Current doctor verify jobs need to be run on relevant pods which are
specified by slave-label. But, after multijob introduced, the parameter
is not passed to children jobs. Also, 'phase' of project is misleading,
as it isn't multijob's phase.
This patch makes sure each doctor job run on correct pod by updating
node label rule for doctor pod to 'doctor-{installer}-{arch}'.
This patch also merges doctor slave parameter definitions into one,
and deletes unnecessary setting where default are set.
Change-Id: Ic9bf218ae7fb4f9866b510efd1e0ccd19277b78e
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
pick from https://gerrit.opnfv.org/gerrit/#/c/50737
Change-Id: If5b83c656f33af1740df194ba826b6a31ac10355
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
|
|
|
|
|
|
Its helpful to know which version of docker is being used to build a
project when debugging build failures.
Change-Id: I2bb9c5386d1d69e61c4477913f5f0162acd0c47d
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
GERRIT_REFSPEC is always passed by the gerrit-trigger plugin when a job
is triggered by Gerrit. Because it is not explicily defined, there is no
way to manually trigger jobs, as the git clone looks up the list of refs
by GERRIT_REFSPEC.
Being able to manually trigger jobs (with node parameters so they can be
restricted) is very helpful in debugging CI issues.
Change-Id: I8a1d9ea380902fc95f30482e5acb616347709ab1
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
image. change build directory to fix build's copy errors "
|
|
Change-Id: I22d2327558ee1d19d04775da6abf1b3eed5b357a
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: I48cdbfbd5b7746e75565d318616e9c580b5ba156
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Forgotten to fix phase jobs.
Change-Id: I50c525089d6d3b4f28650ad78b8810817aaf150e
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: Ie1c2f76b6043133c3821272040b1a2a38de29035
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
The cloning of the correct version of the repo which the scenario
resides in will be handled by get-opnfv-scenario-requirements.yml
for all the scenarios.
The change proposed for merge jobs will be reflected to verify jobs
as well once it is verified with this.
Change-Id: Icaa99a8b9e981c839969ce556e5af6a9ef6d9da8
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
This change enables the deployment upon merge of a change.
Followup patches will incorporate functest smoke and promotion
which the promotion will most likely be the first one as functest
parts are a bit tricky due to failures while running testing
in VMs.
Apart from the enablement of the deployments, job concurrency is
disabled as well since we should only test one change at a time
and attempt promotion for any scenario in order to ensure we keep
the promotion consistent.
Change-Id: Ib4b5754b6b88f42eab83c656e03773c83068016f
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
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>
|
|
|
|
|
|
Change-Id: I738b4eb712bc85ee3327a9be55f4990000ff28c8
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
Permission denied occured in [1].
[1]: https://build.opnfv.org/ci/job/daisy-deploy-zte-pod9-daily-master/7/console
Change-Id: Ic7e67eed8a121cae0ea2c05ab4cc9005358fcda5
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
Since configuration has shifted out of the docker-compose.yml file and
the workspace gets recreated ever job, the config.env file needs to be
copied into place before each deployment.
JIRA: PHAROS-316
Change-Id: I8c80f1148ad268428defa2f7eb1877d821a11491
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
Change-Id: I3ca61f015c07cbf3bd67acd7972d9a1e0011f21d
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
As doctor CI failed: https://build.opnfv.org/ci/job/doctor-verify-apex-sample-build-x86_64-master/24/console
Functest parameters can not passed to 'functest-suite-builder' to build the job
Change-Id: I34039025bb77e78ce43c21ef7ec67da7583b6e39
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
This tries to solve Job name error [1] which cause functest
failure.
[1] https://build.opnfv.org/ci/job/functest-daisy-baremetal-daily-master/257/console
Change-Id: I89c9a00bcaf0ccb274a18339533bdd99b1134be3
Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
|