|
| ▲ | cobertos 2 hours ago | parent | next [-] |
| It's based on act[0] so it's quite like GitHub actions but not completely [1]. I found in the current version of Forgejo the most secure way to set it up was just to put the runner on a different host. There's a Docker in Docker setup [2] that was challenging to get working correctly but still didn't quite feel secure... After setting it all up, I'm convinced GitHub actions as a concept is flawed. I wish the community would make a simpler git-defined CI/CD that didn't have the crazy surface area that actions does... Named shell scripts that can call out to other stuff in the runner Docker image and report it to the UI would be a nice start. [0]: https://github.com/nektos/act [1]: https://forgejo.org/docs/v15.0/user/actions/github-actions/#... [2]: https://forgejo.org/docs/v15.0/admin/actions/docker-access/#... |
| |
| ▲ | dboreham an hour ago | parent [-] | | Agreed. GitHub Actions feels like someone's science project created while on a mushroom trip. Really you just want a thing that executes a shell script in a runner. |
|
|
| ▲ | vinnymac 2 hours ago | parent | prev | next [-] |
| If you know GitHub actions then you’ll immediately understand Forgejo actions. It was designed that way intentionally. There are some differences, but at least for me not enough to warrant any pitchforks. If you have advanced use cases you might be more frustrated, but I’m not aware of any off the top of my head. I think my biggest complaint is that they haven’t exposed action logs over the API, so I can’t build tooling around them at the CLI level, feed them to an LLM, or more quickly diagnose problems that arise without using the website. |
| |
| ▲ | mfenniak an hour ago | parent [-] | | A basic API to access Actions logs was added in Forgejo v16. `/api/v1/repos/{owner}/{repo}/actions/jobs/{job_id}/logs` | | |
| ▲ | vinnymac an hour ago | parent [-] | | Nice! I was hoping they would add this in v16. Unfortunately I am still on v15 of all my instances of Forgejo |
|
|
|
| ▲ | Arrowmaster 2 hours ago | parent | prev | next [-] |
| You can use any CI/CD you want. The only reason GH is popular is that it's free for public repos. But Forgejo does have a GH like CI/CD. If you really care about good CI/CD then you should try some of the alternatives out and decide what works best for your needs. |
| |
| ▲ | Valodim 2 hours ago | parent | next [-] | | What can you recommend? | | |
| ▲ | Arrowmaster an hour ago | parent [-] | | I don't have any specific recommendations other than do as little in your CI/CD as possible, instead do as much as possible in your build system or scripts that get called by CI/CD. This way you can migrate with less work or run locally when you want. |
| |
| ▲ | dreamcompiler an hour ago | parent | prev | next [-] | | > The only reason GH is popular is that it's free for public repos. It's also free for private repos, and I have both. Codeberg doesn't like private repos, so unfortunately I cannot just move everything to Codeberg. I'll probably set up a Forgejo VPS somewhere. | |
| ▲ | esafak an hour ago | parent | prev [-] | | More than that, it is integrated with Github. |
|
|
| ▲ | td-andrew an hour ago | parent | prev | next [-] |
| Hooks directly into drone.io using SSO. Self host both of them on my internal network. Technically old version of gitea which is forgejo pre-fork |
|
| ▲ | 2 hours ago | parent | prev | next [-] |
| [deleted] |
|
| ▲ | bogwog an hour ago | parent | prev [-] |
| Extremely yes |
