actions organization & forgejo-runner #155

Closed
opened 3 months ago by dachary · 12 comments
Owner

With 1.19 comes an internal CI named actions which adds new dependencies and one binary.

Dependencies actions

The internal CI relies on plugins to carry out actions.

There should be an organization similar to https://github.com/actions/ or https://gitea.com/actions for grouping actions that are provided by default by Forgejo. They would be Free Software and not subject to the scrutiny of a third party organization.

This can be bootstrapped with a mirror of the repositories from https://gitea.com/actions at https://codeberg.org/forgejo-actions.

Runner binary and container image

The https://gitea.com/gitea/act_runner daemon makes the link between Forgejo and the actions. It needs to be released as a new binary and container imges.

This can be done at https://codeberg.org/forgejo/runner

With 1.19 comes an internal CI named actions which adds new dependencies and one binary. ### Dependencies actions The internal CI relies on plugins to carry out actions. There should be an organization similar to https://github.com/actions/ or https://gitea.com/actions for grouping actions that are provided by default by Forgejo. They would be Free Software and not subject to the scrutiny of a third party organization. This can be bootstrapped with a mirror of the repositories from https://gitea.com/actions at https://codeberg.org/forgejo-actions. ### Runner binary and container image The https://gitea.com/gitea/act_runner daemon makes the link between Forgejo and the actions. It needs to be released as a new binary and container imges. This can be done at https://codeberg.org/forgejo/runner
dachary self-assigned this 3 months ago
dachary added this to the Forgejo v1.19 milestone 3 months ago
dachary changed title from forgejo-actions organization to forgejo-actions organization & forgejo-runner 3 months ago
Owner

forgejo-actions is going to be a reserved username in the near future, isn't it?

forgejo-actions is going to be a reserved username in the near future, isn't it?
Poster
Owner

Yes forgejo/forgejo#364 is merged and reserves it.

Yes https://codeberg.org/forgejo/forgejo/pulls/364 is merged and reserves it.
Owner

Won't that cause a problem? I suppose Codeberg could revert that particular change. What is the point of reserving that username, exactly?

Won't that cause a problem? I suppose Codeberg could revert that particular change. What is the point of reserving that username, exactly?
Collaborator

What is the point of reserving that username, exactly?

I'm guessing it's related to Gitea doing the same in 4011821 :

`gitea-actions` will become a reserved user name. If a user with the
name already exists in the database, it is recommended to rename it.
> What is the point of reserving that username, exactly? I'm guessing it's related to Gitea doing the same in [`4011821`](/forgejo/forgejo/commit/4011821c946e8db032be86266dd9364ccb204118) : ```md `gitea-actions` will become a reserved user name. If a user with the name already exists in the database, it is recommended to rename it. ```
Poster
Owner

https://codeberg.org/forgejo-actions was created and populated with mirrors to reflect what is available at https://gitea.com/actions

There is one commit that was discarded:

df5bacfff9

because the URLs it builds are 404.

And another one that is potentially useful

8c779dd49b

but was created 9 months ago so... not sure.

Now... this should be used to confirm it is actually useful to have.

https://codeberg.org/forgejo-actions was created and populated with mirrors to reflect what is available at https://gitea.com/actions * https://codeberg.org/forgejo-actions/setup-node * https://codeberg.org/forgejo-actions/go-versions * https://codeberg.org/forgejo-actions/setup-go * https://codeberg.org/forgejo-actions/checkout There is one commit that was discarded: https://gitea.com/actions/go-versions/commit/df5bacfff90bd484e0838a125baf01a9f2e4f48c because the URLs it builds are 404. And another one that is potentially useful https://gitea.com/actions/setup-go/commit/8c779dd49b301bda581f79473e48dce4b70abe7e but was created 9 months ago so... not sure. Now... this should be used to confirm it is actually useful to have.
Owner

https://gitea.com/ChristopherHX/actions_runner is a runner forked from https://gitea.com/gitea/act_runner (as of commit 715d0e85ced5c95d6def01840c0f78e1eac107b6). IFAIU Its purpose is to communicate with Gitea Actions and use https://github.com/ChristopherHX/runner.server to run the steps. Which is different from what https://gitea.com/gitea/act_runner which runs the steps using docker, all by itself.

https://github.com/ChristopherHX/runner.server is a fork of https://github.com/actions/runner that implements some of the features of the official GitHub runner.

https://gitea.com/ChristopherHX/actions_runner is a runner forked from https://gitea.com/gitea/act_runner (as of commit 715d0e85ced5c95d6def01840c0f78e1eac107b6). IFAIU [Its purpose is to communicate with Gitea Actions](https://github.com/ChristopherHX/github-act-runner/discussions/100#discussioncomment-5064830) and use https://github.com/ChristopherHX/runner.server to run the steps. Which is different from what https://gitea.com/gitea/act_runner which runs the steps using docker, all by itself. https://github.com/ChristopherHX/runner.server is a fork of https://github.com/actions/runner that implements [some of the features](https://github.com/ChristopherHX/runner.server#notes) of the official GitHub runner.
Owner
https://github.com/nektos/act does not yet support services https://github.com/nektos/act/issues/173
Owner

https://github.com/nektos/act#runners suggests that each workflow is run in a container but it is unclear if that is actually what act does. Or if it is expected that the person using act does so in a container.

https://github.com/nektos/act#runners suggests that each workflow is run in a container but it is unclear if that is actually what act does. Or if it is expected that the person using act does so in a container.
Owner

https://codeberg.org/forgejo-actions was created and populated with mirrors to reflect what is available at https://gitea.com/actions

It would not work because actions will then try to checkout https://codeberg.org/forgejo-actions/action/checkout which can't work. I renamed the organization to https://codeberg.org/actions (which was luckily not in use) so DEFAULT_ACTIONS_URL can be set to https://codeberg.org on Forgejo.

> https://codeberg.org/forgejo-actions was created and populated with mirrors to reflect what is available at https://gitea.com/actions > It would not work because actions will then try to checkout https://codeberg.org/forgejo-actions/action/checkout which can't work. I renamed the organization to https://codeberg.org/actions (which was luckily not in use) so DEFAULT_ACTIONS_URL can be set to https://codeberg.org on Forgejo.
dachary changed title from forgejo-actions organization & forgejo-runner to actions organization & forgejo-runner 3 months ago
Poster
Owner

Gitea v1.19.0-rc0 was released today. Forgejo v1.19.0-0-rc0 is scheduled to be released in a few days.

Based on the discussions above I will create:

Gitea v1.19.0-rc0 was released today. Forgejo v1.19.0-0-rc0 is scheduled to be released in a few days. Based on the discussions above I will create: * https://codeberg.org/forgejo/runner to be the equivalent of https://gitea.com/gitea/act_runner * https://codeberg.org/forgejo/act to be the soft-fork of https://github.com/nektos/act that Forgejo uses
Owner

It works well enough to try it out.

It works well enough to try it out.
Owner
v1.19.0-0-rc0 is released https://forgejo.org/2023-02-27-release-v1/ and tested with actions https://forgejo.org/2023-02-27-forgejo-actions/
earl-warren closed this issue 3 months ago
Sign in to join this conversation.
No Milestone
No Assignees
4 Participants
Notifications
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/meta#155
Loading…
There is no content yet.