-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
{amazon,community}.aws: cross-project testing #1357
{amazon,community}.aws: cross-project testing #1357
Conversation
df9c7da
to
dfebe3f
Compare
Build succeeded.
|
dfebe3f
to
209cbd1
Compare
Depends-On: ansible/ansible-zuul-jobs#1357
Build succeeded.
|
35f2011
to
01ebc71
Compare
Build succeeded.
|
01ebc71
to
19ea592
Compare
Build failed.
|
19ea592
to
07c82a7
Compare
Zuul encountered a syntax error while parsing its configuration in the while parsing a block collection |
07c82a7
to
7bcb412
Compare
Zuul encountered a syntax error while parsing its configuration in the Job ansible-test-cloud-integration-aws-py38_0 not defined The error appears in the following project-template stanza: project-template: in "ansible/ansible-zuul-jobs/zuul.d/project-templates.yaml@master", line 54, column 3 |
7bcb412
to
a7519bb
Compare
Zuul encountered a syntax error while parsing its configuration in the Job ansible-test-cloud-integration-aws-py38_0 not defined The error appears in the following project-template stanza: project-template: in "ansible/ansible-zuul-jobs/zuul.d/project-templates.yaml@master", line 135, column 3 |
0767b6f
to
bd7272a
Compare
Build failed.
|
bd7272a
to
9a9e85e
Compare
@alinabuzachis, the PR is ready for review. |
Build succeeded.
|
Actually, there is a problem https://ansible.softwarefactory-project.io/zuul/build/04c19185926b45958626059af94324cd |
9a9e85e
to
53b5842
Compare
Build succeeded.
|
53b5842
to
75616a5
Compare
Build succeeded.
|
75616a5
to
0ce9500
Compare
Build succeeded.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@goneri Thank you Goneri. Awesome!
0ce9500
to
a3b3e39
Compare
Build succeeded.
|
a3b3e39
to
a4091ce
Compare
Build succeeded.
|
c14f919
to
0a56e39
Compare
Build succeeded.
|
0a56e39
to
6ec04a3
Compare
Build succeeded.
|
6ec04a3
to
a091ac9
Compare
Build succeeded.
|
If there is a change in module_utils, run the CI only for the modules affected by that change. This also solves the case where in the same PR there is a change in a module_utils file (e.g., rds) and a change on a module (e.g., ec2_vpc_igw), returning the 'target_to_test' containing ec2_vpc_igw and all modules affected by the change in module_utils. At the moment, 'target_to_test' is returned with only ec2_vpc_igw. Co-Authored-by: Alina Buzachis <[email protected]>
a091ac9
to
6613f32
Compare
Build succeeded.
|
Build succeeded (gate pipeline).
|
If there is a change in module_utils, run the CI only for the modules
affected by that change.
This also solves the case where in the same PR there is a change in a
module_utils file (e.g., rds) and a change on a module (e.g., ec2_vpc_igw),
returning the 'target_to_test' containing ec2_vpc_igw and all modules
affected by the change in module_utils. At the moment, 'target_to_test'
is returned with only ec2_vpc_igw.
Co-Authored-by: Alina Buzachis [email protected]