Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
Most of these projects will not have a stable branch, but for those that
do follow the process they will need these jobs.
Change-Id: Id0e6cfa9716d72882c38b0fcb42b3ab420332a2e
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
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>
|
|
The merge job should only run when changes to the release yaml files are
made.
Change-Id: I12d37e465c664b48d4f07223f377a4ff7494ead7
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
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>
|
|
|
|
Change-Id: I16eed2ec0ca1fa659fc449799813c02b19b08174
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
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>
|
|
Change-Id: Ibe0e92b2b3772c53df66e10bf7059be4754d4646
Signed-off-by: Periyasamy Palanisamy <periyasamy.palanisamy@ericsson.com>
|
|
|
|
Change-Id: I55e5042fda4bf5662a90f0065fa427a50bc76bfa
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
|
|
We have hardcoded /root/.kube/config as the default config file
inside functest-kubernetes container:
https://gerrit.opnfv.org/gerrit/#/c/53815/
Change-Id: I135f2009c61bb0238fcc3c9eb6d131305603f495
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
|
|
Change-Id: I345aeed4e11c4f5329251766b1fcf6aa1d852ba1
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
- 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>
|
|
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>
|
|
Change-Id: Ieab479d257fb1922136eb343d1dd25f2006c2ac2
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: I981b115bc37f034db991667a29f0ce66b239cbdf
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
- 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>
|
|
Change-Id: I0913e115951aa48eb99366125292772f4fc6d93e
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
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>
|
|
|
|
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>
|
|
|
|
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>
|
|
|
|
|
|
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>
|
|
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>
|
|
|
|
Change-Id: Iacbd6515de08e77e3874354fc8e23a6cf8f7bf61
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
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>
|
|
|
|
|
|
Change-Id: I61fdcf11cc8008bde1c4e26e7b4fd6f16b6e5a78
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: I1048be7e7a41c56d25c7689678d3811f0a5eae44
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
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>
|
|
Change-Id: I7c19dbe853124272bbf7203ab2778b616c847048
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
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>
|
|
|
|
|
|
|
|
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>
|
|
|
|
These files normally contain the start point of the stable/release branch,
but as this is the initial setup starting from the previous release,
they contain the tip of the stable branch.
When a project is ready to being the stable branch process, they will
copy their project's release file and modify the 'branches' mapping to
create their stable branch.
Change-Id: I0244da5eeb94c431d83f217ec07b08553fdf0639
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|