Conversation

Notices

1. nixCraft 🐧 (nixcraft@mastodon.social)'s status on Wednesday, 20-Nov-2024 19:47:06 JST nixCraft 🐧

   Why does Jenkins have a bad reputation around here? Why do you hate it?

   • Michele Adduci (madduci@mastodon.social)'s status on Wednesday, 20-Nov-2024 20:24:38 JST Michele Adduci

     in reply to

     @nixCraft a lot of functionalities are available only through plugins and these are sources of headache, especially due to CVEs and non trivial intra-dependencies, which might lead to break Jenkins itself sometimes .

     An important feature such as backup is not even there, you can only do that through plugins or copying the correct files (ugh) which is, for 2024, very bad

   • hansvschoot (hansvschoot@mastodon.social)'s status on Wednesday, 20-Nov-2024 20:36:50 JST hansvschoot

     in reply to

     @nixCraft anybody who hates Jenkins, gets upset about the wrong things in life :-)

   • Michael Kohne (mhkohne@mastodon.social)'s status on Wednesday, 20-Nov-2024 21:04:20 JST Michael Kohne

     in reply to

     @nixCraft I used it for a number of years at job[-1], and it was...fine. Clunky in a lot of ways, and too many things are in pre-installed plug-ins that would interact strangely. I think it's also had a bunch of security issues over the years that make people twitchy (I just kept my instance off the internet).

   • Psycodepath (psycodepath@mastodon.social)'s status on Wednesday, 20-Nov-2024 21:44:56 JST Psycodepath

     in reply to

     @nixCraft at a Former Job we had a Project, that deployed one project to 12 instances.

     We could not add an Environment because we got a Method size too large jvm Error.

     It was nothing crazy just running Tests, compile FS and rsync to those instances.

     Never had an issue with that on gitlab ci

   • Joseph Lamoree (jlamoree@mastodon.social)'s status on Wednesday, 20-Nov-2024 22:33:41 JST Joseph Lamoree

     in reply to

     @nixCraft I was not aware of it having a bad reputation. Perhaps you have bad friends.

   • Mike Seymour (mikeseymour@mastodon.social)'s status on Wednesday, 20-Nov-2024 22:45:47 JST Mike Seymour

     in reply to

     @nixCraft Like any tool, it can make life easier or harder depending on how it's used. At my last job, I set it up to do a simple job which it did very well. At this job, long-departed people tried to make it do all manner of complicated things. We depend on it for a lot of testing, but it keeps breaking and no-one really understands the detail of what it's doing or why.

   • London Eastfield 🇵🇸 (lawmanlungis@mastodon.social)'s status on Thursday, 21-Nov-2024 15:03:22 JST London Eastfield 🇵🇸

     in reply to

     @nixCraft Because: Java

   • Erik “Lacraia” Magnusson (lacraia@mastodon.social)'s status on Thursday, 28-Nov-2024 16:45:39 JST Erik “Lacraia” Magnusson

     in reply to

     @nixCraft Because I’ve used it… My number one is that it doesn’t handle the churn and output of AAA game processes. Besides that, it has horrible monolithic architecture. Everything is in one machine and in files with no atomic write protection. If the UI stops working and needs restart your forced to restart the whole server. The protocol between node and server is flaky. We lose connection constantly even though they are in the same rack and at most are two short optical cables apart.