summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2018-03-23Merge "xci: Do not trigger merge jobs for INFO.yaml updates"Fatih Degirmenci1-0/+2
2018-03-22xci: Record promotion time in UTCFatih Degirmenci1-1/+1
Change-Id: Id6ea4f8124bdfe8c4233400d216d503fa101b0cb Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-23Merge "Bugfix: command chown failed because LF POD has no jenkins user"mei mei1-2/+2
2018-03-22Bugfix: command chown failed because LF POD has no jenkins userxudan1-2/+2
Command change the file owner failed on lf-pod1 and lf-pod2 with the reason "chown: invalid user: ‘jenkins:jenkins’". Make pod.yaml file can be modified by any user. Change-Id: I1feb108e95c59c228d2aef55862017e9b80bcb73 Signed-off-by: xudan <xudan16@huawei.com>
2018-03-23Merge "Fix RegExp issue for sfc scenario"mei mei1-1/+1
2018-03-23Merge "xci: Record additional promotion metadata for further use"Fatih Degirmenci1-0/+4
2018-03-22xci: Set additional variables in CI test scriptFatih Degirmenci1-0/+3
We need the variables CI_LOOP, BUILD_TAG, and NODE_NAME passed to the deployment to display during functest execution. Change-Id: Ib6709678d760d43927d3cd9f606d2c7e74e724d0 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-22Fix Python3 Errors for Release AutomationTrevor Bramwell1-2/+7
My testing was done using Python 2.7 but the build server running the jobs is obviously running Python3. These changes allow the create_branch.py release script to run against both Python2 and Python3. Change-Id: I02478986ef869ce82ece5b96dbb4b5ed548a2a55 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-03-22Merge "jjb: xci: bifrost-verify: Update location for XCI bifrost scripts"Fatih Degirmenci1-1/+1
2018-03-22xci: Do not trigger merge jobs for INFO.yaml updatesFatih Degirmenci1-0/+2
Change-Id: I16eed2ec0ca1fa659fc449799813c02b19b08174 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-22xci: Record additional promotion metadata for further useFatih Degirmenci1-0/+4
It would be good to point to the link of the job that promoted certain scenario and display promotion date/time so we know when was the last time the scenario has successfully been promoted. Change-Id: I8099cf48f0ba5000cbf7622aa084f863f123eb15 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-22create stable/fraser branch for sdnvpnPeriyasamy Palanisamy1-0/+9
Change-Id: Ibe0e92b2b3772c53df66e10bf7059be4754d4646 Signed-off-by: Periyasamy Palanisamy <periyasamy.palanisamy@ericsson.com>
2018-03-22Merge "Release Automation"Trevor Bramwell13-0/+792
2018-03-22jjb: xci: bifrost-verify: Update location for XCI bifrost scriptsMarkos Chandras1-1/+1
Change-Id: I55e5042fda4bf5662a90f0065fa427a50bc76bfa Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-22Merge "QTIP: create a daily CI job for network test"Serena Feng1-0/+6
2018-03-22Merge "Fetch creds according scenario type(os or k8)"mei mei2-11/+18
2018-03-22Fix RegExp issue for sfc scenarioLinda Wang1-1/+1
Change-Id: I345aeed4e11c4f5329251766b1fcf6aa1d852ba1 Signed-off-by: Linda Wang <wangwulin@huawei.com>
2018-03-22Add job timeout for clover and container4nfvQiLiang2-0/+9
- set clover-daily-deploy job timeout to 3h - set container4nfv-daily-deploy job timeout to 4h - add time trigger for clover upload job Change-Id: I3809828d764a2da176c8f51713ebb763f979211d Signed-off-by: QiLiang <liangqi1@huawei.com>
2018-03-21Release AutomationTrevor Bramwell13-0/+792
Tracking releases through yaml file similar to the openstack/releases project. Includes a schema file to be for validation, jobs for creating gerrit branches and stable branch jobs, and documentation for projects on creating their releases. Change-Id: Id1876482723e01806c0a6932126dff5ea314eae5 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-03-21xci: Disable merge jobs on centos until centos is fixed properlyFatih Degirmenci1-3/+4
Change-Id: Ieab479d257fb1922136eb343d1dd25f2006c2ac2 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-21xci: Make centos jobs non-voting for promotionFatih Degirmenci1-4/+10
Change-Id: I981b115bc37f034db991667a29f0ce66b239cbdf Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-21Merge "Add Compass POD ipmi info to pod.yaml for ha.tc009"Fatih Degirmenci1-5/+18
2018-03-21Add jjb for cloverQiLiang3-0/+171
- clover-project.yml is a modified copy of container4nfv-project.yml - clover and container4nfv temporary share the same vpod huawei-virtual6 - add job blocker between clover and container4nfv - add clover doc to opnfvdocs Change-Id: I6e4b133670fd46c57e338af37f2a066c95ce4bc6 Signed-off-by: QiLiang <liangqi1@huawei.com>
2018-03-21QTIP: create a daily CI job for network testzhihui wu1-0/+6
Change-Id: I0913e115951aa48eb99366125292772f4fc6d93e Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
2018-03-21Fetch creds according scenario type(os or k8)chenjiankun2-11/+18
We have two kinds of scenario: os and k8, their creds is defferent, so we need to fetch creds according different scenario type. Change-Id: I54d1a1fcdfa981fed2a1433693aa3483abf4baf0 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2018-03-20Merge "Make Apex JJB Renderer Importable"Tim Rozet1-21/+29
2018-03-20xci: Set CI_LOOP, FUNCTEST_MODE, and FUNCTEST_SUITE_NAME in jobsFatih Degirmenci2-4/+61
These variables are needed for displaying details of functest run. Apart from that and more importantly, FUNCTEST_SUITE_NAME will be important for adjusting the criteria for verifying and promoting scenarios. Change-Id: I7a3c82c6babc4d5e057b26fda697e9fc969c8526 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-20Merge "xci: Enable post merge promotion for generic scenarios"Fatih Degirmenci1-0/+15
2018-03-20Add Compass POD ipmi info to pod.yaml for ha.tc009xudan1-5/+18
1. For ha.tc009 which needs to login one controller node and shut it down with its ipmi info. 2. So it needs to add impi info and jumpserver info into pod.yaml file. 3. Remove yardstick.img file to save artifacts space JIRA: DOVETAIL-628 Change-Id: I4d2aa48b209155f27e49a7bb871a170683b47fc9 Signed-off-by: xudan <xudan16@huawei.com>
2018-03-20Merge "xci: Make centos job non-voting for promotion"Fatih Degirmenci1-2/+2
2018-03-20Merge "Temporary incease functest jobs timeout for arm"Jose Lausuch1-1/+1
2018-03-19Make Apex JJB Renderer ImportableTrevor Bramwell1-21/+29
Wrapping the script into a function will make it importable from other python code. Calling the file directly will still work as it did before. Change-Id: I8336d34b05687fa650ce1c123bb37fa311ce2978 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-03-19xci: Make centos job non-voting for promotionFatih Degirmenci1-2/+2
verify-centos jobs do not vote for patch verification since things on centos are still shaky. Make merge-centos jobs non-voting for promotion as well by not allowing them to fail the entire promotion job or by stopping the promotion. Change-Id: Idf7b3c7586d94454ff94cd0bccf42f02954c722c Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-19Merge "Initial Release files from Euphrates Release"Trevor Bramwell34-0/+309
2018-03-19xci: Enable post merge promotion for generic scenariosFatih Degirmenci1-0/+15
Change-Id: Iacbd6515de08e77e3874354fc8e23a6cf8f7bf61 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-19Merge "xci: Enable deployment and testing for post merge jobs"Fatih Degirmenci1-6/+7
2018-03-19xci: Fix envInject and remove scenario distro support checkFatih Degirmenci2-9/+2
envInject doesn't play well with variable expansion so it is fixed. [1] Scenario support check is not necessary for promotion since the promotion job is common for all scenarios/distros and check is done as part of earlier distro jobs accordingly. [2] gsutil upload is also made quiet. Fixed version can be seen from [3]. [1] https://build.opnfv.org/ci/job/xci-merge-promote-virtual-master/2/console [2] https://build.opnfv.org/ci/job/xci-merge-promote-virtual-master/4/console [3] https://build.opnfv.org/ci/job/xci-merge-promote-virtual-master/5/console Change-Id: Ie36394cab631826209dda4cea6daa456aca3c276 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-19Merge "xci: Store the metadata for promoted scenario"Fatih Degirmenci2-9/+34
2018-03-19Merge "xci: Make post merge job common across all scenarios"Fatih Degirmenci1-29/+20
2018-03-19xci: Enable deployment and testing for post merge jobsFatih Degirmenci1-6/+7
Change-Id: I61fdcf11cc8008bde1c4e26e7b4fd6f16b6e5a78 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-19xci: Store the metadata for promoted scenarioFatih Degirmenci2-9/+34
Change-Id: I1048be7e7a41c56d25c7689678d3811f0a5eae44 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-19Merge "Remove iptables and unset privileged flag"Fatih Degirmenci1-6/+1
2018-03-19xci: Make post merge job common across all scenariosFatih Degirmenci1-29/+20
It is difficuly to have post-merge jobs per scenario since we set the scenario during job runtime and having jobs per scenario makes things unnecessarily complicated. Apart from that, there is no reason to have scenario specific merge jobs either since this is some kind of verify job and everything is same except the scenario name itself which we extract via set-scenario script. Daily and further jobs will be scenario specific since they will be run on timer and we will have ability to specify the scenario. Change-Id: I3bf6d5ce0fbc48b2d2b2b9695e198bad229ce08d Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-19Create an initial file for return valueLinda Wang1-0/+3
Change-Id: I7c19dbe853124272bbf7203ab2778b616c847048 Signed-off-by: Linda Wang <wangwulin@huawei.com>
2018-03-19Use /root/.kube/config for all installersCédric Ollivier1-1/+1
There is no reason to use one specific dir per installer in Functest containers. Change-Id: Ib2e1443b14c15aa385e65194f70f6442e0c9f7b9 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-03-19Merge "xci: Adjust the recorded scenario metadata for promotion"Fatih Degirmenci1-15/+21
2018-03-19Merge "change rabbitmq-server to rabbitmq for all installers"mei mei1-0/+7
2018-03-19Merge "Add sshkey and user config into functest container"mei mei1-1/+13
2018-03-17xci: Adjust the recorded scenario metadata for promotionFatih Degirmenci1-15/+21
PROJECT_NAME is added into scenario metadata to use for promotion and xci dashboard. Also, the metadata collected is aligned across different type of patches including the skipped ones. Change-Id: I3751884b48f5d9306d0cae35c757b976484b26a3 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-17Merge "xci: Log functest output before failure"Fatih Degirmenci1-2/+5