Continuous Integration with Jenkins

This is 25 question set of Continuous Integration with Jenkins. Please NOTE that all questions and answers are based on our research and self-study.

What is Continuous Integration with Jenkins?

Continuous Integration (CI) is a software development practice where developers integrate their code changes frequently and automatically into a shared repository. The main goal of CI is to detect and resolve integration issues early in the development cycle, thereby reducing the cost and time involved in resolving issues later.

Overall, Continuous Integration with Jenkins helps developers to detect and resolve issues early in the development cycle, thereby improving the quality of the software and reducing the time and cost involved in resolving issues later.

1. Jenkins allows you to :
Ans: All of the options

2. Jabber is a :
Ans: Messaging plugin

3. The project type supported by Jenkins is/are:
Ans: All of the options

4. Which of the following statement is true about Jenkins?
Ans: Jenkins supports plugins to showcase both metrics and trends

5. Which of the following functionality is not supported by Jenkins?
Ans: Code

6. Which of the following is an artifact repository that can be configured as a plugin for Jenkins?
Ans: Nexus

7. Jenkins can manage job dependencies using the?
Ans: File Fingerprinting

8. Job-status notifications can be sent in JSON or XML formats from Jenkins, without extending its functionality.
Ans: False

9. Record of multiple builds is displayed using a
Ans: Weather icon

10. Jenkins build job cannot be triggered manually?
Ans: False

11. In the build status images, which of the following statement is correct?
Ans: Partial Sun with clouds icon in the status means 20-40% of the recent builds failed

12. Copy artifacts’ is an option that is available for selection under the
Ans: Build Step

13. If you have multiple projects and if you need to check for new updates, every five minutes, which is the correct CRON expression that Jenkins can use to avoid polling all the projects at the same time.
Ans: H/5 * * * *

14. Build can be triggered :
Ans: All of the options

15. Functional testing can be automated using Jenkins.
Ans: True

16. File usage across Jenkins jobs can be tracked using :
Ans: Fingerprints

17. View of upstream and downstream connected jobs that form a build pipeline is provided by:
Ans: Build Pipeline Plugin

18. Jenkins can be configured to monitor external jobs like CRON jobs :
Ans: Choose the ‘Monitor External job’ option under the ‘Build Step’ section

19. Users can now implement the entire build, deploy and test using the:
Ans: All of the options

20. Jenkins builds the source code :
Ans: In its own workspace.

21. Master and slave nodes communicate through :
Ans: None of the options

22. Backups can be automated using :
Ans: ThinBackup plugin

23. An amber ball in the build status refers to an unstable build?
Ans: False

24. In a distributed build environment, the master computer can not execute any build and only slaves are capable of running build jobs
Ans: True

25. If you want to track which top build projects are using which middle and bottom build projects, what has to be done?
Ans: Relevant projects to be configured to record fingerprints

Jenkins pipeline Jenkins pipeline Jenkins pipeline Jenkins pipeline

Must Read:

Leave a Reply

Your email address will not be published. Required fields are marked *