Ephemeral patchbot on GH Actions

[mkoeppe]

PR sagemath/sage-patchbot#155 adds a GH Actions workflow to sage-patchbot, which runs the patchbot in a Docker container using one of the pre-built images that our CI pushes to https://github.com/orgs/sagemath/packages?repo_name=sage

Follow-ups:

• .github/workflows/run_patchbot.yml: Actually handle github.event.inputs.patchbot_ticket sage-patchbot#156 (fixup)

• .github/workflows/run_patchbot_cygwin.yml: New sage-patchbot#157 (Cygwin)

• Run as a scheduled workflow on GH Actions. Users who fork the GitHub repo can activate the workflow by depositing a repository secret SAGE_PATCHBOT_ENVS of the form ubuntu-focal-standard ubuntu-hirsute-standard .... The workflow would create 1 job per platform listed there

CC: @fchapoton

Component: scripts

Issue created by migration from https://trac.sagemath.org/ticket/33253

[mkoeppe]

Description changed:

--- 
+++ 
@@ -2,3 +2,4 @@
 
 Users who fork the GitHub repo can activate the workflow by depositing a repository secret `SAGE_PATCHBOT_ENVS` of the form `ubuntu-focal-standard ubuntu-hirsute-standard ...`. The workflow would create 1 job per platform listed there and run the patchbot on a few tickets.
 
+https://wiki.sagemath.org/patchbot

[mkoeppe]

Description changed:

--- 
+++ 
@@ -3,3 +3,6 @@
 Users who fork the GitHub repo can activate the workflow by depositing a repository secret `SAGE_PATCHBOT_ENVS` of the form `ubuntu-focal-standard ubuntu-hirsute-standard ...`. The workflow would create 1 job per platform listed there and run the patchbot on a few tickets.
 
 https://wiki.sagemath.org/patchbot
+
+https://github.com/mkoeppe/sage-patchbot/actions/workflows/run_patchbot.yml
+

[mkoeppe]

Description changed:

--- 
+++ 
@@ -4,5 +4,7 @@
 
 https://wiki.sagemath.org/patchbot
 
+PR: https://github.com/sagemath/sage-patchbot/pull/155
+
 https://github.com/mkoeppe/sage-patchbot/actions/workflows/run_patchbot.yml
 

[mkoeppe]

Description changed:

--- 
+++ 
@@ -1,10 +1,7 @@
-The patchbot would run as a scheduled workflow on GH Actions.
+PR https://github.com/sagemath/sage-patchbot/pull/155 adds a GH Actions workflow to sage-patchbot, which runs the patchbot in a Docker container using one of the pre-built images that our CI pushes to https://github.com/orgs/sagemath/packages?repo_name=sage
 
-Users who fork the GitHub repo can activate the workflow by depositing a repository secret `SAGE_PATCHBOT_ENVS` of the form `ubuntu-focal-standard ubuntu-hirsute-standard ...`. The workflow would create 1 job per platform listed there and run the patchbot on a few tickets.
 
-https://wiki.sagemath.org/patchbot
 
-PR: https://github.com/sagemath/sage-patchbot/pull/155
+Follow-up:
+- Run as a scheduled workflow on GH Actions.  Users who fork the GitHub repo can activate the workflow by depositing a repository secret `SAGE_PATCHBOT_ENVS` of the form `ubuntu-focal-standard ubuntu-hirsute-standard ...`. The workflow would create 1 job per platform listed there
 
-https://github.com/mkoeppe/sage-patchbot/actions/workflows/run_patchbot.yml
-

[tobiasdiez]

comment:5

Is this really necessary? It's running one ci tool in another one. I would say its more flexible to convert the patchbot steps into github workflows, as we have already done with the linter and #33263. This should replace the patchbots completely in the long term.

[mkoeppe]

comment:6

Replying to @tobiasdiez:

It's running one ci tool in another one.

GH Actions is not a CI, it runs CIs

[mkoeppe]

Description changed:

--- 
+++ 
@@ -2,6 +2,10 @@
 
 
 
-Follow-up:
+Follow-ups:
+- https://github.com/sagemath/sage-patchbot/pull/156 (fixup)
+
+- https://github.com/sagemath/sage-patchbot/pull/157 (Cygwin)
+
 - Run as a scheduled workflow on GH Actions.  Users who fork the GitHub repo can activate the workflow by depositing a repository secret `SAGE_PATCHBOT_ENVS` of the form `ubuntu-focal-standard ubuntu-hirsute-standard ...`. The workflow would create 1 job per platform listed there
 

[mkoeppe]

comment:10

Completed, can be closed