Hi Sean, I see the "rerun" button on the "checks" page of GitHub from my login.
We have a mix of both Azure Pipelines and GitHub Actions today, so I think it is important to see the "rerun" from GitHub view for Maintainers. This github page describes the feature, but not the permissions required. https://docs.github.com/en/actions/managing-workflow-runs/re-running-workflows-and-jobs We currently have EDK II Maintainer Team set to "Triage Role" permissions. From the table below, only "Write" and above are allowed to re-run. https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/repository-roles-for-an-organization#permissions-for-each-role "Write" permissions add a lot of options, so I think we should discuss tradeoffs in the next Tools/CI meeting. One option is to add a bot based on a new label to request failed jobs to be re-run. The bot can use a token with permissions to re-run. Best regards, Mike From: Sean Brogan <spbro...@outlook.com> Sent: Monday, May 29, 2023 8:37 AM To: Kinney, Michael D <michael.d.kin...@intel.com>; devel@edk2.groups.io; a...@kernel.org; Rebecca Cran <rebe...@bsdio.com> Cc: Kubacki, Michael <michael.kuba...@microsoft.com>; Gao, Liming <gaolim...@byosoft.com.cn>; Kinney, Michael D <michael.d.kin...@intel.com> Subject: Re: [edk2-devel] failed Pr 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 ________________________________ From: Kinney, Michael D <michael.d.kin...@intel.com<mailto:michael.d.kin...@intel.com>> Sent: Monday, May 29, 2023 8:13:32 AM To: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>>; spbro...@outlook.com<mailto:spbro...@outlook.com> <spbro...@outlook.com<mailto:spbro...@outlook.com>>; a...@kernel.org<mailto:a...@kernel.org> <a...@kernel.org<mailto:a...@kernel.org>>; Rebecca Cran <rebe...@bsdio.com<mailto:rebe...@bsdio.com>> Cc: Kubacki, Michael <michael.kuba...@microsoft.com<mailto:michael.kuba...@microsoft.com>>; Gao, Liming <gaolim...@byosoft.com.cn<mailto:gaolim...@byosoft.com.cn>>; Kinney, Michael D <michael.d.kin...@intel.com<mailto:michael.d.kin...@intel.com>> Subject: RE: [edk2-devel] failed Pr 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<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>> On Behalf Of Sean Sent: Monday, May 29, 2023 8:12 AM To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>; a...@kernel.org<mailto:a...@kernel.org>; Rebecca Cran <rebe...@bsdio.com<mailto:rebe...@bsdio.com>> Cc: devel@edk2.groups.io<mailto:devel@edk2.groups.io>; Kinney, Michael D <michael.d.kin...@intel.com<mailto:michael.d.kin...@intel.com>>; Kubacki, Michael <michael.kuba...@microsoft.com<mailto:michael.kuba...@microsoft.com>>; Gao, Liming <gaolim...@byosoft.com.cn<mailto:gaolim...@byosoft.com.cn>> Subject: Re: [edk2-devel] failed Pr It has been rerun. ________________________________ From: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>> on behalf of Ard Biesheuvel <a...@kernel.org<mailto:a...@kernel.org>> Sent: Monday, May 29, 2023 7:44:37 AM To: Rebecca Cran <rebe...@bsdio.com<mailto:rebe...@bsdio.com>> Cc: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>>; Michael Kinney <michael.d.kin...@intel.com<mailto:michael.d.kin...@intel.com>>; Michael Kubacki <michael.kuba...@microsoft.com<mailto:michael.kuba...@microsoft.com>>; Liming Gao (Byosoft address) <gaolim...@byosoft.com.cn<mailto:gaolim...@byosoft.com.cn>> Subject: Re: [edk2-devel] failed Pr On Mon, 29 May 2023 at 16:37, Rebecca Cran <rebe...@bsdio.com<mailto:rebe...@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";<https://go.microsoft.com/fwlink/?linkid=846610%22> > 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. -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#105390): https://edk2.groups.io/g/devel/message/105390 Mute This Topic: https://groups.io/mt/99199003/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/leave/9847357/21656/1706620634/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
