summaryrefslogtreecommitdiffstats
path: root/jjb/global
AgeCommit message (Collapse)AuthorFilesLines
2018-02-08Merge "Apex: Cleanup slave/slave-label configuration"Tim Rozet1-37/+1
2018-02-08Apex: Cleanup slave/slave-label configurationTim Rozet1-37/+1
Changes Include: - Remove defining 'node:' per job template and use slave-params defaults - Gate job was using daily/build slave, when it should be using virtual slave Change-Id: Iec2321801daef1b1fa40724a244bf2f6edf36c6e Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-02-08Merge "fix sed command in macros"Aric Gardner1-2/+2
2018-02-07Apex: remove setting node in slave-paramsTim Rozet1-9/+0
We only want to specify slave-label, not sure why we are specifyign node here and in jjb for Apex. Change-Id: I184df37836039887f47e7d6141c89f8dd9cd014f Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-02-07fix sed command in macroswutianwei1-2/+2
The char "/" was included in $msg. It will have issue "sed: -e expression #1, char 7: unknown option to `s'" We can substitute '/' with '#' in sed command to solve this issue Signed-off-by: wutianwei <wutianwei1@huawei.com> Change-Id: I1308e9b1b2111f0033df119e4465df4dda27eac0
2018-02-05Update the postscriptbuild usageJulien1-1/+2
when we want to trigger the scipt only when previous builders fail, we should also set the other macro 'script-only-if-succeeded' to false, the default value is true. script-only-if-succeeded: false script-only-if-failed: true Change-Id: Ifdca24ea8d076dd4e16ef466705e0167b97cf1df Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
2018-02-02Set the lint job shell to /bin/bashTrevor Bramwell1-0/+5
The default builder in Jenkins is '/bin/sh -ex'. Because of this lint jobs are failing that we assume won't as everywhere else we've used /bin/bash and explitily set options when needed. Explicitly setting these jobs to use /bin/bash should keep Jenkins from failing builds without reporting the lint results. Change-Id: Ibe6cad979d6dcf30e7991873c9ac446ae3bf3a8b Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-01-31Merge "adding pike support during installation."Fatih Degirmenci1-2/+2
2018-01-29Merge "[fuel] Retire 'BRIDGE' slave param"Aric Gardner1-4/+0
2018-01-26Set lint jobs to run concurrentagardner1-1/+1
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 masteragardner1-3/+3
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-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 Mibu1-97/+61
2018-01-26[fuel] Retire 'BRIDGE' slave paramAlexandru Avadanii1-4/+0
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-24add 'lint-all-code' as wrapper of lint buildersRyota MIBU1-97/+61
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 MIBU1-27/+7
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 Mibu1-0/+4
2018-01-23Add GERRIT_REFSPEC to 'project-parameter' MacroTrevor Bramwell1-0/+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-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-16Merge "Docker Builds from Git Tag"Trevor Bramwell1-1/+1
2018-01-15Add macro for reporting the provision resultJulien2-0/+51
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-11Merge "Reduce Basic Job Duplication"Trevor Bramwell1-0/+46
2018-01-11[daisy] Enable ovs_dpdk scenarios jobs001845321-0/+23
Change-Id: I5193285493926fcf82779f12d491a118bc83baa7 Signed-off-by: 00184532 <lu.yao135@zte.com.cn>
2018-01-10Reduce Basic Job DuplicationTrevor Bramwell1-0/+46
In the initial formation of projects we found it easy to copy job definitions to provide project a baseline job config to work off. This has led to a lot of duplication and misalignment with the gerrit triggers and default build server tag to be used. Collapsing these jobs into a job-group containing the stream and a verify job per-stream, should help reduce this duplication. Change-Id: Icb366487590a145be4cbfc0637a8d86a6d9b7cec Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-01-10Merge "Backup Pharos Dashboard Data"Trevor Bramwell1-0/+16
2018-01-09Docker Builds from Git TagTrevor Bramwell1-1/+1
Facilitates the creation of docker images from tags pushed to Gerrit, which should remove the need to manually trigger 'tagged' builds. Fixes a typo in the 'gerrit-trigger-tag-created' macro, replaces 'RELEASE_VERSION' with 'GERRIT_REFNAME', and adds the tag-trigger to docker builds. Change-Id: I6d8f8f34b1c51d74bb98211dfae21c37cf9356fa Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2017-12-21xci: Create periodic jobs for upstream osaFatih Degirmenci1-0/+10
This change takes xci-verify-jobs as base and adjusts osa-periodic jobs to ensure they do what they are supposed to. The structure of periodic jobs is pretty similar to xci-verify-jobs and the differences comparing to them are - OPENSTACK_OSA_VERSION is set to master. - SCM type changed to git-scm from gerrit - Voting is removed. - Triggering will be done using pollscm to ensure we only run jobs when something changes upstream. Triggers are not enabled yet until the basics are verified working. This change requires https://gerrit.opnfv.org/gerrit/#/c/49275/ in order for periodic jobs to work as expected. Further changes are needed to finalize the structure. Change-Id: I8f6519ccce93e6b8b65509638294419459fd36e8 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2017-12-07[Compass4nfv] run centos in intel-pod17wutianwei1-0/+14
Change-Id: Ifbe959d178781c14a9d32db78d84972d2505c8dc Signed-off-by: wutianwei <wutianwei1@huawei.com>
2017-12-05Backup Pharos Dashboard DataTrevor Bramwell1-0/+16
Use an alpine container to mount the pharos_data volume and create a backup in the home directory on the system. Change-Id: If6700a8c4cd19a6c4b854efc54225d8f6b973aaa Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2017-11-30Update Releng Testresults PTL MacroTrevor Bramwell1-1/+6
Send emails to Serena after weekly Anteater scans on the releng-testresults repository. Change-Id: Ic4d61137ea8e30985f5330651e8d2da37b71fca3 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2017-11-29Fix Anteater Weekly Reporting JobTrevor Bramwell1-26/+18
- Does not output the full scan to the console log - Updates the email-ext defaults to include any *.log file in the root of the workspace. This should include securityaudit.log - Adds 'GERRIT_REFSPEC' to the list of job parameters as required by 'git-scm-gerrit' - Fixes email-ptl macros so projects with extra repos have the proper recipients. Change-Id: Ibf22bf0683fc1f88de07ef3bb4717769c6ea0174 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2017-11-29Merge "Email Weekly Anteater Reports to PTLs"Trevor Bramwell2-0/+513
2017-11-27Email Weekly Anteater Reports to PTLsTrevor Bramwell2-0/+513
Completely replaces the current weekly security scan job. Instead of publishing weekly security scan reports they will be emailed to individual project PTLs. Uses a modified copy of 'anteater-security-audit.sh' to ensure the security scan job is not affected in this change. A later change will be made to merge the file back in and update the jobs. This is why 'anteater-parameters' are added to both jobs-templates. Change-Id: Ia8ebffbfce7a2d4feb83ef68ff0ab0c7bb4d2104 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2017-11-24Fix Doctor run on 'doctor-{installer}-verify' slaveDelia Popescu1-0/+6
Change-Id: I65a2a3c6643cba870eec2f794199bb824c6b868c Signed-off-by: Delia Popescu <delia.popescu@enea.com> Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2017-11-22adding pike support during installation.Narinder Gupta1-2/+2
Change-Id: I31a1f6d1de5796c82bcf7e001451ec3ca0d3b1ce Signed-off-by: Narinder Gupta <narinder.gupta@canonical.com>
2017-11-13Merge "fix the bug of patch verify"Trevor Bramwell1-1/+6
2017-11-10Remove Artifacts JSON JobTrevor Bramwell1-22/+0
As far as I know the site that consumed this resource was never actually published, and given this runs frequently on master, removing it should save resources. Change-Id: I383fcffcef98e0e12a38d15dcb1204419283b833 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2017-11-09fix the bug of patch verifywutianwei1-1/+6
If one patch don't modify the "yml" or "yaml" file, the script will exit with 1 at egrep "ya?ml$", then mark build as failure. In my opinion, if not modify the "yml" or "yaml" file, the yamllint should be successful. So we need mark the result of egrep "ya?ml$" as true, then judge the $YAML_FILES. Change-Id: I8abcadc9e4c85935ac7b20cdf54713b9800108ba Signed-off-by: wutianwei <wutianwei1@huawei.com>
2017-11-08Merge "Add qtip job to pod zte-virtual6"Aric Gardner1-0/+15
2017-11-08Add qtip job to pod zte-virtual6Taseer Ahmed1-0/+15
JIRA: QTIP-282 Change-Id: If765bfa01a1dab987409c311f3a718bffea76797 Signed-off-by: Taseer Ahmed <taseer94@gmail.com>
2017-11-08Sudo pip install.agardner1-1/+1
not in a venv, so build fails if called by jenkins user without sudo Change-Id: I612a20777cc70a33542f767a63075939782e3201 Signed-off-by: agardner <agardner@linuxfoundation.org>
2017-11-08Merge "Update Yamllint Version"Trevor Bramwell1-1/+1
2017-11-02Merge "Switch yamllint job to only run against new files"Trevor Bramwell1-7/+8
2017-11-02Need to change directory check for new docs verifyagardner1-1/+1
old dir is no longer generated grab dir created by tox -e docs Change-Id: If52e931f6abdc8dcb39fbe7aac3c6b3342ce81c8 Signed-off-by: agardner <agardner@linuxfoundation.org>
2017-11-02Merge "Move all doc verfication to docs-verify-rtd-*"Aric Gardner1-61/+1
2017-11-01Move all doc verfication to docs-verify-rtd-*agardner1-61/+1
Ready for review (tested locally) 1) remove opnfvdocs-daily-{stream}: We don't need a timed docs build. and it did not build anything usefull 2) remove opnfv-docs-verify-{stream}: This uses depreciated and unmaintained opnfvdocs/scripts/docs-build.sh It does not clone submodules and gives no usefull feedback but it does post to artifacts and give a gerrit comment move that functionality to docs-*-rtd-* 3) remove opnfv-docs-merge-{stream}: does not upload anything meaningful 4) remove macro upload-generated-docs-to-opnfv-artifacts: is no longer needed since we use read the docs 5) improve docs-verify-rtd-{stream}: generate single page html and post to artifacts send gerrit commment with location of single page html, errors (like malformed table) are embedded nicely in the single page output and give devs a single source of feedback on their work 6) improve docs-merge-rtd-{stream}: this job now needs to remove review documenation created by docs-verify-rtd-{stream} TODO, after this is merged: remove now unused opnfvdocs/scripts/docs-build.sh Change-Id: I802eb11712d42555d34f986d061bf0dfc623c1e9 Signed-off-by: agardner <agardner@linuxfoundation.org>
2017-11-01Merge "Add Gerrit Trigger on Tag Creation"Fatih Degirmenci1-0/+14
2017-11-01Rename zte-pod4 to zte-virtual5zhihui wu1-3/+3
JIRA: QTIP-280 Change-Id: Ie588c3e38af82fe9b2de8bb01549a1c9249d54ff Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
2017-10-31Add Gerrit Trigger on Tag CreationTrevor Bramwell1-0/+14
We should be able to capture a tag creation event by triggering on 'ref-updated' but looking specifically at the 'refs/tags/' branch prefix. Though this will trigger a build against a specific tag, scripts will still need to examine the GERRIT_REFSPEC to determine the tag name. Change-Id: Ic18a3e11530fb71735431240f93d2074dacf4e1c Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2017-10-19Integrate yardstick on daisy master branchAlex Yang1-0/+4
JIRA: DAISY-9 1. Trigger yardstick job in daisy-baremetal-daily-master on zte-pod3 2. Add daisy pods in yardstick 3. Add EXTERNAL_NETWORK in installer params Change-Id: Ia8e69e503102c1fb282d6d2c5acac2ac3cbfe747 Signed-off-by: Alex Yang <yangyang1@zte.com.cn>