Untangling Jenkins
I&#x27;ve been a build&#x2F;release engineer for quite a few years now, most spent using Jenkins.<p>It can be quite a heavyweight beast, especially since it&#x27;s written in Java (so heavy in terms of resource usage) and since it&#x27;s old (so lots of legacy in terms of architecture).<p>Still, in terms of costs and scalability (up to the level where you have thousands of developers and you probably want to roll your own), I think it is one of the best tools out there for its role as a prettier cron&#x2F;queuing system.<p>A few tips:<p>* if you can afford it, stop ASAP using the UI for configurating jobs; look into Pipelines or the JobDSL, based on your needs<p>* once you have more than a few jobs, stop running anything on the master node, for increased stability<p>* use the minimum number of plugins and tie as few things to Jenkins as possible; script as many things and put the scripts into version control<p>* backup the global configuration; you can try to version control it but it&#x27;s tricky; at least back it up periodically and most of the time it is enough<p>That&#x27;s it for now, for more details, $200&#x2F;h :p