Make sure that functional test triggered on sample changes
To be able to define different irrelevant-files for the functional jobs
than the ones defined in openstack-zuul-jobs we need to copy the jobs to
the nova tree and modify the fields in tree.
Technically we could factor out the irrelevant-files regexp list from
functional and functional-py35 jobs as they are the same today. However
in the future when they diverge we cannot simply override the
irrelevant-files in one of the jobs. Therefore this patch does not
introduce a common base job for functinal and functional-py35 jobs
to discurage trying to override.
The openstack-tox-functional and fuctional-py35 are removed from the
nova part of the project-config in
I56d44f8dff41dbf3b2ff2382fa39b364f55f9a44
Conflicts: .zuul.yaml
NOTE(mriedem): The conflict is due ot the nova-lvm job definition
not existing in Pike, which is OK because it's a non-voting job
that runs in the experimental queue so we don't need it in Pike.
Reviewed: https:/ /review. openstack. org/536934 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=274e2e61187 030332d5d427d22 72b48a26a0012a
Committed: https:/
Submitter: Zuul
Branch: stable/pike
commit 274e2e611870303 32d5d427d2272b4 8a26a0012a
Author: Balazs Gibizer <email address hidden>
Date: Fri Jan 12 16:23:00 2018 +0100
Make sure that functional test triggered on sample changes
To be able to define different irrelevant-files for the functional jobs
than the ones defined in openstack-zuul-jobs we need to copy the jobs to
the nova tree and modify the fields in tree.
Technically we could factor out the irrelevant-files regexp list from files in one of the jobs. Therefore this patch does not
functional and functional-py35 jobs as they are the same today. However
in the future when they diverge we cannot simply override the
irrelevant-
introduce a common base job for functinal and functional-py35 jobs
to discurage trying to override.
The openstack- tox-functional and fuctional-py35 are removed from the 41dbf3b2ff2382f a39b364f55f9a44
nova part of the project-config in
I56d44f8dff
Conflicts:
.zuul. yaml
NOTE(mriedem): The conflict is due ot the nova-lvm job definition
not existing in Pike, which is OK because it's a non-voting job
that runs in the experimental queue so we don't need it in Pike.
Depends-On: https:/ /review. openstack. org/538619/
Closes-Bug: #1742962 7af31aa4479fc88 3a7c65848ff 8ed96cc8d707187 7eefab994f)
Change-Id: Ia684786d1622da
(cherry picked from commit d4377c2d537ea99