Comment by 999900000999
8 days ago
Jenkins is open source and very well documented.
GitHub Actions are really for just short scripts. Don't take your Miata off road.
8 days ago
Jenkins is open source and very well documented.
GitHub Actions are really for just short scripts. Don't take your Miata off road.
LOL, I worked on the Jenkins project paid for three years. Even they use actions to build Jenkins.
https://github.com/jenkinsci/jenkins/tree/master/.github/wor...
Jenkins! For the love of god don’t listen to this.
Always open to learning, what's wrong with Jenkins?
It's a bit bloated, but it's free and works.
Fragile against upgrades, tons of unmaintained plugins, admin panel UX is a mess where you struggle to find the stuff your are looking for, half backed transition to nicer UI (Blue Ocean) that has been ongoing for years, too many ways to setup jobs and integrates with repos, poor resource management (disk space, CPU, RAM), sketchy security patterns inadvertently encouraged.
This stuff is a nightmare to manage, and with large code bases/products, you need a dedicated "devops" just to babysit the thing and avoid it becoming a liability for your devs.
I'm actually looking forward our migration to GHEC from on-prem just because Github Actions, as shitty as they are, are far less of an headache than Jenkins.
Why is gha just for short scripts, out of interest?
It's just short on features.
I get the vibe it was never intended to seriously compete with real CI/CD systems.
But then people started using it as such, thus this thread is full of complaints.
What features is it missing that you would like to see it implement?
death before Jenkins