Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The "goodness" of Jenkins for my use-case is that the service can be a kind of "sudo" for capabilities we don't want to spread around.

That said, learning Yet Another Language that only deals with a niche requirement is a total bore.

If we can cook it down to executing some garden-variety bash in a special context, along with some spiffy pipeline visualization, that is enough.



At the end of the day, its just the shell executing the commands :) sure, you can always distil it down to a script (or a set of scripts) and nothing wrong with it either - as always, depends on the context.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: