How a Jenkins Job Broke our Jenkins UI

Re:How a Jenkins Job Broke our Jenkins UI by bfung on Thursday June 03, 2021 @11:31PM (#27390263)

I've used Jenkins for a long time, long enough to have used Hudson (Jenkins is a fork of Hudson due to Oracle drama).

The alternatives listed in reply to your thread are all much better than Jenkins, from system design, to usability, to cost of ownership of the personnel needed and tech debt incurred. Here's my own opinionated list, having used or evaluated them before:

1. GitlabCI 2. Circle CI 3. Travis CI 4. Github Actions 5. TeamCity 6. Concourse CI

Jenkins just happen to have been around a long time. It's like Jira -- everyone uses it, but nobody likes it.

[ Parent | on HN ]

Re:How a Jenkins Job Broke our Jenkins UI by avereveard on Friday June 04, 2021 @04:53AM (#27391828)

Jenkins has an important niche: "overgrown or enterprise projects that were initially created without ci in mind and require a ugly, hacky pipline to build"

I think it still has no rival in that area and it's also why is getting a bad rep.

[ Parent | on HN ]