Jenkins

“You can do a lot more than GitHub actions with a lot less complexity than Jenkins.”

“Compared to GitHub Actions or Jenkins its a pretty poor experience”

“we needed to maintain our own jenkins infrastructure for CI/CD”

“Jenkins had many problems. But I would argue that the solutions were always grounded in the Linux userland.”

“Nice and simple (even if the scripts sometimes got insane)”

“intensely grateful that despite rumblings, the company I contract to hasn't switched from self-hosted Jenkins”

“maybe we should stay on our old crusty self-hosted Jenkins setup”

“My experience with any tool that offers non-developer UI for developer-related activities was overall infuriatingly negative”

“Feels like using a free Jenkins gets you everything you want.”

“shell script execution was part of Jenkins from day 1, to my knowledge, over 20 years ago now”

“at that point Jenkins is mostly acting as a nice frontend to all those cronjobs and shell scripts”

“A GUI that lists all the available options is much more user-friendly than a YAML configuration file”

“Jenkins has possibly the worst user experience of any piece of software I've had to use in the last few years.”

“Jenkins CI has a clever feature where every password it injects will be redacted if printed to stdout”

“the security model, reliability and backup/restore story has gotten seismically better in the intervening decade”

“It's too old and easy-to-use for anyone to hype it up as the next cool thing.”

“biggest flaw of jenkins is that by default it runs on builder env, as it was made pre-container era”

“its the most flexible and fastest CI system I have ever used”

“It parsed the log output with regular expressions and presented new warnings and errors in a nice table.”

“Once it was updated to latest and all the bad old manually created jobs were removed it was decent.”

“My last two employers had rock solid Jenkins environments because they were set up as close to vanilla as possible.”

“Jenkins had a lot of issues and I'm glad to not be using it overall”

“I wish more applications would adopt the 'H' option that Jenkins uses in it's cron notation”

“It is overwhelmingly less resource-intensive to maintain over time than any Jenkins server.”

“simple and clear pipelines setup that autobuild any branch we want”

“Jenkins is in every way a “Java” program, and not the good kind.”

“Jenkins is the worst form of CI, except for all those other forms that have been tried”

“Self-hosting Jenkins on an EC2 instance is probably going to result in a _better_ experience at this point.”

“everything is kinda janky on Jenkins, but everything falls into an expectable corridor of jank you get used to”

“It's decent out of the box, but if you load it down with a billion plugins”

“it was far more stable, but a pain to maintain and understand”

“their only real exposure to it is as the DSL of gradle and jenkins”

“Jenkins was just build in pre-container way so a lot of stuff”

“Couldn't move it into containers (or anywhere for that matter) without really digging in.”

“I've had my setup broken once after updating Jenkins and not being able to update the plugins to match the newer Jenkins version.”

“Anyone who has ever used Gitlab, or dare my foul mouth say Jenkins, has experienced a better system than Github actions.”

“It's one of the few CI tools where you can test your pipeline without committing it.”

“DSL is incredibly helpful at scale. IAC is incredibly helpful at scale.”

“What makes Jenkins stand out IMO is the community and the core maintainers”

“The trouble is that the tool itself doesn't guide you much to the good path”