120
Jenkins was invented b/c an engineer “got tired of incurring the wrath of his team every time his code broke the build.” (graphite.dev)
submitted 2 years ago by to c/programming@programming.dev
27 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 49 points 2 years ago (4 children)

Jenkins is not a modern CI. It is a historical milestone, but if you read an article you should see that it was replaced by other tools. Now I don't recommend considering Jenkins for new projects. It it fast to set up but extremely hard to support and full of old bugs and legacy code. Writing Groovy pipelines is much harder than pipelines in gitlab/github/forgejo/etc. Tens of plugins you have to use even for simple tasks have inconsistent syntax, many of them are buggy, they often become unsupported or deprecated. This all consumes lot of resourses: I maintain an instance that eats ~4G of RAM being idle.

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] 9 points 2 years ago (1 child)

    and full of old bugs and legacy code.

    The feeling of reading through those crazy JVM stack traces with classes named "hudson" from the Jenikins prototype... I shudder! Well done for pushing through it all!

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 5 points 2 years ago

    I have a soft spot for Jenkins because it was the first integration tool I ever used fresh out of college.

    But today I want to stab the server because a job started failing randomly with a permission error when trying to copy a file.

  • permalink
  • fedilink
  • source
  • parent
  • [–] -2 points 2 years ago

    I have a soft spot for Jenkins because it was the first integration tool I ever used fresh out of college.

    But today I want to stab the server because a job started failing randomly with a permission error when trying to copy a file.

  • permalink
  • fedilink
  • source
  • parent