3 ms·

> The first CI system whose configuration file is, like, Lua, will become a billion dollar business overnight. Jenkinsfile is written in Groovy and is not a bi

> The first CI system whose configuration file is, like, Lua, will become a billion dollar business overnight. Jenkinsfile is written in Groovy and is not a billion dollar business that I'm aware of. Were you trying to emphasize the lua part? Space from JetBrains has its build config written in Kotlin, for a more strongly typed version: https://www.jetbrains.com/help/space/automation-getting-started.html https://www.jetbrains.com/help/space/automation-getting-star... I believe there are others but those are the two I have handy

no_wizard 6y ago
Jenkins has persistent problems in my experience with reliability. We only ever really got shell scripts to work well with Jenkins at a previous place of employment years ago. The API layer was hard to leverage properly (part of what I was getting at in my rant. Which is why I get why configuration has taken over a lot of these kinds of complex systems) I think a lot of this got fixed with Jenkins X because its underlying tech is just docker images. There again though you're mostly managing complex configuration rather than dealing with an exposed API layer