You have taken over a build environment where Jenkins is responsible for scanning for changes made in a Git repository every hour and then applying that build to a few dozen web servers. As part of that job, Jenkins also is responsible for completing some scripted performance-based Visit us athttps://www.examsboost.com/test/cje/ Leading the way in IT testing and certification tools, www.examkiller.net tests and, depending on the defined results, marking the build as complete and notifying the team OR rolling back the build, notifying the team, and marking it as failed. You notice that the build itself is now taking longer than an hour to complete, which is affecting the push of new changes on occasion. What changes could you make to your Jenkins environment to alleviate the amount of time it takes to complete and test a build so that the hourly schedule is more likely to be kept?
- Create additional Jenkins Masters and deploy the job to each one. Schedule the job staggered by 30 minutes on each one so that the additional master servers won’t be busy if the first job runs long.
- Add one or more slave nodes to the environment, this will allow us to deploy code to multiple end points at one time. Break up the single job into multiple jobs so that each one can be triggered by the successful completion of the previous job to eliminate scheduling problems on beginning a new build in the event subsequent steps run longer than the intended time period.
- None of these
- Remove the performance testing from the build. Schedule performance testing as a separate job 30 minutes after the build runs and trigger a rollback if the performance testing fails at this point.
Answer(s): B
Explanation:
As the load of your Jenkins setup expands, you can distribute the burden by adding one or more slave nodes.