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

Ansible Role for Runner Deployment #23704

Open
benyanke opened this issue Mar 25, 2023 · 1 comment
Open

Ansible Role for Runner Deployment #23704

benyanke opened this issue Mar 25, 2023 · 1 comment
Labels
topic/gitea-actions related to the actions of Gitea type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@benyanke
Copy link
Contributor

benyanke commented Mar 25, 2023 •
edited
Loading

Feature Description

I think it would be great if there was an ansible role for runner deployment, handling downloading the binary, setting up the service, starting it on boot, registering (related #23703), etc.

I do have one started for my own private use that I'm using now. I'd be happy to contribute it upstream if there was interest in making an official gitea ansible role for runner deployment. I think that would make adoption much easier.

Screenshots

No response
@benyanke benyanke added type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first. labels Mar 25, 2023
@wolfogre wolfogre added the topic/gitea-actions related to the actions of Gitea label Mar 27, 2023
@nodiscc
Copy link
Contributor

nodiscc commented Nov 21, 2023

I wrote a role to deploy an act-runner instance https://github.com/nodiscc/xsrv/tree/master/roles/gitea_act_runner (will probably list it in https://gitea.com/gitea/awesome-gitea#scripts as well). However it is "opinionated" about the way the runner is deployed (to keep deployment simple, I won't support all possible configuration settings, different OS/distributions, etc.) and I wouldn't have time to maintain an "official" role. It's under GPLv3 so feel free to fork it, or file bugs and features requests in the issue tracker.

abdelhousni pushed a commit to abdelhousni/awesome-gitea that referenced this issue Oct 26, 2024
@nodiscc
add nodiscc.xsrv.gitea_act_runner ansible role (#142)
7be1f3f 
- ref. https://gitea.com/gitea/awesome-gitea/pulls/97
- ref. go-gitea/gitea#23704

----

This is similar to https://gitea.com/gitea/awesome-gitea/pulls/97 and I would write a summary for it like I did last time, **but** as you can see, the commit seems to have changed all line endings (I committed from the web interface).

Steps to reproduce:
- Fork https://gitea.com/gitea/awesome-gitea/ from the web UI
- navigate to README.md, click the edit button
- add one line
- select `Create a new branch for this commit and start a Pull Request`, enter a commit message
- click the `Propose file change button`
- the diff shows all lines as changed (217 additions, 216 deletions)

Please let me know how I should proceed.

Reviewed-on: https://gitea.com/gitea/awesome-gitea/pulls/142
Reviewed-by: techknowlogick <techknowlogick@noreply.gitea.com>
Reviewed-by: John Olheiser <john+gitea@jolheiser.com>
Co-authored-by: nodiscc <nodiscc@gmail.com>
Co-committed-by: nodiscc <nodiscc@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
topic/gitea-actions related to the actions of Gitea type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@nodiscc @benyanke @wolfogre