Skip to content
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

Stop hard-coding the framework path #1911

Merged
merged 1 commit into from
Jun 20, 2024

Conversation

cjeanner
Copy link
Contributor

@cjeanner cjeanner commented Jun 19, 2024

It may happen a user doesn't want to copy the framework in the
"standard" location, or that they are using some other tools that clone
the framework from another provider.

In such case, controller-0 might see the framework cloned in some other
tree, meaning all of the generated content.

Let's try to be more flexible by using the user provided data, while
defaulting to the standard location.

The internal _cifmw_reproducer_framework_location fact is available
since the very start of the reproducer role call, ensuring we're able to
use it even for new features.

As a pull request owner and reviewers, I checked that:

  • Appropriate testing is done and actually running

Copy link
Contributor

openshift-ci bot commented Jun 19, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

Copy link

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://review.rdoproject.org/zuul/buildset/308a5d084a28487abf7f6b0c5e208e0b

✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 8m 28s
✔️ cifmw-pod-pre-commit SUCCESS in 7m 50s
✔️ cifmw-molecule-libvirt_manager SUCCESS in 14m 58s
cifmw-molecule-reproducer FAILURE in 5m 24s

@cjeanner cjeanner force-pushed the reproducer/ci-framework-path branch 2 times, most recently from ac79ac3 to 6c34366 Compare June 20, 2024 06:04
Copy link

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://review.rdoproject.org/zuul/buildset/1bf90991711041479f760819c25e0c7a

✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 9m 29s
✔️ cifmw-pod-pre-commit SUCCESS in 7m 31s
✔️ cifmw-molecule-libvirt_manager SUCCESS in 19m 22s
cifmw-molecule-reproducer FAILURE in 18m 50s

It may happen a user doesn't want to copy the framework in the
"standard" location, or that they are using some other tools that clone
the framework from another provider.

In such case, controller-0 might see the framework cloned in some other
tree, meaning all of the generated content.

Let's try to be more flexible by using the user provided data, while
defaulting to the standard location.

The internal _cifmw_reproducer_framework_location fact is available
since the very start of the reproducer role call, ensuring we're able to
use it even for new features.
@cjeanner cjeanner force-pushed the reproducer/ci-framework-path branch from 6c34366 to 8650a85 Compare June 20, 2024 07:16
@cjeanner cjeanner marked this pull request as ready for review June 20, 2024 08:50
@cjeanner cjeanner requested review from pablintino and rebtoor June 20, 2024 08:50
@rebtoor
Copy link
Contributor

rebtoor commented Jun 20, 2024

/approve

Copy link
Contributor

openshift-ci bot commented Jun 20, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rebtoor

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit db785d1 into main Jun 20, 2024
6 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the reproducer/ci-framework-path branch June 20, 2024 09:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants