Actions re-run not working in Gitea 1.25 #15064

Closed
opened 2025-11-02 11:29:17 -06:00 by GiteaMirror · 1 comment
Owner

Originally created by @merlinz01 on GitHub (Oct 29, 2025).

Description

If I click "Re-run all jobs" or the re-run button for a specific job, it doesn't start the actions workflow. The run icon changes to a gray circle and the cancel button appears. The old job logs remain.

This is only since I updated the Gitea instance today.

Gitea Version

1.25 (released today)

Can you reproduce the bug on the Gitea demo site?

No - no actions runners available

Logs

Oct 29 19:16:56 gitea[1000856]: 2025/10/29 19:16:56 .../actions/notifier_helper.go:167:notify() [W] Ref of event "workflow_run" is empty, will fall back to the default branch
Oct 29 19:16:56 gitea[1000856]: 2025/10/29 19:16:56 HTTPRequest [I] router: completed POST /myuser/myrepo/actions/runs/203/jobs/0/rerun for x.x.x.x:32213, 200 OK in 184.8ms @ actions/view.go:401(actions.Rerun)
Oct 29 19:16:56 gitea[1000856]: 2025/10/29 19:16:56 HTTPRequest [I] router: completed GET /myuser/myrepo/actions/runs/203 for x.x.x.x:32213, 200 OK in 32.6ms @ actions/view.go:52(actions.View)

Screenshots

After clicking "re-run" on the three jobs with gray circles:

Image

The old logs are still there. The Cancel button has no effect.

Image

Git Version

2.39.5

Operating System

Debian 12

How are you running Gitea?

linux amd64 binary from release page, run as systemd service on Debian 12

Database

PostgreSQL

Originally created by @merlinz01 on GitHub (Oct 29, 2025). ### Description If I click "Re-run all jobs" or the re-run button for a specific job, it doesn't start the actions workflow. The run icon changes to a gray circle and the cancel button appears. The old job logs remain. This is only since I updated the Gitea instance today. ### Gitea Version 1.25 (released today) ### Can you reproduce the bug on the Gitea demo site? No - no actions runners available ### Logs ``` Oct 29 19:16:56 gitea[1000856]: 2025/10/29 19:16:56 .../actions/notifier_helper.go:167:notify() [W] Ref of event "workflow_run" is empty, will fall back to the default branch Oct 29 19:16:56 gitea[1000856]: 2025/10/29 19:16:56 HTTPRequest [I] router: completed POST /myuser/myrepo/actions/runs/203/jobs/0/rerun for x.x.x.x:32213, 200 OK in 184.8ms @ actions/view.go:401(actions.Rerun) Oct 29 19:16:56 gitea[1000856]: 2025/10/29 19:16:56 HTTPRequest [I] router: completed GET /myuser/myrepo/actions/runs/203 for x.x.x.x:32213, 200 OK in 32.6ms @ actions/view.go:52(actions.View) ``` ### Screenshots After clicking "re-run" on the three jobs with gray circles: <img width="965" height="326" alt="Image" src="https://github.com/user-attachments/assets/5df04f9b-4086-4e1b-8641-ceac19985bc2" /> The old logs are still there. The Cancel button has no effect. <img width="1606" height="219" alt="Image" src="https://github.com/user-attachments/assets/60edc753-7c89-4b1e-a1b2-16835008255c" /> ### Git Version 2.39.5 ### Operating System Debian 12 ### How are you running Gitea? linux amd64 binary from release page, run as systemd service on Debian 12 ### Database PostgreSQL
GiteaMirror added the issue/confirmedtopic/gitea-actionstype/bug labels 2025-11-02 11:29:17 -06:00
Author
Owner

@lunny commented on GitHub (Nov 2, 2025):

This should be resolved by #35784

@lunny commented on GitHub (Nov 2, 2025): This should be resolved by #35784
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#15064