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

Execute cross-build task using PW pool #2344

Merged
merged 1 commit into from
Jun 3, 2024
Merged

Conversation

cevich
Copy link
Member

@cevich cevich commented May 30, 2024

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.

Copy link

Ephemeral COPR build failed. @containers/packit-build please check.

.cirrus.yml Outdated Show resolved Hide resolved
@cevich cevich force-pushed the cross_on_pool branch 2 times, most recently from 61babfd to b1ea0b2 Compare May 30, 2024 18:16
@cevich
Copy link
Member Author

cevich commented May 30, 2024

Leaving this on Draft: I need to update the Mac deployment setup script so it installs gpgme and pkg-config.

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>
@cevich cevich marked this pull request as ready for review June 3, 2024 17:08
@cevich
Copy link
Member Author

cevich commented Jun 3, 2024

force-push: Rebased.

This should be ready to go now.

@cevich cevich requested a review from mtrmac June 3, 2024 17:12
Copy link
Contributor

@mtrmac mtrmac left a 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
Copy link
Contributor

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.

@rhatdan
Copy link
Member

rhatdan commented Jun 3, 2024

LGTM

@mtrmac mtrmac merged commit 77bb7e4 into containers:main Jun 3, 2024
23 of 25 checks passed
@stale-locking-app stale-locking-app bot locked as resolved and limited conversation to collaborators Sep 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants