Opened 5 months ago

Last modified 3 months ago

#33253 new enhancement

Ephemeral patchbot on GH Actions

Reported by: mkoeppe Owned by:
Priority: major Milestone: sage-9.7
Component: scripts Keywords:
Cc: chapoton Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description (last modified by mkoeppe)

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

Follow-ups:

  • 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

Change History (8)

comment:1 Changed 5 months ago by mkoeppe

  • Description modified (diff)

comment:2 Changed 5 months ago by mkoeppe

  • Description modified (diff)

comment:3 Changed 5 months ago by mkoeppe

  • Description modified (diff)

comment:4 Changed 5 months ago by mkoeppe

  • Description modified (diff)

comment:5 follow-up: Changed 5 months ago by gh-tobiasdiez

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.

comment:6 in reply to: ↑ 5 Changed 5 months ago by mkoeppe

Replying to gh-tobiasdiez:

It's running one ci tool in another one.

GH Actions is not a CI, it runs CIs

comment:7 Changed 5 months ago by mkoeppe

  • Description modified (diff)

comment:8 Changed 3 months ago by mkoeppe

  • Milestone changed from sage-9.6 to sage-9.7
Note: See TracTickets for help on using tickets.