Age | Commit message (Collapse) | Author | Files | Lines |
|
Enable triggers of Colorado on zte-pod1 and zte-pod3. Meanwhile, add
colorado branch for zte-pod1 and zte-pod3 in Functest and Yardstick.
Change-Id: I575d37356c9223935d5975a834589b33f9e7498b
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
Change-Id: Ic5c9d35ccc92d8f19419c9b25476c0e084c7299f
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
Change-Id: I47cb8e3ff448b8adc26b62201b15ddd3476dd0c1
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
This change contains updates that impact compass and joid jobs due
to updates in functest and yardstick that remove brahmaputra branch.
Please note that the triggers for colorado haven't been created yet.
It will be done once the basics in place.
Change-Id: Id5eb8c406d34ff9f3ac59f73243034cbf49b23f0
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
|
|
Change-Id: I61b68a7db60193f5525de7151e43b7752e5dd604
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
For all zte pods, the fuel ip is not 10.20.0.2 . It need to override.
Change-Id: Ib9533c28d9d03fdfc4804955de9eee7501453cd9
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
Change-Id: I00ea21566bd2244c35bdf658eb95e8cf435b7be9
Signed-off-by: Paul Vaduva <Paul.Vaduva@enea.com>
|
|
1. CI scenario: os-odl_l2-nofeature-ha using Fuel installer
2. Adjust qtip daily job from zte-pod1 to zte-pod2
Change-Id: I3e4e1adf3a6865a4cc9be81522472c781a8aea4f
Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
|
|
Deployment in zte-pod3 successfully but yardstick and fucntest
can not be triggered.
JIRA: PHAROS-247
Change-Id: I5407f8c51bac83263b9f165558a38fa0db199868
Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
|
|
Add ZTE-POD3 to support whole procedure of CI, including:
deployment, yardstick and funectest.
Currently it supports os-nosdn-kvm-ha scenario at the initial step
JIRA: PHAROS-247
Change-Id: I70dde8765696ee08339e7cada2428f8461b5f3a2
Signed-off-by: Julien-zte <zhang.jun3g@zte.com.cn>
|
|
1. first need to change in yardstick
2. then change in releng to modify the input parameter
JIRA: YARDSTICK-299
Change-Id: Ie9c96d4ddc6b15b0488ef1cff1f2c7531429baf0
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
This is the first step towards having alignment of the job structure, applying
commit gating and use of labels for all installer jobs.
Apart from the above, it also
- puts all CI baremetal and virtual PODs together
- gets rid of use of slaves directly for CI baremetal and virtual PODs
- switches labels for all CI baremetal and virtual PODs using below labels
{installer}-baremetal
{installer}-virtual
- puts all CI build slaves together and switches to labels - except huawei-build
- puts all none-CI PODs together
Please note that this change does not impact the overall job structure.
Change-Id: I2d8d15799a57fe7e063d39f81b96d19c218b100e
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: Iaa1b15badf9750f47a68612f4dae48952de3a3d4
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
This is a required field for JJB > 1.4
Change-Id: Ifb6f5d4b3a28f2d85f546151ca9aca4a4061f3ef
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
This change switches compass jobs to use labels instead of tying
jobs to slaves.
The changes in detail are:
- Compass jobs can roam on any pod that is labelled with compass-baremetal
and compass-virtual.
- Above means that there is no branch/pod allocation anymore.
- New jobs are created in order to get rid of pod names from them and just
use baremetal or virtual in names.
- Old jobs are removed.
- Related test jobs are updated.
- huawei-virtual label is renamed to compass-virtual since we still have
installer specific slaves, not company specific. In future the job
might end up on a none-Huawei slave too.
- huawei-pod2 is not a CI POD so it is left in none-CI PODs section.
- block relations and triggers might require fine tuning and left to compass
project to decide how to adjust
Job structure remains same; one parent job calling 3 downstream jobs:
deploy, functest, yardstick.
The OS to deploy (trusty or centos7) needs to be solved in a separate patch
in a sustainable way.
Change-Id: I22bfaff36640667b6764f0e303a3286af0eb41b2
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
This change switches joid jobs to use labels instead of tying
jobs to slaves.
The changes in detail are:
- Joid jobs can roam on any pod that is labelled with joid-baremetal
and joid-virtual.
- Above means that there is no branch/pod allocation anymore.
- New jobs are created in order to get rid of pod names from them and
just use baremetal or virtual in names.
- Old jobs are removed.
- Related test jobs are updated.
- POD specific parameters are updated and instead of adding pod
specific parameters, they now become parameters for all the pods
labelled with same label. It is not a problem at the moment as
both Intel PODs (pod5, pod6) have same parameters but a different
pod with different parameters will require alignment between pods.
Job structure remains same; one parent job calling 3 downstream jobs:
deploy, functest, yardstick.
Change-Id: I30d270cd05ba3756f6f161d65ee5160eab6b80f4
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
This change switches fuel jobs to use labels instead of tying
jobs to slaves.
The possibilities and changes introduced with this approach are
- If things do not work as expected, slave-label parameter can
be set to certain slave name to get back to old way of
tying jobs to slaves.
- If a scenario requires a different slave, it can still be
created using baremetal or virtual but the label can be
different, pointing to a slave that is capable of running
that scenario. (fuel-baremetal-multisite, etc.)
- The auto-trigger-name for brahmaputra is moved under the
branch anchor and can be used like this if triggers for all
all the jobs for a certain branch need not to be triggered
automatically but job is still kept enabled in case if some
crucial bug needs to be tested.
- No of max concurrent builds stepped to 4 in order to use
all the labelled slaves available. This will require some
adjustments before colorado jobs start to run in order to
share resources between branches fairly.
- All the fuel CI PODs except lf-pod1 have been removed.
Change-Id: I91eca6743bb3d34263e634f9b74550efa1e2ddbe
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
JIRA: COMPASS-393
Change-Id: Ib079cb543f7ed9ae932ea3af99a8c3f187dd0cbc
Signed-off-by: meimei <meimei@huawei.com>
|
|
Change-Id: I22bdffac5888656ee95c458d42c0f6621c822f7f
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
JIRA: YARDSTICK-269
Change-Id: Ibaf305db81d3a24164e9791249408f09cdd41e27
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
Change-Id: I246bcdd9f1fa300639bd7ec744cefe82e293b222
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: If58c84e6f431db88eed3376e446479826da71502
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Slave names will be as below.
- huawei-us-deploy-bare-1 -> huawei-pod1
- huawei-us-deploy-bare-2 -> huawei-pod2
- huawei-sh-test-2-defaults -> huawei-pod3
- huawei-sh-pod6 -> huawei-pod4
- huawei-us-deploy-vm-1 -> huawei-virtual1
- huawei-us-deploy-vm-2 -> huawei-virtual2
- huawei-us-deploy-vm-3 -> huawei-virtual3
- huawei-us-deploy-vm-4 -> huawei-virtual4
huawei-sh-pod4 will be removed from Jenkins.
Please note that this change will result in removal of existing jobs.
This is not that crucial since the use of labels will result in same.
Change-Id: I63798c799a402b1694ee0767ffdb45a597897cd9
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Due to a full cycle job running on zte-pod1, adjust the trigger in
yardstick-ci-jobs.yml on zte-pod1.
Change-Id: Ic5e37d0ce378984c67490d1346835827c45f540b
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
JIRA: YARDSTICK-262
Change-Id: Ib3b9d2e514eff2da2a6ba3ebc9c2dbb614ff1496
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
Change-Id: I70ad2be1c31408a815725f2e7f8759189e63498c
Signed-off-by: Jorgen Karlsson <jorgen.w.karlsson@ericsson.com>
|
|
Change-Id: I0e2722ce81d1ffca966832f608b51f8624866ce1
Signed-off-by: zhifeng.jiang <jiang.zhifeng@zte.com.cn>
|
|
Change-Id: If4bc1826899e57f332c639aacbc45184aea47881
JIRA:-
Signed-off-by: kubi <jean.gaoliang@huawei.com>
|
|
Change-Id: I94a2f097432148a9fa1e739225960c1ac1ec581e
Signed-off-by: meimei <meimei@huawei.com>
|
|
Change-Id: I0e0dce6e2fa7ad8f8cf6261e0c7311f650ecb938
Signed-off-by: QiLiang <liangqi1@huawei.com>
|
|
Also use latest for images built on master and stable for images built on stable branch.
Change-Id: I0988be86abcb2a13d8e94962b4ba1ced8778793b
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: I87aa03bfdab14d31e7794a1a44999bfd3d12b941
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Also enable some more PODs to use influxdb dispatcher
Change-Id: I4143b9dbf9bdc936a962a7c3ef958239f8803ed5
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
|
|
Change-Id: I1409da6441debc551ff674041b3977338521b9ae
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
|
|
Change-Id: I1f07dec5ed94ca35591ed12753c101168d80abd1
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: I2f7cec73be482122d3ff7409eae6d514838a0e3e
Signed-off-by: meimei <meimei@huawei.com>
|
|
Change-Id: I879c8157a5b77d49df7459c9fe77f4f747f04913
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: Iab4fe6f929ad0bcaab02ef236f52c8348fb8614d
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: I063b6083231cfa08f572a19b7ffea79b29e986d4
Signed-off-by: meimei <meimei@huawei.com>
|
|
Change-Id: I8aa23d69d0d3138a069f131e66cc336c82fd74a9
Signed-off-by: meimei <meimei@huawei.com>
|
|
Change-Id: Ie11c8eff68a0d778e2fc63c9cca97f3cd9803c48
Signed-off-by: meimei <meimei@huawei.com>
|
|
Change-Id: Iccd3f461d289e9ecc421cf68bd4e1f01b5f02039
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
This change also adds build blocker for generic job.
Change-Id: I2d1987ca632b30ad8497d14de79b66735afea611
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: I95d8819095ccee74207c645833830a0c6576385f
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Add tirgger macros for PODs to only run yardstick test suites.
Change-Id: I8223fb035cbc7f0c7c72e20af9e6ae024a17b470
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
Change-Id: I6a076b082ab06636e871df190849a2e431ed1a56
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
So it can be overriden by multijob when/if started automatically
and changed by hand when they are started manually.
Change-Id: If574e206a8ce83214ee110929001e9f99012fcf2
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
In case you need it...
Change-Id: I73d90cbb38ad86cc42552060e38db2f1e50a8e99
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
Normally, if Functest jjb is run before, it will have removed
the iptables,this way, we avoid removing something that
does not exist
Change-Id: I2676cc9c87aabaf670d617a9953915b27062b865
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|