4 ms·

The most comedic mistake is to have a running jenking in 2023

• comprev 3y ago
  The vast majority of gigs/jobs I've had which involved touching Jenkins were for the purpose of migrating elsewhere - Gitlab, GitHub Actions, Drone, Harness...
• paulddraper 3y ago
  Highly customizable CI tool.
  • ActorNightly 3y ago
    ..written in Java. In case anyone needs reminding, Java developers, on purpose, put a line in a logging library that can fetch and execute code when given a url string for a log statement. Nobody should be touching anything Java in 2023.
    • Smeevy 3y ago
      Yes, we all sat down and unanimously agreed that we should perform JNDI lookups to execute arbitrary code stored in an LDAP directory. No regrets.
      • amoss 3y ago
        Java, Not Even Once.
      • onionisafruit 3y ago
        I remember that meeting. It was the one where we all wore togas and drank the java kool aid from goblets before we voted on that. All 5,000,000 of us.
      • ActorNightly 3y ago
        You joke, but that code made it through rounds of reviews, and nobody saw anything wrong with having a logging library able to make network requests in the first place. I honestly don't even blame the developers of Log4J that much, because after all its open source, and nobody is paying them to use it despite the idiocy surrounding shit like that. I do however blame the developers that use Java, see things like this happen, and then continue to use it with Log4j after the patch like nothing ever happened.
        • wil421 3y ago
          Since developers can just decide to rewrite a code base because Java is not a shiny new language.
      • imtringued 3y ago
        JNDI is an obscure feature from the Java Enterprise Edition days that nobody really uses nowadays.
• deleted 3y ago
  [deleted]
• deleted 3y ago
  [deleted]
• okdood64 3y ago
  What's the most comparable alternative to use for self-hosted CI in 2023? Curious.