I can’t overstate how much I hate GitHub Actions. I don’t even remember hating any other piece of technology I used. Sure, I still make fun of PHP that I remember from times of PHP41, but even then I didn’t hate it. Merely I found it subpar technology to other emerging at the time (like Ruby on Rails or Django). And yet I hate GitHub Actions.
With Passion2.

Road to Hell
Day before writing these words I was implementing build.rs for my tmplr project. To save you a click - it is a file/project scaffold tool with human readable (and craftable) template files. I (personally) use it very often, given how easy it is to craft new templates, by hand or with aid of the tool, so check it out if you need a similar tool.

you are viewing a single comment's thread
view the rest of the comments
[–] 5 points 9 months ago (8 children)

Not saying it's perfect, but every job I've been at they're migrating away from Jenkins. And they never have a reason to do so other than shiny new toy. Jenkins has it's own problems, but I personally think it's litterally decades ahead of github actions.

I do like runners better than the default jenkins run baremetal on the server, however the runners are too blackbox. I wish there was a debug toggle on runners. Pause at step, then provide a console into the runner. Some runs litterally take hours, so adding some debug output, and rerunning makes troubleshooting tedious.

  • source
  • parent
  • hideshow 8 child comments
  • [–] 3 points 9 months ago (2 children)

    And they never have a reason to do so other than shiny new toy.

    Security. Jenkins has issues with every other plugin being a backdoor or version having some vulnerability.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 9 months ago (2 children)

    I've found the edit/test/debug loop in Jenkins to be much faster than Github Actions. It was quite a refreshing change when I made that transition.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 9 months ago (1 child)

    Yep, I think the only thing github actions has over jenkins is built in versioning. I wish in jenkins I could edit a pipeline and easily roll it back. Or even better have tags so if I break something the team can just use the previous tag while I figure it out.

  • source
  • parent
  • hideshow 1 child comment
  • Interesting. Were you using a Jenkinsfile? I'm not sure I completely understand your use case, but using a Jenkinsfile would mean that your entire pipeline would be defined in a file in source control, so you could roll it back if you made a change that didn't work quite right. Seems to be what your looking for if I'm understanding what you're looking for.

    https://www.jenkins.io/doc/book/pipeline/jenkinsfile/

  • source
  • parent
  • [–] 2 points 9 months ago (1 child)

    have you looked at solutions which emulate github actions locally?

    https://github.com/nektos/act this is one of them but I think I've seen one more.

    Github actions also has self hosted runners: https://docs.github.com/en/actions/concepts/runners/self-hosted-runners

  • source
  • parent
  • hideshow 1 child comment