It has changed over time and I no longer see a button on the "checks" page of GitHub. I only see the button in the azure pipeline which would mean maintainers would need to be "contributors" in the azure DevOps organization/project. I have no problem with that and it looks like you can sign in with a GitHub account so it should just be a matter of collecting the email address associated with their GitHub and inviting them to join. We only get 5 free basic users but we get unlimited free "stakeholder" accounts. I assume we might need basic accounts to interact with the pipeline stuff but I don't know for sure. Anyone who has paid Microsoft visual studio subscriptions (like from an employer) usually doesn't count towards the 5.

Regardless for those actively contributing and interested we should add them up to the limit. This was one of the reasons we had desired long term to align on GitHub build services instead.

Other thoughts?

Thanks

Sean

Hi Sean,

Do you know what GitHub permissions are required to see the re-run button?

I think it is reasonable for all Maintainers to have that available.

Mike

From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Sean
Sent: Monday, May 29, 2023 8:12 AM
To: devel@edk2.groups.io; ardb@kernel.org; Rebecca Cran <rebecca@bsdio.com>
Cc: devel@edk2.groups.io; Kinney, Michael D <michael.d.kinney@intel.com>; Kubacki, Michael <michael.kubacki@microsoft.com>; Gao, Liming <gaoliming@byosoft.com.cn>
Subject: Re: [edk2-devel] failed Pr

It has been rerun.

From: devel@edk2.groups.io <devel@edk2.groups.io> on behalf of Ard Biesheuvel <ardb@kernel.org>
Sent: Monday, May 29, 2023 7:44:37 AM
To: Rebecca Cran <rebecca@bsdio.com>
Cc: devel@edk2.groups.io <devel@edk2.groups.io>; Michael Kinney <michael.d.kinney@intel.com>; Michael Kubacki <michael.kubacki@microsoft.com>; Liming Gao (Byosoft address) <gaoliming@byosoft.com.cn>
Subject: Re: [edk2-devel] failed Pr

On Mon, 29 May 2023 at 16:37, Rebecca Cran <rebecca@bsdio.com> wrote:
>
> It looks like the agent or machine running the CI task crashed.
>
> "##[error]We stopped hearing from agent Azure Pipelines 18. Verify the
> agent machine is running and has a healthy network connection. Anything
> that terminates an agent process, starves it for CPU, or blocks its
> network access can cause this error. For more information, see:
> https://go.microsoft.com/fwlink/?linkid=846610"
>

Hmm, it would be nice if this thing could distinguish between 'error
in your code' and 'internal error' where the latter does not mark your
PR as being rejected.

>
>
>
>
> The only way I've found to make CI run again is to do something to cause
> the commit hash to change, for example by making a change to ReadMe.rst
> then reverting it.
>

Mike Kinney mentioned last time that there is a button I could push. Mike?

I am reluctant to make unnecessary changes to the state of the branch
just to trick the CI into having another go at it.