github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-16 13:13:23 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

gitea actions not working #12111

New Issue
Closed
opened 2025-11-02 09:58:42 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-02 09:58:42 -06:00
Owner
Copy Link

Originally created by @zhangbaojia on GitHub (Nov 29, 2023).

Description

The steps are as follows:
step1: Installing gite
gitea

step2:  Modify file app.ini and get Token

step3: Installing act_runner

gitea-runner

step4:  add  yarml

yaml

step5:  runners configuration

lookup

step6:   commit and push

setp7:   output result

nonfun

Why is the compilation not performed? Is there any configuration missing?

Gitea Version

1.21

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

CPE OS Name: cpe:/o:centos:centos:7 Kernel: Linux 3.10.0-862.el7.x86_64

How are you running Gitea?

Install "gitea" and "act-runner" simultaneously using docker on a single server.
gitea-runner

Database

SQLite

Originally created by @zhangbaojia on GitHub (Nov 29, 2023). ### Description The steps are as follows: step1: Installing gite ![gitea](https://github.com/go-gitea/gitea/assets/19427334/601f561c-1c29-4929-acc0-326fe4e07670) step2: Modify file app.ini and get Token step3: Installing act_runner ![gitea-runner](https://github.com/go-gitea/gitea/assets/19427334/893d7c16-c7b6-49ba-ac3c-5474d2cfd489) step4: add yarml ![yaml](https://github.com/go-gitea/gitea/assets/19427334/7bbe98dd-0e1f-4593-b3d5-3987277dc0be) step5: runners configuration ![lookup](https://github.com/go-gitea/gitea/assets/19427334/263126f3-31b7-4e7a-8217-6f05c7e94b97) step6: commit and push setp7: output result ![nonfun](https://github.com/go-gitea/gitea/assets/19427334/afd6ddd8-02fd-49d9-bca5-e89b90e5ce3f) Why is the compilation not performed? Is there any configuration missing? ### Gitea Version 1.21 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System CPE OS Name: cpe:/o:centos:centos:7 Kernel: Linux 3.10.0-862.el7.x86_64 ### How are you running Gitea? Install "gitea" and "act-runner" simultaneously using docker on a single server. ![gitea-runner](https://github.com/go-gitea/gitea/assets/19427334/0c058012-4822-42a2-8bc4-2e38ffb71638) ### Database SQLite
GiteaMirror added the issue/not-a-bug label 2025-11-02 09:58:42 -06:00
GiteaMirror commented 2025-11-02 09:58:44 -06:00
Author
Owner
Copy Link

@zhangbaojia commented on GitHub (Nov 29, 2023):

docker logs

giteaLog:

gite_log

act-runnerLog:

runner_logs

@zhangbaojia commented on GitHub (Nov 29, 2023): docker logs giteaLog: ![gite_log](https://github.com/go-gitea/gitea/assets/19427334/b48b0570-50df-42b6-9bd3-e339885e6dd4) act-runnerLog: ![runner_logs](https://github.com/go-gitea/gitea/assets/19427334/07c5e8ce-bb4e-4e09-b0c9-01be47e32fb9)
GiteaMirror commented 2025-11-02 09:58:44 -06:00
Author
Owner
Copy Link

@yp05327 commented on GitHub (Nov 29, 2023):

runs-on should match runner's label.

ps: When we check matching runner, it seems that we should also check the runner's status.

@yp05327 commented on GitHub (Nov 29, 2023): `runs-on` should match runner's label. ps: When we check matching runner, it seems that we should also check the runner's status.
GiteaMirror commented 2025-11-02 09:58:44 -06:00
Author
Owner
Copy Link

@zhangbaojia commented on GitHub (Nov 29, 2023):

runner：
image

runs-on：
image

@yp05327 recreate container, but it still did not take effect！

@zhangbaojia commented on GitHub (Nov 29, 2023): runner： ![image](https://github.com/go-gitea/gitea/assets/19427334/0d2e4e9e-37b7-4c36-953b-6b7dd94ddd28) runs-on： ![image](https://github.com/go-gitea/gitea/assets/19427334/b03348dd-0542-49c2-a163-45e40c8958c4) @yp05327 recreate container, but it still did not take effect！
GiteaMirror commented 2025-11-02 09:58:44 -06:00
Author
Owner
Copy Link

@yp05327 commented on GitHub (Nov 29, 2023):

Have no idea. So strange. 😕

@yp05327 commented on GitHub (Nov 29, 2023): Have no idea. So strange. 😕
GiteaMirror commented 2025-11-02 09:58:45 -06:00
Author
Owner
Copy Link

@zhangbaojia commented on GitHub (Dec 1, 2023):

After many tests, it was found that the problem was that the installation of runner on an offline server could not even run the basic operation。

微信截图_20231201212313

微信截图_20231201211828

@zhangbaojia commented on GitHub (Dec 1, 2023): After many tests, it was found that the problem was that the installation of runner on an offline server could not even run the basic operation。 ![微信截图_20231201212313](https://github.com/go-gitea/gitea/assets/19427334/b295fab0-b612-42d0-8799-9c444ddd9151) ![微信截图_20231201211828](https://github.com/go-gitea/gitea/assets/19427334/bc32befd-0df7-43b3-838f-3c2be7526c87)
GiteaMirror commented 2025-11-02 09:58:45 -06:00
Author
Owner
Copy Link

@yp05327 commented on GitHub (Dec 4, 2023):

I tried to run Gitea in DevContainer and disabled the network interface of docker in the host.
But I didn't reproduce this issue. 😕

@yp05327 commented on GitHub (Dec 4, 2023): I tried to run Gitea in DevContainer and disabled the network interface of docker in the host. But I didn't reproduce this issue. 😕
GiteaMirror commented 2025-11-02 09:58:45 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Dec 7, 2023):

This is because your labels are not matched.

@lunny commented on GitHub (Dec 7, 2023): This is because your labels are not matched.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/not-a-bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#12111
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?