Steve Dower wrote:
> GitHub Actions *is* a CI service now, so my PR is actually using their
> machines for Windows/macOS/Ubuntu build and test.

Oh I see, that makes more sense. Thanks for the clarification.

Steve Dower wrote:
> It doesn't change the ease of enabling/disabling anything - that's still
> very easy if you're an administrator on our repo and impossible if
> you're not :)

Yeah I was aware that it required administrative permissions, I was just under the impression that it wasn't a simple on/off toggle, and that there wasn't an easy way to ensure failures were occurring due to external factors. I suppose that's a separate issue though.

Steve Dower wrote:
> And you don't need a separate login to rerun checks - it's just a simple button in the
> GitHub UI.

That would be especially great, and much better than closing+reopening the PR. Restarting the checks is typically a last resort since intermittent regression test failures are a concern, but it's highly useful when the failure is occurring due to external factors (such as a recently merged PR or issues with the CI service itself).

On Fri, Dec 6, 2019 at 1:33 PM Steve Dower <steve.dower@python.org> wrote:
On 06Dec2019 1023, Kyle Stanley wrote:
> Steve Dower wrote:
>  > As a related aside, I've been getting GitHub Actions support together
>  > (which I started at the sprints).
>
> Would adding support for GitHub Actions make it easier/faster to
> temporarily disable and re-enable specific CI services when they're
> having external issues? IIUC, that seems to be the primary concern to
> address.
>
> Note that I'm not particularly well acquainted with GitHub Actions,
> other than briefly looking over https://github.com/features/actions.

GitHub Actions *is* a CI service now, so my PR is actually using their
machines for Windows/macOS/Ubuntu build and test.

It doesn't change the ease of enabling/disabling anything - that's still
very easy if you're an administrator on our repo and impossible if
you're not :)

However, it does save jumping to an external website to view logs, and
over time we can improve the integration so that error messages are
captured properly (but you can easily view each step). And you don't
need a separate login to rerun checks - it's just a simple button in the
GitHub UI.

Cheers,
Steve