-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Support a CI-colon-MACHINE mode #20946
Support a CI-colon-MACHINE mode #20946
Conversation
9f99a4c
to
1a69a16
Compare
@edsantiago PTAL at this idea. I drank some inspiration in this morning's coffee 😁 IIRC (I can test it) the PR title magic Cirrus-CI env. var values are sticky. In other words, they don't change if you press "re-run". Since PR-merging is blocked for drafts, and a green "Total Success" status, I simply moved the magic-string check there 👌 |
1a69a16
to
d63597b
Compare
force-push: Woops, forgot to add an |
d63597b
to
256131e
Compare
Woops: Force-push: Updated conditions so machine tests only run for PRs. We only want the most critical bare-bones checks on branches and new tags to avoid flakes. |
256131e
to
06a14f4
Compare
Redo Test: Magic string in title + no draft mode set. |
TODO: Test w/o magic, w/o draft, confirm all PR-level tests run normally. |
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.
/lgtm
/hold
script: | | ||
if [[ "$CIRRUS_CHANGE_TITLE" =~ CI:MACHINE ]] && [[ -n "$CIRRUS_PR" ]]; then | ||
echo "Error: Risk of untested change merge." | ||
echo "Please remove [CI:MACHINE] from title." | ||
exit 1 | ||
fi |
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.
This is brilliant.
Please remove [WIP] flag from title. |
There's at least one more test I need to run. |
Because the podman machine tests normally run at the end of the chain, it's time consuming for developers to validate machine-only changes. Support a special CI runtime mode, only when a PR is marked as a draft. Update related documentation Also: Only run machine tests on PRs, never for branches or new tags. Signed-off-by: Chris Evich <[email protected]>
06a14f4
to
95eb22c
Compare
Test: Run w/o magic, w/o draft. Reviewers: Please double-check my eyeballs, confirm all expected (normal) PR-level tests run/ran. This PR touches some tricky, anti-POLA logical conditions. I could easily have screwed something up. |
Okay, I think this is ready now. |
/approve |
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.
will merge and immediately put into action.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: baude, cevich 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 |
9877dc4
into
containers:main
Because the podman machine tests normally run at the end of the chain, it's time consuming for developers to validate machine-only changes. Support a special CI runtime mode, only when a PR is marked as a draft. Update related documentation
Also: Only run machine tests on PRs, never for branches or new tags.
Does this PR introduce a user-facing change?