forgejo-contrib-ansible-issues-29.md
Watch7
Star9
Fork
You've already forked ansible
CodeIssues 4Pull requestsReleases 5Activity
Open
opened 2026-02-13 13:34:00 +01:00 by stdevel · 5 comments
stdevel commented 2026-02-13 13:34:00 +01:00
Copy link
Hi,
thanks a lot for the effort maintaining an Ansible collection - highly appreciated!
It would be nice to also have an Ansible role for installing and configuring a Forgejo Actions runner. I will have a look at it - maybe I can contribute some code for this.
Keep up the good work 👍
Hi, thanks a lot for the effort maintaining an Ansible collection - highly appreciated! It would be nice to also have an Ansible role for installing and configuring a Forgejo Actions runner. I will have a look at it - maybe I can contribute some code for this. Keep up the good work 👍
l3d commented 2026-02-13 13:35:22 +01:00
Collaborator
Copy link
something like this? https://galaxy.ansible.com/ui/repo/published/l3d/git/content/role/forgeo_runner/
something like this? https://galaxy.ansible.com/ui/repo/published/l3d/git/content/role/forgeo\_runner/
stdevel commented 2026-02-16 20:03:27 +01:00
Author
Copy link
@l3d wrote in #29 (comment):
something like this? https://galaxy.ansible.com/ui/repo/published/l3d/git/content/role/forgeo_runner/
That looks promising - having problems to use the collection along with my other collections though:
$ ansible-galaxy collection install -r collections/requirements.yml
Starting galaxy collection install process
Process install dependency map
ansible-galaxy is looking at multiple versions of l3d.git to determine which version is compatible with other requirements. This could take a while.
[ERROR]: Failed to resolve the requested dependencies map. Could not satisfy the following requirements:
* community.general:>=1.0.0 (dependency of devsec.hardening:10.5.0)
* community.general:>=6.6.0,<12.0.0 (dependency of fedora.linux_system_roles:1.120.2)
* community.general:>=1.0.0 (dependency of maxhoesel.borgbackup:4.0.2)
* community.general:>=12.0.0,<13.0.0 (dependency of l3d.git:1.1.13)
Need to deep-dive on this.
@l3d wrote in https://codeberg.org/forgejo-contrib/ansible/issues/29#issuecomment-10559692: > something like this? https://galaxy.ansible.com/ui/repo/published/l3d/git/content/role/forgeo\_runner/ That looks promising - having problems to use the collection along with my other collections though: command $ ansible-galaxy collection install -r collections/requirements.yml Starting galaxy collection install process Process install dependency map ansible-galaxy is looking at multiple versions of l3d.git to determine which version is compatible with other requirements. This could take a while. [ERROR]: Failed to resolve the requested dependencies map. Could not satisfy the following requirements: * community.general:\>=1.0.0 (dependency of devsec.hardening:10.5.0) * community.general:\>=6.6.0,\<12.0.0 (dependency of fedora.linux_system_roles:1.120.2) * community.general:\>=1.0.0 (dependency of maxhoesel.borgbackup:4.0.2) * community.general:\>=12.0.0,\<13.0.0 (dependency of l3d.git:1.1.13) Need to deep-dive on this.
pat-s commented 2026-03-01 10:48:52 +01:00
Collaborator
Copy link
Alternatively, there is devxy.cicd.forgejo_runner.
Alternatively, there is devxy.cicd.forgejo_runner.
👀 1
kwoot commented 2026-03-23 10:16:41 +01:00
Copy link
Notwithstandig all previous efforts on making a Forgejo-runner installer, there seems to be only one forgejo.forgejo namespace in the Ansible collections. To me, as a really stupid (so I've been told) IT person it seems like this repository is the most obvious place to add some role to install a runner. Most likely, as the open source saying goes, continue building on the shoulders of giants. These are of course my 2 cents and do not carry a lot of weight.
Notwithstandig all previous efforts on making a Forgejo-runner installer, there seems to be only one forgejo.forgejo namespace in the Ansible collections. To me, as a really stupid (so I've been told) IT person it seems like this repository is the most obvious place to add some role to install a runner. Most likely, as the open source saying goes, continue building on the shoulders of giants. These are of course my 2 cents and do not carry a lot of weight.
pat-s commented 2026-04-21 09:46:59 +02:00
Collaborator
Copy link
Notwithstandig all previous efforts on making a Forgejo-runner installer, there seems to be only one forgejo.forgejo namespace in the Ansible collections.
Can't really follow what you want to say here: of course there can only be one namespace named forgejo in Ansible Galaxy. This one is pretty new though and others have done work on their end beforehand to implement a runner role.
It is often way easier to init and maintain a role on your own that does things how you like it instead of porting or discussing within a community role on what the best approach would be to install and configure forgejo runner given the many ways it can be installed and configured (host, container, dind or not, etc.).
It would of course be great to have a role in here and have "everything" in one place but because Forgejo and Codeberg are very opinionated on how development has to happen and what tools are available for it, it isn't so easy or attractive to everyone.
Nevertheless, anyone interested in doing so is of course invited to contribute a runner role - but keep it mind that it would also come with the burden to maintain it properly and make use of the automated dependency updates we have in place here.
> Notwithstandig all previous efforts on making a Forgejo-runner installer, there seems to be only one forgejo.forgejo namespace in the Ansible collections. Can't really follow what you want to say here: of course there can only be one namespace named forgejo in Ansible Galaxy. This one is pretty new though and others have done work on their end beforehand to implement a runner role. It is often way easier to init and maintain a role on your own that does things how you like it instead of porting or discussing within a community role on what the best approach would be to install and configure forgejo runner given the many ways it can be installed and configured (host, container, dind or not, etc.). It would of course be great to have a role in here and have "everything" in one place but because Forgejo and Codeberg are very opinionated on how development has to happen and what tools are available for it, it isn't so easy or attractive to everyone. Nevertheless, anyone interested in doing so is of course invited to contribute a runner role - but keep it mind that it would also come with the burden to maintain it properly and make use of the automated dependency updates we have in place here.
Sign in to join this conversation.
No Branch/Tag specified
main
chore/cleanup-frontend
ci/release-workflow
v1.2.1
v1.2.0
v1.1.1
v1.1.0
v1.0.0
Labels Clear labels No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
Notifications Subscribe
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".
No due date set.
Dependencies
No dependencies set.
Reference
forgejo-contrib/ansible#29
WritePreview
Loading…
Add table
| Rows | | | Columns | |
CancelOK
Add a link
Url Description Hint: With a URL in your clipboard, you can paste directly into the editor to create a link.
CancelOK
CancelSave
Reference in a new issue
Repository
forgejo-contrib/ansible
Title
Body
Create issue
No description provided.
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?
No Yes