But, as for me specifically, there are two and a half answers: I wanted to run VSCodium's build locally, which act for sure puked about. Then, while trying to troubleshoot that, I thought I'd try something simpler and have it run the lint job from act's own repo <https://github.com/nektos/act/blob/1252e551b8672b1e16dc8835d...> to rule out "you're holding it wrong" type junk. It died with
[checks/lint] Failure - Main actions/setup-go@v3
[checks/lint] failed to create exec: Error response from daemon: Container b9059f831d3a1549c9902cabc7e5258231b2a7291b2692eaa33f976794059738 is not running
and no amount of --verbose would tell me what, specifically, "Failure" means or what action I'm supposed to take about it
Finally, I believe I am pretty self-service when projects are written in sane programming languages and publish under a permissive license, so the "and a half" is that I tried to introduce some better logging or fix up some of the more egregious silliness that I found in the codebase, but ultimately it felt like I was pushing a boulder uphill so I let that go. I haven't been following the progress of any of the 1100 forks on GH, or the hundreds of Gitea forks, or whatever the hell is going on with Forgejo nowadays
But my experience is that if the thing can't run its own workflows, or at least emit some constructive action that I, the user, can take about that situation, then the VSCodium one that I linked to has no prayer
Fair, but I definitely wasn't trolling, and I really appreciate your comment. 2 days ago I told myself I'd set up gitea actions after experimenting with drone, buildbot, earthly, and Jenkins and not being fully satisfied with any (Jenkins feels old and runners were annoying to set up, buildbot was too involved and didnt have a ui, and I couldn't find an execution environment for earthly to run in on git push).
Personally, I put more weight in real-world complaints than issue trackers. For example, everyone I know that uses OBS has never had a single complaint, yet there are 400 open issues. I was looking for an example of what real users run into and I just couldn't find that looking at the 11-month old hn article or reddit. Based on your comment, I will keep that in mind and bail at the first sign of frustrating behavior.
I guess I'll give my opinion here for anyone who's looking for CI or CD. Earthly is a really cool CI tool, but as far as I know, it doesn't have an actual run component. Think of it like make for the docker era, and it does that very well. Drone is cool, but it runs in docker, so trying to build docker images with earthly (also runs in docker) is a pain unless you mount your docker sock, which I don't want to do. Jenkins is the most functional and handles all use cases. There's a reason it's still so huge in the self-hosted world.
I don't think treating every mention of act as an opportunity for airing of personal grievances is helpful in a discussion when there's already ample reports of people's concrete issues with it, had one looked at the 800 issues in its repo https://github.com/nektos/act/issues?q=is%3Aissue or the 239 from gitea's for https://gitea.com/gitea/act_runner/issues or whatever is going on with Forgejo's fork https://code.forgejo.org/forgejo/act .
But, as for me specifically, there are two and a half answers: I wanted to run VSCodium's build locally, which act for sure puked about. Then, while trying to troubleshoot that, I thought I'd try something simpler and have it run the lint job from act's own repo <https://github.com/nektos/act/blob/1252e551b8672b1e16dc8835d...> to rule out "you're holding it wrong" type junk. It died with
and no amount of --verbose would tell me what, specifically, "Failure" means or what action I'm supposed to take about itFinally, I believe I am pretty self-service when projects are written in sane programming languages and publish under a permissive license, so the "and a half" is that I tried to introduce some better logging or fix up some of the more egregious silliness that I found in the codebase, but ultimately it felt like I was pushing a boulder uphill so I let that go. I haven't been following the progress of any of the 1100 forks on GH, or the hundreds of Gitea forks, or whatever the hell is going on with Forgejo nowadays
But my experience is that if the thing can't run its own workflows, or at least emit some constructive action that I, the user, can take about that situation, then the VSCodium one that I linked to has no prayer