summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2018-05-17Adding sysstat xmlstarlet and facterAric Gardner2-0/+6
Adding lf global jjb deps to ansible build server job Change-Id: If71a9cf68c6011a6f6c283e2296a17f211255286 Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
2018-05-17xci: Fix scenario determination for changes coming to releng-xciFatih Degirmenci1-25/+42
Earlier change took the possibility of dynamically determining the default scenario. This change puts part of it back which is based on the changed installer and/or other changed files. Change-Id: Ie6d9a9b0622ac4ae5ff0cf0e679fd26beed51747 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-05-17Merge "Combine generic and external scenario determination to one"Fatih Degirmenci1-51/+29
2018-05-17Merge "jjb: xci: Do not check for the WORKSPACE variable"Fatih Degirmenci1-2/+2
2018-05-17Combine generic and external scenario determination to oneFatih Degirmenci1-51/+29
Previously we were determining the impacted generic scenario by looking into changeset in releng-xci. Since we moved the scenarios to releng-xci-scenarios, this is not needed anymore and same function can be used for determining the scenario. Change-Id: I06a65599e03dff4016d0d9d78116e505d84b5061 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-05-17jjb: xci: Do not check for the WORKSPACE variableMarkos Chandras1-2/+2
The WORKSPACE variable is always set so we do not need to check it in the script. Change-Id: I33d2e17b9a4a7b262c781c7442cc69c2433f8729 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-05-16Rename files under jjb from 'yml' to 'yaml'Trevor Bramwell110-2/+2
global-jjb only supports the .yaml file ending for jjb jobs. Instead of waiting for a release we're going to rename the files. Change-Id: Icf3339eacd2320c583333e02250998cf6b1881f7 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-05-16Use Global-JJB for Releng merge/verify JobsTrevor Bramwell2-116/+9
Replaces the releng templates: - releng-verify-jjb - releng-merge-jjb With the job group '{project-name}-ci-jobs' which includes: - releng-jjb-verify - releng-jjb-merge - releng-jenkins-cfg-merge - releng-jjb-deploy JIRA: RELENG-397 Change-Id: If8160a67d8d665dcb8f86b6649288a710cc0fe13 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-05-16Merge "Clone Releng with submodules to include jjb"Trevor Bramwell2-25/+13
2018-05-16Clone Releng with submodules to include jjbAric Gardner2-25/+13
Needed for JJB verify and Merge to work. These jobs are going away, but first we need to get a verified +1 from jenkins Also remove releng-comment-jjb its unused Change-Id: Ice2ad625f87f1d9c841979ede4bb1943110691c8 Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
2018-05-15Update global-jjb to v0.17.0Trevor Bramwell1-0/+0
Since the commit submodule commit can't be set to an explicit tag, please see this link[1] for verification that 90e4e825b3d0ac5959122c50e457419ad0cfe137 is v0.17.0. [1] https://gerrit.linuxfoundation.org/infra/#/c/9386/ JIRA: RELENG-398 Change-Id: I9d4e90cc073c8b9cb741735a2ba582a2c7882087 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-05-15Merge "Disable git tagging during Jenkins git clone"Trevor Bramwell1-0/+4
2018-05-15Merge "jjb: xci: xci-run-functest: Switch to dynamic inventory"Markos Chandras1-1/+1
2018-05-15jjb: xci: xci-run-functest: Switch to dynamic inventoryMarkos Chandras1-1/+1
We no longer have static inventory files per installer and flavor so we need to switch to the dynamic inventory option. Change-Id: I5b8bf800264b1b297b61d09d010552cd22636627 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-05-14Disable git tagging during Jenkins git cloneTrevor Bramwell1-0/+4
Even with per-build-tag set to false, JJB 1.6.2 does not seem to remove 'Create tag for each build' from the git-scm settings. Though the option is deprecated it is still supported, so setting both of these should disable tagging when Jenkins clones a git repo. Change-Id: I5977149ad581df67d938ce2b46794d47c5e06fe3 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-05-14Merge "Specify CI jobs time intervals for armband"Aric Gardner1-6/+6
2018-05-14Merge "Releng PTL change to Trevor Bramwell"Fatih Degirmenci1-10/+10
2018-05-11jjb: xci: Connect new releng-xci-scenarios repositoryMarkos Chandras2-2/+2
The scenarios have been moved from the releng-xci to releng-xci-scenarios repository so we should connect Jenkins to that repo as well. Change-Id: Ifcb4f02b8532dd94c8a622185328f7316e726c6b Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-05-10Yardstick needs export EXTERNAL_NETWORK to envxudan1-0/+1
Change-Id: I380008fe2cadbce8f6b7b1f84c9f3bf720df485e Signed-off-by: xudan <xudan16@huawei.com>
2018-05-10jjb: xci: xci-start-new-vm: Fix passing YAML var files to AnsibleMarkos Chandras1-1/+1
When passing a YAML variables file to Ansible, we need to prefix it with '@'. Change-Id: I884f4698a1033cca9ad55bf3592e1dd817273f81 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-05-09jjb: xci: xci-start-new-vm: Fix gerrit variable for git SHAMarkos Chandras1-2/+2
The gerrit variable for the git SHA is GERRIT_PATCHSET_REVISION instead of GERRIT_CHANGE_ID. We also need to export the XCI_ANSIBLE_PARAMS variable. Change-Id: I206820f1155a4876fb7d87cc0b5ae1b8afb06bd6 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-05-09Specify CI jobs time intervals for armbandCharalampos Kominos1-6/+6
Since there is only one CI pod available for armband at the moment, we instruct CI to run only one job per day. Four jobs for master branch and 3 for stable branch. Change-Id: I645a98d922c00b2237cb5aeeb280d00ecdf0e288 Signed-off-by: Charalampos Kominos <Charalampos.Kominos@enea.com>
2018-05-09Merge "jjb: xci: xci-start-new-vm: Create scenario overrides file"Markos Chandras1-3/+12
2018-05-08Bugfix: Dovetail failed to upload results to artifactsxudan1-2/+4
That's mainly because of that 1. The owner of all results files are root:root 2. Sometimes there are some files that can only be read by root 3. User jenkins failed to upload these files Solutions: 1. Change the owner to be jenkins:jenkins 2. Remove these files which are useless for users Change-Id: I0b5e72e8d5045c7e0d64e32a13ba559612460a84 Signed-off-by: xudan <xudan16@huawei.com>
2018-05-08jjb: xci: xci-start-new-vm: Create scenario overrides fileMarkos Chandras1-3/+12
Pass scenario information using the new override mechanism. This patch depends on the matching releng-xci change https://gerrit.opnfv.org/gerrit/#/c/56643/ Change-Id: Ib8473249e424f259f5757ebdaed7d73fa4b0adce Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-05-08Merge "JJB 2.0.X does not allow scenario to be passed here"mei mei1-6/+2
2018-05-07Releng PTL change to Trevor BramwellTrevor Bramwell1-10/+10
I am nominating myself as PTL of Releng following Fatih's announcement to step down. See this email thread for context: https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2018-May/021142.html Change-Id: I6426a612378143d7829420cc9cf254021ce1eeae Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-05-07Merge "Enable Local Docs builds by using LF Docs Conf"Trevor Bramwell5-1/+20
2018-05-07Merge "Disable vnf runs for aarch64"Aric Gardner1-2/+2
2018-05-04Merge "Disable Snaps Fraser Verify Job"Trevor Bramwell1-1/+1
2018-05-04Merge "[yardstick] debug dump image ID"Trevor Bramwell1-0/+1
2018-05-04Disable vnf runs for aarch64Delia Popescu1-2/+2
Functest VNF tests are not adapted for aarch64. The tests can be reactivated when they are adapted to execute on aarch64. JIRA: FUNCTEST-964 Change-Id: I2413a6eff831c8dd2751b7bc73ad583f55a00dcf Signed-off-by: Delia Popescu <delia.popescu@enea.com>
2018-05-04Merge "fuel, armband: basic healthcheck in verify jobs"Trevor Bramwell2-68/+42
2018-05-04JJB 2.0.X does not allow scenario to be passed hereagardner1-6/+2
With this change releng/jjb/* now passes on: Jenkins Job Builder version: 2.0.1 and 1.6.2 Error: TypeError: write() argument must be str, not list Explanation: in jjb 1.6.2 it would allow the list in and then the job would convert the list into a literal string of "['var1', 'var2']" - 'compass-{scenario}-{pod}-daily-{stream}' Can have scenario passed, {scenario} is part of the job name so it knows which scenario to add. - 'compass-deploy-{pod}-daily-{stream}' cannot have scenario passed, there is not one job generated per scenario so its tryting to add "['senario1', 'scenario2', 'etc']" into the {scenario} value, which is not allowed. This worked on jjb 1.6.2 becasue we overwrite the scenario information later: - trigger-builds: - project: 'compass-deploy-{pod}-daily-{stream}' predefined-parameters: | DEPLOY_SCENARIO={scenario} jjb/armband/armband-ci-jobs.yml is very simillar to this job and passes a default, which works, so that is what I have done here: - string: name: DEPLOY_SCENARIO default: 'os-odl-nofeature-ha' addendum: removed scenario: '{scenario}' from 'compass-{scenario}-{pod}-daily-{stream}' even though it is valid, Trevor rightly pointed out that there is nothing to consume this value. Change-Id: I134b2bd5888dcdfa5b768a7db2bdc98ad32ec28e Signed-off-by: agardner <agardner@linuxfoundation.org> Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-05-02Apex: Fix resources/images directory usage with deployTim Rozet1-3/+2
Change-Id: If50ad310049edca687da8e0acf412a7e1eacd2b6 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-05-02Apex: disable iso verify for master branchTim Rozet1-0/+5
Change-Id: I46753983e1fb37300df70700c474c3dda3532ffa Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-05-02Apex: Update for master upstream deploymentsTim Rozet5-57/+99
Change-Id: I92635178ddc354dd7773cd372a34d46f5ee0bf2a Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-05-02Add Bottlenecks Fraser Docker Push JobYang Yu1-0/+4
Change-Id: I4d6c4015ca36f743dadbb6524a1ca8d5619ce3d6 Signed-off-by: Yang Yu <Gabriel.yuyang@huawei.com>
2018-04-30Add release notes in releases/fraser/functest.yamlCédric Ollivier1-0/+2
Change-Id: I0384563e5e663ea485626562df5ee49815b95817 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-04-28Merge "Tag SDNVPN for Fraser 6.0"Aric Gardner1-0/+5
2018-04-28Merge "Tag Stor4NFV for Fraser 6.0"Aric Gardner1-0/+7
2018-04-28Merge "Update Clover tags Clover for Fraser 6.0.1"Aric Gardner1-0/+3
2018-04-28Tag OPNFVDocs for Fraser 6.0Trevor Bramwell1-0/+5
This is tagged at the last merged docs patch to stable/fraser Change-Id: I0d976cd947621ceab3a15df8ea98bdc245fe93fc Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-04-28Merge "Fraser 6.0.0 tag"Trevor Bramwell1-0/+5
2018-04-28Merge "Fraser 6.0.0 tag"Trevor Bramwell1-0/+5
2018-04-28Merge "Fraser 6.0.0 tag"Trevor Bramwell1-0/+5
2018-04-28Tag Apex for Fraser 6.0agardner1-0/+14
The last commit I had to revert, as the refs were put under branches branch should never change and indicates where the branching happens. I have taken those refs and put them in the releases section Change-Id: I8026b331b18cde18c08ed1bef79d291c3a7ffce8 Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-04-28Merge "Revert "Apex: update sha commit hashes for Fraser""Aric Gardner1-4/+4
2018-04-28Revert "Apex: update sha commit hashes for Fraser"Aric Gardner1-4/+4
This reverts commit 583c715b4c5320bdd6e0b09b68af852d8660dc14. Change-Id: I63c99606804c4c02b1e8aff91937c62916137bc9
2018-04-28Update Clover tags Clover for Fraser 6.0.1Trevor Bramwell1-0/+3
Add the opnfv-6.0.1 to the current commit, and lists opnfv-6.0.0 as being tagged on the previous one. Change-Id: I01b3efb6fe04b3dcf32ef2c01315ecb34fb30133 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>