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

Gitea Actions - could not find runner by label #11300

New Issue
Closed
opened 2025-11-02 09:33:43 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 09:33:43 -06:00
Owner
Copy Link

Originally created by @sgabenov on GitHub (Jul 21, 2023).

Description

Gitea - v 1.20.0
Runner - tested on 0.2.3 (linux) and nightly v0.2.3-10-g1a7ec5f
Runner - INFO Registering runner, arch=amd64, os=linux, version=v0.2.3-10-g1a7ec5f

I have configured Gitea Actions, added and registered runner, but all jobs are not executed. I can see on UI, that it could not find runner by label. But the label exists. See attached screenshots.

Gitea Version

1.20.0

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

actions_0 actions_1 actions_2 ubunt

Git Version

No response

Operating System

ubuntu 22.10

How are you running Gitea?

docker

Database

PostgreSQL

Originally created by @sgabenov on GitHub (Jul 21, 2023). ### Description Gitea - v 1.20.0 Runner - tested on 0.2.3 (linux) and nightly v0.2.3-10-g1a7ec5f Runner - INFO Registering runner, arch=amd64, os=linux, version=v0.2.3-10-g1a7ec5f I have configured Gitea Actions, added and registered runner, but all jobs are not executed. I can see on UI, that it could not find runner by label. But the label exists. See attached screenshots. ### Gitea Version 1.20.0 ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots <img width="1800" alt="actions_0" src="https://github.com/go-gitea/gitea/assets/15741789/bc603557-93cc-498b-849f-27d7945967ad"> <img width="712" alt="actions_1" src="https://github.com/go-gitea/gitea/assets/15741789/f49c63bb-77ea-46c7-b8b8-0baa061bd29c"> <img width="725" alt="actions_2" src="https://github.com/go-gitea/gitea/assets/15741789/36ae868e-4ed0-4346-921d-40a4dc845712"> ubunt ### Git Version _No response_ ### Operating System ubuntu 22.10 ### How are you running Gitea? docker ### Database PostgreSQL
GiteaMirror added the topic/gitea-actionsissue/needs-feedbacktype/bug labels 2025-11-02 09:33:43 -06:00
GiteaMirror commented 2025-11-02 09:33:44 -06:00
Author
Owner
Copy Link

@CaiCandong commented on GitHub (Jul 24, 2023):

I can't reproduce the bug, are you able to provide more details?

@CaiCandong commented on GitHub (Jul 24, 2023): I can't reproduce the bug, are you able to provide more details?
GiteaMirror commented 2025-11-02 09:33:44 -06:00
Author
Owner
Copy Link

@wolfogre commented on GitHub (Jul 24, 2023):

Let me guess.

  • According to the screenshot, the type of the runner is "Individual", so it means that you have registered a runner for your own account, not an organization or the entire instance.
  • And you tried to test Actions on sandbox/gitea-actions, I am not sure, but sandbox doesn't sound like a username, maybe it's a organization?
  • If I'm right, you should register a runner for sandbox, not your own account.
@wolfogre commented on GitHub (Jul 24, 2023): Let me guess. - According to the screenshot, the type of the runner is "Individual", so it means that you have registered a runner for your own account, not an organization or the entire instance. - And you tried to test Actions on `sandbox/gitea-actions`, I am not sure, but `sandbox` doesn't sound like a username, maybe it's a organization? - If I'm right, you should register a runner for `sandbox`, not your own account.
GiteaMirror commented 2025-11-02 09:33:45 -06:00
Author
Owner
Copy Link

@sgabenov commented on GitHub (Jul 24, 2023):

@wolfogre Thank you! Indeed, the runner was configured not for organization, but for individual.

@CaiCandong - There is a problem in documentation, actual links to configure actions are different, compared to this article:
https://docs.gitea.com/next/usage/actions/act-runner#obtain-a-registration-token

Actual links to Gitea 1.20 are:
Global: https://<gitea_url>/admin/actions/runners
Organization: https://<gitea_url>/org/(org_name)/settings/actions/runners
Individual: https://<gitea_url>/user/settings/actions/runners

Also i wold recommend to add information how to configure it from UI as well to this page (https://docs.gitea.com/next/usage/actions/quickstart)

Global: Site Administration > Actions > Runners
Organization: Explore > Organizations > (org_name) > Settings > Actions > Runners
Individual: User > Settings > Actions > Runners

@sgabenov commented on GitHub (Jul 24, 2023): @wolfogre Thank you! Indeed, the runner was configured not for organization, but for individual. @CaiCandong - There is a problem in documentation, actual links to configure actions are different, compared to this article: https://docs.gitea.com/next/usage/actions/act-runner#obtain-a-registration-token Actual links to Gitea 1.20 are: Global: https://<gitea_url>/admin/actions/runners Organization: https://<gitea_url>/org/(org_name)/settings/actions/runners Individual: https://<gitea_url>/user/settings/actions/runners Also i wold recommend to add information how to configure it from UI as well to this page (https://docs.gitea.com/next/usage/actions/quickstart) Global: Site Administration > Actions > Runners Organization: Explore > Organizations > (org_name) > Settings > Actions > Runners Individual: User > Settings > Actions > Runners
GiteaMirror commented 2025-11-02 09:33:45 -06:00
Author
Owner
Copy Link

@CaiCandong commented on GitHub (Jul 24, 2023):

@sgabenov Thank you a lot for your suggestion

@CaiCandong commented on GitHub (Jul 24, 2023): @sgabenov Thank you a lot for your suggestion
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/needs-feedback topic/gitea-actions type/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#11300
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?