Why Do Enterprises Grow from Jenkins? Part 1: Fragile Instances

In this series, we’ll walk through these reasons for scaling Jenkins and explain how to recognize them in your own teams, from losing track of plugins to losing control of security and credential management. For example, you might lose sight of how many teams are on each instance, how many controllers are in use, who […]

In this series, we’ll walk through these reasons for scaling Jenkins and explain how to recognize them in your own teams, from losing track of plugins to losing control of security and credential management. For example, you might lose sight of how many teams are on each instance, how many controllers are in use, who has made changes to code and scripts or how many scripts are in use—keeping track of these administrative tasks can be a real challenge. While it’s important to closely monitor the financial implications of the compute resources you’ll require, this team-based approach boosts the performance and speed of your build jobs and reduces cross-team friction when managing plugin versions and agents’ needs.
Source: CloudBees