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
CI: Support testing w/ podman-next COPR packages #4830
Conversation
7c9f045
to
f64785e
Compare
LGTM |
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.
Big picture LGTM, with a few concerns.
This deserves to be documented, but I can't even find where CI:DOCS
or :BUILD
are documented...?
Sometimes important updates need to be made to dependent packages and run through CI w/o waiting for package release and new CI VM image builds. Support this in buildah CI as in podman CI, by updating packages during setup when the magic string is present and PR is in draft-mode. Note: To support containerized testing, both `CIRRUS_CHANGE_TITLE` and `CIRRUS_PR_DRAFT` env. vars. are passed through. For these tasks, this will result in **TWO** updates - One for the host, and another one in the container. Signed-off-by: Chris Evich <cevich@redhat.com>
Yeah probably. It got way more out of hand in podman-CI, which is why it's documented there. And still I don't think many/any people read it 😞 |
Force-push: Addressed all of Ed's concerns, except the missing docs. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cevich, edsantiago 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 |
/lgtm |
/hold cancel |
What type of PR is this?
/kind other
What this PR does / why we need it:
Sometimes important updates need to be made to dependent packages and
run through CI w/o waiting for package release and new CI VM image
builds. Support this in buildah CI as in podman CI, by updating
packages during setup when the magic string is present and PR is in
draft-mode.
Note: To support containerized testing, both
CIRRUS_CHANGE_TITLE
and
CIRRUS_PR_DRAFT
env. vars. are passed through. For these tasks,this will result in TWO updates - One for the host, and another one
in the container.
How to verify it
CI will pass with and without magic keyword in title.
Which issue(s) this PR fixes:
Special notes for your reviewer:
CI Run when
[CI:NEXT]
was in the PR title. I believe the handful of SELinux related test failures are a known issue.Does this PR introduce a user-facing change?