Using a test Jenkins instance
Continuous Integration (CI) servers are critical in the creation of deterministic release cycles. Any long-term instability in the CI will reflect in a slowing down of the rate at which milestones are reached in your project plans. Incremental upgrading is addictive and mostly straightforward, but should be seen in the light of a Jenkins critical role—a software project's life cycle.
Before releasing plugins to your Jenkins production server, it is worth aggressively deploying to a test Jenkins instance and then sitting back and letting the system run jobs. This gives you enough time to react to any minor defects found.
There are many ways to set up a test instance. One is to use a virtual image of Ubuntu and share ...