• bizdelnick@lemmy.ml
    link
    fedilink
    arrow-up
    51
    arrow-down
    2
    ·
    7 months ago

    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.

    • Oliver Lowe@apubtest2.srcbeat.com
      link
      fedilink
      arrow-up
      9
      ·
      7 months ago

      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!

      • gitamar@feddit.de
        link
        fedilink
        arrow-up
        8
        ·
        7 months ago

        Jenkins was called Hudson already a long time after being a prototype. We used it productively already.

    • bobburger@fedia.io
      link
      fedilink
      arrow-up
      5
      ·
      7 months 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.

    • bobburger@fedia.io
      link
      fedilink
      arrow-up
      1
      arrow-down
      3
      ·
      7 months 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.