Answers
- Correct answer: A
Explanation:
The Jenkins plugin for GitHub must be installed first to enable the integration. Then, a personal access token is created on GitHub, which is used for authenticating Jenkins with GitHub. This token is added to Jenkins as a secret text credential. Only after these steps are completed can the final configuration in Jenkins’ global settings be performed, establishing the full integration.
- Correct answer: False
Explanation:
The GitHub plugin for Jenkins does indeed provide seamless integration with GitHub pull requests. It allows Jenkins to automatically build and validate code changes proposed in pull requests.
- Correct answer: B
Explanation:
The Jenkins plugin for SonarQube must be installed first to enable the integration. Then, a personal access token is created on SonarQube, which is used for authenticating Jenkins with SonarQube. This token is added to Jenkins as a secret text credential. Only after these steps are completed can...