Post #2441023
2026-01-14 17:05 UTC
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.
Replies (3)
-
@moonpiedumplings@programming.dev 2026-01-14 18:11
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
-
@namingthingsiseasy@programming.dev 2026-01-15 01:39
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.
-
@dublet@lemmy.world 2026-01-14 18:40
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.