Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I7b4ad69b1c7c7b59b9feadef8808a1ef81a34367
Signed-off-by: meimei <meimei@huawei.com>
|
|
Change-Id: If1678725a1b417cf0a94265557a6d88aa7c416cb
Signed-off-by: helenyao <yaohelan@huawei.com>
|
|
|
|
JIRA: FUNCTEST-653
opnfv/functest images with <none> tag are generated after functest images are pull many times.
These images can be queried with filter "dangling".
Logics are added to remove dangling images and their containers.
Change-Id: I271f4d95c5fb62fdebe690d82330f6b25ac1e2f8
Signed-off-by: helenyao <yaohelan@huawei.com>
|
|
|
|
Change-Id: Iad856adf625a56c2f5c366fb414746d1e9e16691
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
JIRA: FUNCTEST-665
In patch https://gerrit.opnfv.org/gerrit/#/c/25775/,
it set CLEAN_DOCKER_IMAGES=false to save time.
On CI job, the cleaning step is still undertaken.
Change-Id: Iaca64d3a347dafa9c87975c756ea8bcb30ae2f93
Signed-off-by: helenyao <yaohelan@huawei.com>
|
|
This patch makes sure we use 2 types of scm, and allows us to specify
them by adding one line in job-templates.
- git-scm # for daily jobs and merge jobs
- git-scm-gerrit # for verify jobs [New]
Change-Id: Iddc8a5e0e115193c7081a6d6c53da209900e95c8
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
This is probably not the best way to fix this and will hopefully
be aligned with the rest.
Change-Id: I0a7602c34c3b5941f36ae0073e7abfdf4b4a9cb4
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
For the functest change we use the new cli which provides us
with comma seperation of the test cases.
Change-Id: Id6c88bd3e13ecce7bf5a738ead8ad98df4e00b5a
Signed-off-by: Nikolas Hermanns <nikolas.hermanns@ericsson.com>
|
|
This will save some time. The "docker pull" command
takes care of upgrading the image if it exists.
Change-Id: I195e0ddac3673cdafb13ab6d78874367420e37ff
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
The builder/script 'functest-cleanup' will delete docker images
for functest, so that we can make sure the latest functest will
be used during the tests. But, it also makes a pod downloads
image every time CI triggered functest-suite.
This patch adds option 'CLEAN_DOCKER_IMAGES' (default=true),
so that the job owner can choose whether he/she wants to drop
the docker images or not depends on frequency or charactaristics
of the job.
Change-Id: I0b7affccb404fb8c4f0939b00d65e363ec62f7c3
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
|
|
With the addition of ODL and OpenStack Gerrit servers, it's important we
don't generate additional noise by accidentally building against these
Gerrit servers when we don't intend to.
JIRA: RELENG-179
Change-Id: Ia163c6c3eaa58e8e21dc6548a839062fcbde39ed
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: Icb5dd3f0f46eb4891609d1f0e4d868e84fe49a14
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
After refactoring of the repo structure
we add to adapt the path in releng
but this change is only valid for Danube and after
old pathes must be kept for colorado
JIRA: FUNCTEST-525
Change-Id: I4cf5951111dbb9cb3d7a002c24efe1167e994222
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
JIRA: FUNCTEST-525
Change-Id: I613757f98a7b41e924f1334053f83f8966536018
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
run_unit_tests.sh is a new thing for Danube,
it shouldn't be executed in Colorado verify jobs.
Change-Id: Ibc9fd41ae390ef2fcb7d448914dd65a7b9166781
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
|
|
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
Change-Id: Ieb8e291d31479fff1c7cad941eb9be83cd4b670f
Depends-On: Icd958552fafb4e8dc58f9008586bcaf33862ccd4
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
arm-pod-3 will be removed as CI pod and this commit add triggers
to make it a non-ci pod
Change-Id: Ice16b8d32c553a059a2c9885fd801a736a59a14d
Signed-off-by: cristinapauna <cristina.pauna@enea.com>
|
|
Change-Id: I8b8cf515d47e6117bfa5804c15fac22ac8b8d90a
Signed-off-by: meimei <meimei@huawei.com>
|
|
This entry will be used by doctor's verify job which will triggered
by each patch upload into gerrit.
Change-Id: I1f4bc8cbb56baf8192ba9d26dcfb80de8cade560
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
Change-Id: I9e402d395a3c90f65d0e73f9ef18c08e0801afad
Signed-off-by: meimei <meimei@huawei.com>
|
|
Change-Id: I9c6ee092cea755aea58a91a696cb338e1eb5df8b
Signed-off-by: meimei <meimei@huawei.com>
|
|
This patch adds a new jenkins job which will be executed every time
doctor patch is uploaded. The code will be verified by executing
doctor scenario on the specific pod using functest.
JIRA: DOCTOR-70
Change-Id: I480cd905991ccb1ef7426187fe83cbf1ae798ce9
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
Change-Id: I50c47a40f3337e7140740f49b09f3e508eb0087c
Signed-off-by: Paul Vaduva <Paul.Vaduva@enea.com>
|
|
Change-Id: I8309c027a871246623c199447dcb667b5bb2f066
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
|
|
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: I39d085726551ac1db2531d474d9c407840f5ffc0
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
This prevents from exiting the job without pushing the logs
to artifacts if the functest loop fails.
JIRA: FUNCTEST-443
Change-Id: I6925b5855326df809dbce9f389b10be8a00cf8de
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
Change-Id: I07d7f0a3cdef3ebe1dec07156791f181a149ba19
Signed-off-by: Tim Rozet <trozet@redhat.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>
|
|
Daily jobs for Colorado branch for installer and test projects
have not been created yet and it needs to be done via separate
patches.
Change-Id: I34517e89dfc502ce5741733e01bf8425d513df02
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>
|
|
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>
|
|
JIRA: FUNCTEST-412
Change-Id: Ic23f5629e00d4adec62f6021bfd859f439e12825
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
Some installer/scenarios take too long to execute the
tests and the job times out.. Although this is not the
best solution, we can let the installer teams run the
tests to see why it takes too long sometimes)
Change-Id: I37cc393c65408741c5f0ecb9cc12ad6297c31d6d
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
Change-Id: Id06771db96d1ca014c153ffc2b7567d6b2ea07ea
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
Change-Id: I405bcbf26965a5290fb8dad9786881251e6aea81
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: If63cca009f539125ce877fa05f40178bb1c71247
Signed-off-by: meimei <meimei@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>
|
|
|
|
Something in Apex is pushing the RETURN rule down the chain, and adding
REJECT reject-with icmp-port-unreachable. This enhances the check to
make sure not only does the rule exist, but it is at the top of the
chain.
Change-Id: I527bc45c30008aaf30d5bc9e1d474a14065b3fdf
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|