Jenkins CLI + Emacs = Butler

tag(s): #programming #overblown-minor-annoyances #emacs This is yet another gripping tale of "do everything in Emacs". In this case running Jenkins jobs. It is also a good overview of my current approach to building Emacs packages. Which is by half-assing them. The scenario We run deployments at work with an in-house CLI tool. Why not use Jenkins/Octopus/Bamboo/Whatever directly to move code around? I have no idea. Actually, a better way to put it is: I think we could do it, maybe even should. But I am not idealistic enough to have volunteered to, you know, actually make it happen. I accepted the CLI as part of our workflow: it is mature, stable, and at this point I can modify to support whatever we require. Just accept that part. Like I do. :) Also, as I said, it is a CLI. I always have a shell buffer open in the server. Time to run a deploy? Easy peasy. Except that the powers that be decided we need to click around a web page instead of an easy to use CLI. Why, oh why, misguided…