Comment on

• yaroto98@lemmy.world ⁨3⁩ ⁨days⁩ ago

  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

  • dublet@lemmy.world ⁨3⁩ ⁨days⁩ ago

    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

    • yaroto98@lemmy.world ⁨3⁩ ⁨days⁩ ago

      And the Actions in the marketplace aren’t?

      My employers have only allowed a very small subset of each. It’s super frustrating having to reinvent the wheel constantly.

      source

      • tal@lemmy.today ⁨3⁩ ⁨days⁩ ago

        I wonder if problems could be mostly avoided by running potentially-unsafe code in a container without network access.

        source
  • namingthingsiseasy@programming.dev ⁨3⁩ ⁨days⁩ ago

    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

    • yaroto98@lemmy.world ⁨3⁩ ⁨days⁩ ago

      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

      • namingthingsiseasy@programming.dev ⁨3⁩ ⁨days⁩ ago

        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.

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

        source
  • moonpiedumplings@programming.dev ⁨3⁩ ⁨days⁩ ago

    have you looked at solutions which emulate github actions locally?

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

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

    source

    • dublet@lemmy.world ⁨3⁩ ⁨days⁩ ago

      Never found act useful. Where I work, we have our own self hosted instance, including self hosted runners and it doesn’t really improve the situation WRT debugging an Action.

      source
• jeena@piefed.jeena.net ⁨3⁩ ⁨days⁩ ago

  I like zuul quite a lot, it’s a bit complicated to set up first but once it’s runnint’s really cool, especially the gating mechanisms can’t be found anywhere else and the dependencies between jobs are very intuitive too.

  source