Clojurians Log v2
architecture
I'm looking at jenkins and i'm like... why. Why introduce a build tool with a new obscure language. Why not just write it in babashka or bash or whatever.
I'm looking at the majority of the existing languages, and I'm like "Why introduce a new language when you can use Lisp?"
Yes, exactly.
At this point Jenkins literally looks like a programming language with a gui to me right now.
More specifically, it's Java. Like i want to keep an open mind, but at a certain point that's a liability to.
It means your going to get dragged into what ever marketed solution someone dangles in front of you. So I'm curious when someone was writing bash scripts and was like "oh no" , and they turned to jenkins.
> So I'm curious when someone was writing bash scripts and was like "oh no" , and they turned to jenkins. I'm not a groovy fan, but I would choose it over bash in no time
Ok, babashka then...
Been a while, last I used Jenkins it had "free style" builds which were just running shell commands
At a previous job we would export the xml that defined the Jenkins jobs, keep it in git then had a Jenkins build that watching that hit repo and re-pit the xml into Jenkins on any changes, was great
I constantly face two kinds of push back: 1. "You can't build your own X, have to use a battle tested library" a. You can't just write your own CI ! Let's use Jenkins instead. 2. "You can't just do that... can't you?" a. You can't just run this on one machine with a local SQLite... Can't You? It's not web-scale, what about fail over? Should you at least use mongo?
@mstoyukhin thanks for the suggestion, at a glance that seems to be built by tools i have more of a familarity with then jenkins, and so it would be a nice option. I think at this stage, left to my own devices (which i never am) i would just build something from tools I was intimately familiar with. To my weary eyes, a lot of what seemed like innovation was really someone elses convention.
Haven't used Jenkins in ages, but GitHub Actions/GitLab CI are basically both also declarative languages. Simpler, sure, but still plenty of space for corner cases and arcane knowledge you must learn. To @didibus's point: I wonder how hard it would be to make a Babashka-based CI workflow engine, just featureful enough to be used as a replacement thinking-face (Vibe coding session! 😬)
Can jenkins just shell out to say clojure or babashka? I haven’t used it since forever
Yes, it can shell out.