Hi! <https://github.com/osquery/osquery/pull/7315...
# generalr
Robin Powell
09/23/2021, 8:01 PMHi! https://github.com/osquery/osquery/pull/7315 failed for reasons that I don't think have anything to do with my changes and that seem like they're probably transient?, so I thought I'd come in here and ask if the correct thing to do is to retry the checks, and if so how y'all tend to do that around here? (Like normally and amend and force push the latest commit, but some places don't like that sort of shenanigans.)
s
Stefano Bonicatti
09/23/2021, 8:03 PMHi! I kicked a new build
r
Robin Powell
09/23/2021, 8:04 PMOh! Neat, how? Like, I've never figured out how to get github to do that, even for projects I own. Or is this something you did on the CI backend?
s
Stefano Bonicatti
09/23/2021, 8:05 PMSo this needs a maintainer access (write access to the repository), but in the PR, the Checks tab, on the top right side you have "Re-run all jobs"
Stefano Bonicatti
09/23/2021, 8:08 PMIn the past we were using Azure Devops CI and that permitted to re-run a particular failed job, but with Github Actions you're forced to re-run everything ^^'.
Another way is to close and reopen the PR. Obviously that causes a message to be sent if anyone is watching.
At the same time that also realigns the temporary merge branch against master, that Github creates behind the curtains, which is what the CI uses to build.
r
Robin Powell
09/23/2021, 8:42 PMHuh. It looks like the reason I've never seen that before is that most of the projects I work with have CI/CD components that are not "checks", in some github-specific sense; that is, I'm looking at PRs with checks listed in the conversation area:
Robin Powell
09/23/2021, 8:42 PMimage.png
Robin Powell
09/23/2021, 8:42 PMBut that same PR:
Robin Powell
09/23/2021, 8:42 PMimage.png
Robin Powell
09/23/2021, 8:43 PMDifferent kind of CI/CD integration, I guess. 🤷♂️ Not actually important, was just curious. 🙂
7 Views