summaryrefslogtreecommitdiffstats
path: root/jjb
AgeCommit message (Collapse)AuthorFilesLines
2018-01-30Merge "Pull the image before running functest container"mei mei1-0/+3
2018-01-29Merge "[fuel] Retire 'BRIDGE' slave param"Aric Gardner2-6/+2
2018-01-29Pull the image before running functest containerLinda Wang1-0/+3
Change-Id: Iebd8a9b558486927c25735d266d3557f91e26a15 Signed-off-by: Linda Wang <wangwulin@huawei.com>
2018-01-28[fuel] Retire 'virtual_kvm' overrideAlexandru Avadanii1-4/+0
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>
2018-01-26Set lint jobs to run concurrentagardner2-1/+5
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>
2018-01-26Linting should be done on a build server, not on masteragardner2-3/+17
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>
2018-01-26[daisy] Run functest daily jobs on zte-pod9Alex Yang1-0/+5
Change-Id: Ib61cb40b04eed23ad276f261645d83ce7cf00629 Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
2018-01-26Fix typo in lint-initAlex Yang1-1/+1
Change-Id: I310c4f2e46a26b35eeafef2dfc8670d70ace0575 Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
2018-01-26Merge "add 'lint-all-code' as wrapper of lint builders"Ryota Mibu4-113/+114
2018-01-26[fuel] Retire 'BRIDGE' slave paramAlexandru Avadanii2-6/+2
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>
2018-01-25Merge "[fuel] deploy: Stop using securedlab for master"Aric Gardner1-7/+11
2018-01-25Merge "Pharos Dashboard: Deploy once config is in place"Trevor Bramwell1-0/+1
2018-01-25Merge "[doctor] fix node-label setting"Ryota Mibu2-74/+21
2018-01-25xci: Run functest as part of xci-merge jobsFatih Degirmenci2-3/+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-24Add schema valiadator to jinja checkeragardner1-0/+8
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>
2018-01-24[fuel] deploy: Stop using securedlab for masterAlexandru Avadanii1-7/+11
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>
2018-01-24add 'lint-all-code' as wrapper of lint buildersRyota MIBU4-113/+114
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>
2018-01-24[doctor] fix node-label settingRyota MIBU2-74/+21
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>
2018-01-24Merge "Add GERRIT_REFSPEC to 'project-parameter' Macro"Ryota Mibu4-12/+4
2018-01-24Merge "[daisy] Skip signing kolla images"Serena Feng1-26/+0
2018-01-24Merge "Add lf-pod4 and lf-pod5 to slave params"Ryota Mibu1-0/+38
2018-01-23Output version before Docker buildsTrevor Bramwell1-2/+2
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>
2018-01-23Merge "Disable Interactivity for and enable Pharos Backup"Trevor Bramwell1-1/+3
2018-01-23Add GERRIT_REFSPEC to 'project-parameter' MacroTrevor Bramwell4-12/+4
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>
2018-01-23Merge "docker: update name and dockerfile location for barometer collectd ↵Fatih Degirmenci1-11/+6
image. change build directory to fix build's copy errors "
2018-01-23xci: Skip jobs if the scenario is not supported on a distroFatih Degirmenci4-0/+28
Change-Id: I22d2327558ee1d19d04775da6abf1b3eed5b357a Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-01-22xci: Do not clone and checkout scenario repo if it is releng-xciFatih Degirmenci1-1/+1
Change-Id: I48cdbfbd5b7746e75565d318616e9c580b5ba156 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-01-22xci: Clone releng-xci repo for phase jobs as wellFatih Degirmenci1-1/+6
Forgotten to fix phase jobs. Change-Id: I50c525089d6d3b4f28650ad78b8810817aaf150e Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-01-22xci: Clone the repo and checkout the patch for testingFatih Degirmenci2-0/+9
Change-Id: Ie1c2f76b6043133c3821272040b1a2a38de29035 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-01-22xci: Always clone releng-xci into WORKSPACE for merge jobsFatih Degirmenci1-1/+6
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>
2018-01-22xci sfc: Enable post merge deploymentFatih Degirmenci2-19/+34
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>
2018-01-22xci: Convert execute shell scripts to external scriptsFatih Degirmenci5-77/+128
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>
2018-01-19Merge "RFC: Set the basic structure for post merge jobs"Fatih Degirmenci1-0/+252
2018-01-18Merge "Disable the triggers for euphrates in armband"Aric Gardner1-4/+4
2018-01-18Disable the triggers for euphrates in armbandCristina Pauna1-4/+4
Change-Id: I738b4eb712bc85ee3327a9be55f4990000ff28c8 Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
2018-01-18[daisy] delete tmp dir with sudoAlex Yang1-1/+1
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>
2018-01-17Pharos Dashboard: Deploy once config is in placeTrevor Bramwell1-0/+1
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>
2018-01-17Merge "Create job to deploy Pharos Dashboard"Trevor Bramwell1-0/+35
2018-01-17Add lf-pod4 and lf-pod5 to slave paramsTrevor Bramwell1-0/+38
Change-Id: I3ca61f015c07cbf3bd67acd7972d9a1e0011f21d Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-01-17Merge "bugfix: pass functest parameters to builders"Ryota Mibu1-54/+62
2018-01-17bugfix: pass functest parameters to buildersdongwenjuan1-54/+62
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>
2018-01-16[daisy] Add '|' for more than one predefined-parametersZhijiang Hu1-3/+3
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>
2018-01-16docker: update name and dockerfile location for barometer collectd image.Gordon Kelly1-11/+6
change build directory to fix build's copy errors Change-Id: I3bc4f929156c7c04cc93822d28b0a64991f18595 Signed-off-by: gordonkelly <gordon.kelly@intel.com>
2018-01-16Merge "Docker Builds from Git Tag"Trevor Bramwell6-16/+21
2018-01-16Create job to deploy Pharos DashboardTrevor Bramwell1-0/+35
Runs docker-compose build & up to recreate containers when code changes, and redeploys the dashboard. JIRA: PHAROS-316 Change-Id: Ie83ae775c55aa9e18069b9988bfd771b5655c14b Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-01-16Merge "The '{is-skip-vote}' is always 'true' for the jobs"Ryota Mibu1-10/+25
2018-01-16Merge "Add macro for reporting the provision result"Serena Feng3-0/+63
2018-01-15Add macro for reporting the provision resultJulien3-0/+63
1. add macro for report the provision result of installers and try it in daisy 2. update according to TestAPI interface Change-Id: Ic041744c917c37fcd84a12a92e927e39106cf18f Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
2018-01-15Merge "Revert "container4nfv: Disable jobs until the project stops changing ↵Aric Gardner1-1/+1
docker version""
2018-01-15Revert "container4nfv: Disable jobs until the project stops changing docker ↵Fatih Degirmenci1-1/+1
version" The project fixed their build script to stop reinstalling docker which downgrades it so the jobs can be enabled back now. https://gerrit.opnfv.org/gerrit/#/c/50603/ This reverts commit c9aac428e09385a5893313a99b6af6652dafd216. Change-Id: I529850be56e30e4fdd66929809628b89e3a2ed8f