Jenkins®, is arguably one of the most popular development tools on the planet, with some reports estimating that over 70% of all continuous integration pipelines run on Jenkins. It’s great at helping small, agile development teams build, test, and deploy multiple times a day. Some estimates say Jenkins supports more than 180,000 sites, running 20 million jobs across more than 750,000 build agents.
Why consider Advanced Jenkins
However, as teams, environments, projects and market pressures increase, so do the administrative tasks associated with maintaining and administering Jenkins. Scaling Jenkins usage across a growing enterprise, without affecting the security or stability of its software development lifecycle (SDLC) is challenging, particularly for highly regulated industries.
CloudBees is the leading contributor of code commits for Jenkins and with over a decade of field experience in the DevOps space. That’s why in this whitepaper they will explain best practices used by companies of all sizes for setting up efficient, secure Jenkins pipelines.
- Why you should use just enough pipelines.
- Why you should say no to pipelines in programming languages.
- How to avoid creating a monolithic controller.
- What to consider in your plugin management strategy.
- The importance of using containers and Dockerfiiles for build agents.
And a flexible, governed and secure CI at scale.