Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

gitea actions not working #28277

Closed
zhangbaojia opened this issue Nov 29, 2023 · 7 comments
Closed

gitea actions not working #28277

zhangbaojia opened this issue Nov 29, 2023 · 7 comments
Labels
issue/not-a-bug The reported issue is the intended behavior or the problem is not inside Gitea

Comments

@zhangbaojia
Copy link

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
@zhangbaojia
Copy link
Author

docker logs

giteaLog:

gite_log

act-runnerLog:

runner_logs

@yp05327
Copy link
Contributor

yp05327 commented 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 yp05327 mentioned this issue Nov 29, 2023
Merged
@techknowlogick techknowlogick added type/question Issue needs no code to be fixed, only a description on how to fix it yourself. and removed type/bug labels Nov 29, 2023
@zhangbaojia
Copy link
Author

zhangbaojia commented Nov 29, 2023 •
edited
Loading

runner：
image

runs-on：
image

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

@yp05327
Copy link
Contributor

yp05327 commented Nov 29, 2023

Have no idea. So strange. 😕

@zhangbaojia
Copy link
Author

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

@yp05327
Copy link
Contributor

yp05327 commented 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. 😕

@lunny lunny added type/bug and removed type/question Issue needs no code to be fixed, only a description on how to fix it yourself. labels Dec 5, 2023
@lunny lunny added this to the 1.21.2 milestone Dec 5, 2023
@lunny
Copy link
Member

lunny commented Dec 7, 2023

This is because your labels are not matched.

@lunny lunny closed this as completed Dec 7, 2023
@lunny lunny removed this from the 1.21.2 milestone Dec 7, 2023
@lunny lunny added issue/not-a-bug The reported issue is the intended behavior or the problem is not inside Gitea and removed type/bug labels Dec 7, 2023
@GiteaBot GiteaBot mentioned this issue Dec 18, 2023
Merged
lunny pushed a commit that referenced this issue Dec 18, 2023
@yp05327
Only check online runner when detecting matching runners in workflows (…
4ea522f 
…#28286)

Mentioned:
[#28277](#28277 (comment))

We should only check online runner when detecting matching runners in
workflows,
as if runner is not online, the workflow will not run.


![image](https://github.com/go-gitea/gitea/assets/18380374/11855e9d-7241-4b7a-b8d7-49dbb94ba1c5)
GiteaBot pushed a commit to GiteaBot/gitea that referenced this issue Dec 18, 2023
@yp05327 @GiteaBot
Only check online runner when detecting matching runners in workflows (…
4a197e1 
…go-gitea#28286)

Mentioned:
[go-gitea#28277](go-gitea#28277 (comment))

We should only check online runner when detecting matching runners in
workflows,
as if runner is not online, the workflow will not run.


![image](https://github.com/go-gitea/gitea/assets/18380374/11855e9d-7241-4b7a-b8d7-49dbb94ba1c5)
lunny pushed a commit that referenced this issue Dec 19, 2023
@GiteaBot @yp05327
Only check online runner when detecting matching runners in workflows (…
d9aeb1f 
…#28286) (#28512)

Backport #28286 by @yp05327

Mentioned:
[#28277](#28277 (comment))

We should only check online runner when detecting matching runners in
workflows,
as if runner is not online, the workflow will not run.


![image](https://github.com/go-gitea/gitea/assets/18380374/11855e9d-7241-4b7a-b8d7-49dbb94ba1c5)

Co-authored-by: yp05327 <576951401@qq.com>
fuxiaohei pushed a commit to fuxiaohei/gitea that referenced this issue Jan 17, 2024
@yp05327 @fuxiaohei
Only check online runner when detecting matching runners in workflows (…
ee0e318 
…go-gitea#28286)

Mentioned:
[go-gitea#28277](go-gitea#28277 (comment))

We should only check online runner when detecting matching runners in
workflows,
as if runner is not online, the workflow will not run.


![image](https://github.com/go-gitea/gitea/assets/18380374/11855e9d-7241-4b7a-b8d7-49dbb94ba1c5)
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
issue/not-a-bug The reported issue is the intended behavior or the problem is not inside Gitea
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@lunny @techknowlogick @yp05327 @zhangbaojia