-
Notifications
You must be signed in to change notification settings - Fork 2.2k
[1.3] ci fixes + support for scheduled ci jobs #4763
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
Commit 8742074 neglects to update the exclusion rules when bumping Go releases, and so we no longer exclude running on actuated with older Go release, or running with criu-dev with older Go release. Fixes: 8742074 ("CI: add Go 1.24, drop go1.22") Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com> (cherry picked from commit 0628b1e) Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
... or from another job. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com> (cherry picked from commit 9d970f1) Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
When we run CI not on a pull request, the commit job is skipped, as a result, all-done is also skipped. To allow all-done to succeed, modify the commit job to succeed for non-PRs. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com> (cherry picked from commit 43955a0) Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
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, thanks!
@opencontainers/runc-maintainers PTAL |
Why most of CI jobs didn't run in this PR? |
I guess it's because I originally forgot to change the branch to release-1.3, and later, when I did, github did not restart some jobs. The only way to work around that is close/reopen the PR, which @AkihiroSuda did (thank you). |
This is a partial backport of #4760 to release-1.3 branch, fixing some issues and allowing the scheduled jobs to be run on release-1.3 branch.