-
Notifications
You must be signed in to change notification settings - Fork 792
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
Execute cross-build task using PW pool #2344
Conversation
Ephemeral COPR build failed. @containers/packit-build please check. |
61babfd
to
b1ea0b2
Compare
Leaving this on Draft: I need to update the Mac deployment setup script so it installs |
Previously this task ran using the Cirrus-CI compute service, consuming compute credits. However, since podman is already using a persistent worker pool for CI, it can also be leveraged for use here. Since Mac resources are relatively expensive, it also makes financial sense to re-use infrastructure where possible. Notes: - This change also restricts the cross-build task to only running on the default branch. This is necessary because the PW Pool environment is always rolling forward and may not match what was in place at the time a release-branch was created. - This changes the test from an install + run, to just a build + run. This is required because the task is running as a regular user w/o permissions to install anything system-wide, on a host shared with other CI tasks. Signed-off-by: Chris Evich <cevich@redhat.com>
force-push: Rebased. This should be ready to go now. |
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.
Thanks! LGTM.
- go version | ||
- go env | ||
- make tools | ||
- make validate-local test-unit-local bin/skopeo |
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.
I think (as the failures here show) make bin/skopeo test-unit-local validate-local
might be more helpful, but that’s pre-existing and unrelated.
LGTM |
Previously this task ran using the Cirrus-CI compute service, consuming compute credits. However, since podman is already using a persistent worker pool for CI, it can also be leveraged for use here. Since Mac resources are relatively expensive, it also makes financial sense to re-use infrastructure where possible.
Notes: