I have used Jenkins a lot in in my career for automated builds, automated
testing, continuous integration, all that crap. It's a great solution for
that. But managers big on 'DevOps' want the visibility of pipelines, which
Jenkins supports via Groovy, a big hairy extension to Java, a big hairy
language. It's total overkill for just getting some jobs to show their
live status when all it really needed was a way to tag steps within a
job.
So as a learning experiment I decided to write my own build/CI server
in pure Go, which didn't impose any domain-specific language on the
job automation process. It's implemented as a single Go file (well,
two actually -- the second file's just to customize the job artifact
browser).
I use it to schedule and monitor all of my personal project builds.
Try it out if you want a build/CI server that is easy to install and
just stays out of your way.