-
Notifications
You must be signed in to change notification settings - Fork 57
Try alternative branches for tests that use non-stratisd repos #3858
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
Conversation
|
Congratulations! One of the builds has completed. 🍾 You can install the built RPMs by following these steps:
Please note that the RPMs should be used only in a testing environment. |
2 similar comments
|
Congratulations! One of the builds has completed. 🍾 You can install the built RPMs by following these steps:
Please note that the RPMs should be used only in a testing environment. |
|
Congratulations! One of the builds has completed. 🍾 You can install the built RPMs by following these steps:
Please note that the RPMs should be used only in a testing environment. |
471023e to
e222410
Compare
|
Even though both branch checkouts failed, the condition for both checkout succeeding passed. This is very strange. |
e222410 to
7fe32f7
Compare
|
This one is working... |
387e197 to
5347b28
Compare
5347b28 to
adf821b
Compare
7e51b34 to
16f633e
Compare
|
ref value is expanding to 3858/merge which is not what is wanted. |
16f633e to
26dff9b
Compare
In case a change has to be made to the other repo so that this PR compiles, this should ensure that the branch that addresses the problem is automatically used instead of the default branch. The branch name for the external repos is exactly the branch name for the PR. Also install git for checkout action, so that the checkout action doesn't have to fall back to the GitHub API. Signed-off-by: mulhern <amulhern@redhat.com>
|
Packit test failures can be ignored... |
jbaublitz
left a comment
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.
Approved. Are you planning to just do this for stratis-cli for the time being? I feel like libcryptsetup-rs/libblkid-rs/etc. will be harder as they're Rust packages and it involves changing the Cargo.toml in Github Actions. I'm not even sure what it would take in packit.
This is for stratis-cli and for testing repos. For our Rust dependencies...it will have to be a Rust solution. I'm not sure yet what we could do with Cargo.toml to make that work. It's possible that |
Related stratis-storage/project#755