DevOps Shack

Jenkins Interview Questions

Click Here To Enrol To Batch-5 | DevOps & Cloud DevOps

1. What is Jenkins? Explain its key features.

Answer:
Jenkins is an open-source automation server that helps automate parts of software
development related to building, testing, and deploying, facilitating continuous
integration and continuous delivery.
Key Features:

• Easy Installation: Jenkins is a self-contained Java-based program, ready to run out-

of-the-box.
• Extensible: Jenkins can be extended via its plugin architecture.
• Distributed Builds: Jenkins can distribute build/test loads to multiple computers.
• Easy Configuration: Jenkins offers a simple and user-friendly web interface.

Example:
java -jar jenkins.war
This command starts Jenkins on your local machine.

2. Explain the Jenkins architecture.

Answer:
Jenkins architecture consists of:

• Jenkins Server: The central server that holds the configurations and executes build
pipelines.
 • Build Nodes: These are slave machines that handle the execution of build jobs
distributed by the Jenkins server.
• Jobs/Projects: Individual tasks configured to run by Jenkins.

Diagram:
[ Jenkins Server ] -> [ Build Node 1 ]
[ Build Node 2 ]
[ Build Node N ]

3. How do you configure a Jenkins job?

Answer:
To configure a Jenkins job:

1. Navigate to Jenkins dashboard.

2. Click on "New Item."
3. Enter the job name and select the type of job (e.g., Freestyle project).
4. Configure the job by specifying details like SCM, build triggers, build steps, and post-
build actions.

Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
echo 'Building...'
}
}
stage('Test') {
steps {
echo 'Testing...'
}
}
stage('Deploy') {
steps {
echo 'Deploying...'
}
}
}
}
This is a simple pipeline script for a Jenkins job.

4. What are Jenkins pipelines and how do you create them?

Answer:
Jenkins pipelines are a suite of plugins which support implementing and integrating
continuous delivery pipelines into Jenkins. A pipeline defines the entire lifecycle of
your project, including build, test, and deploy stages.
To create a pipeline:

1. Go to Jenkins dashboard.
2. Click on "New Item" and select "Pipeline."
3. Define your pipeline script in the Pipeline section.

Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
script {
echo 'Building...'
// Add build commands here
}
}
}
stage('Test') {
steps {
script {
echo 'Testing...'
// Add test commands here
}
}
}
stage('Deploy') {
steps {
script {
echo 'Deploying...'
// Add deploy commands here
}
}
}
}
}

5. Explain the concept of 'agent' in Jenkins pipeline.

Answer:
In Jenkins pipeline, an 'agent' specifies where the entire Pipeline or a specific stage of
the Pipeline will execute in the Jenkins environment.

Example:

• agent any runs the pipeline on any available agent.

• agent { label 'my-label' } runs the pipeline on an agent with the specified
label.
• agent { docker { image 'maven:3-alpine' } } runs the pipeline inside a
Docker container with the specified image.

Example:
pipeline {
agent { label 'linux' }
stages {
stage('Build') {
agent { docker { image 'maven:3-alpine' } }
steps {
echo 'Building inside a Docker container'
}
}
stage('Test') {
steps {
echo 'Testing on a Linux agent'
}
}
}
}

6. What are Jenkins plugins and how do you install them?

Answer:
Jenkins plugins extend Jenkins with additional features. Plugins can provide new
build steps, SCM integrations, report formats, and more.

To install a plugin:

1. Go to Jenkins dashboard.
2. Navigate to "Manage Jenkins" -> "Manage Plugins."
3. Select the "Available" tab.
4. Search for the desired plugin and install it.

Example: To install the Git plugin:

1. Go to "Manage Plugins."
2. Search for "Git plugin."
3. Check the box and click "Install without restart."

7. How do you secure Jenkins?

Answer:
To secure Jenkins:

1. Enable Security: Navigate to "Manage Jenkins" -> "Configure Global Security" and
enable security.
2. Authentication: Use Jenkins’ own user database or integrate with an external
authentication system (e.g., LDAP).
3. Authorization: Define who can do what within Jenkins.
4. SSL: Set up Jenkins to run over HTTPS.
 5. Security Plugins: Install security-related plugins (e.g., Role-based Authorization
Strategy).

Example:
pipeline {
agent any
stages {
stage('Secure Stage') {
steps {
script {
if (!env.SECURE_VARIABLE) {
error 'SECURE_VARIABLE is not set!'
}
}
}
}
}
}
This example demonstrates checking for a secure variable before proceeding with
the pipeline.

8. What is a Jenkinsfile and how do you use it?

Answer:
A Jenkinsfile is a text file that contains the definition of a Jenkins Pipeline and is
checked into source control. It allows the Pipeline to be versioned alongside the
project code.

Example:

• Create a Jenkinsfile in the root of your repository:

pipeline {
agent any
stages {
stage('Build') {
steps {
echo 'Building...'
}
}
stage('Test') {
steps {
echo 'Testing...'
}
}
stage('Deploy') {
steps {
echo 'Deploying...'
}
}
}
}

• Add and commit the Jenkinsfile to your repository.

 • Jenkins will detect the Jenkinsfile and use it to define the pipeline.

9. How do you use environment variables in Jenkins?

Answer:
Environment variables in Jenkins can be used to make the pipeline scripts more
dynamic. They can be accessed using env.VARIABLE_NAME.
Example:
pipeline {
agent any
environment {
MY_VAR = 'Hello, World!'
}
stages {
stage('Print Variable') {
steps {
echo "Value of MY_VAR: ${env.MY_VAR}"
}
}
}
}

10. How do you trigger Jenkins jobs?

Answer:
Jenkins jobs can be triggered in various ways:

1. Manually: Click "Build Now" on the Jenkins dashboard.

2. SCM Changes: Configure SCM polling in job settings.
3. Scheduled Builds: Use Cron syntax in job settings.
4. Build Triggers: Trigger builds after another project is built.
5. Webhooks: Use webhooks from external services like GitHub.

Example (Cron Trigger):

triggers {
cron('H */4 * * *')
}
This triggers the build every 4 hours.

11. Explain how Jenkins can be used for continuous integration.

Answer: Jenkins can automate the process of integrating code changes from
multiple contributors. When a developer commits code to the repository, Jenkins can
automatically:

• Pull the latest code from the SCM.

• Build the project.
 • Run tests to ensure the code changes do not break the build.
• Generate reports and notify developers of the build status.

Example: A simple pipeline that performs continuous integration:

pipeline {
agent any
stages {
stage('Checkout') {
steps {
git 'https://github.com/example/repo.git'
}
}
stage('Build') {
steps {
sh './build.sh'
}
}
stage('Test') {
steps {
sh './test.sh'
}
}
}
post {
always {
archiveArtifacts artifacts: '**/target/*.jar', fingerprint:
true
junit 'target/test-*.xml'
}
}
}

12. How do you configure Jenkins to integrate with GitHub?

Answer:

1. Install GitHub Plugin: Go to "Manage Jenkins" -> "Manage Plugins" and install the
GitHub plugin.
2. Create a New Job: Select "Freestyle project" or "Pipeline."
3. Configure Source Code Management: Under "Source Code Management," select
"Git" and provide the repository URL.
4. Add GitHub Webhook: In GitHub repository settings, add a webhook pointing to
your Jenkins server URL (e.g., http://your-jenkins-server/github-webhook/).
5. Set Build Triggers: Enable "GitHub hook trigger for GITScm polling" under "Build
Triggers."

Example:
pipeline {
agent any
stages {
stage('Checkout') {
steps {
 git url: 'https://github.com/example/repo.git', branch:
'main'
}
}
// Additional stages here
}
}

13. What are Jenkins Blue Ocean and its features?

Answer: Blue Ocean is a modern, user-friendly interface for Jenkins that simplifies
the creation and management of pipelines. Features:

• Visual pipeline editor.

• Intuitive visualization of pipeline stages.
• Integrated with GitHub and Bitbucket for easy pipeline creation.
• Improved user experience with a clean and responsive UI.

Example: Create a new pipeline in Blue Ocean:

1. Click on "New Pipeline" in the Blue Ocean interface.

2. Connect to your GitHub or Bitbucket repository.
3. Define your pipeline using the visual editor.

14. Explain the use of Jenkins environment variables with examples.

Answer: Environment variables can be used in Jenkins to pass configuration values

or secrets to build scripts.

Example:
pipeline {
agent any
environment {
MY_VAR = 'Hello, World!'
}
stages {
stage('Print Variable') {
steps {
echo "Value of MY_VAR: ${env.MY_VAR}"
}
}
}
}
This pipeline sets an environment variable MY_VAR and prints its value.

15. How do you handle credentials in Jenkins?

Answer: Jenkins provides a secure way to manage credentials. You can store
credentials (e.g., passwords, SSH keys) in Jenkins and use them in your jobs without
exposing them in scripts.

Steps to add credentials:

1. Go to "Manage Jenkins" -> "Manage Credentials."

2. Select a domain (e.g., global).
3. Click on "Add Credentials."
4. Enter the details (e.g., username, password, SSH key) and save.

Example: Using credentials in a pipeline:

pipeline {
agent any
environment {
GITHUB_CREDENTIALS = credentials('github-credentials-id')
}
stages {
stage('Checkout') {
steps {
git credentialsId: 'github-credentials-id', url:
'https://github.com/example/repo.git'
}
}
}
}
16. Explain the role of Jenkinsfile in CI/CD.
Answer: Jenkinsfile defines the pipeline as code, making it easier to manage,
version, and review. It allows you to define the entire CI/CD process in a single file.
Example: A Jenkinsfile for a simple CI/CD pipeline:
pipeline {
agent any
stages {
stage('Build') {
steps {
sh 'mvn clean install'
}
}
stage('Test') {
steps {
sh 'mvn test'
}
}
stage('Deploy') {
steps {
sh 'scp target/myapp.jar user@server:/path/to/deploy'
}
}
}
}

17. What are post-build actions in Jenkins?

Answer: Post-build actions are steps that run after the build has completed. They
can be used to perform tasks such as archiving artifacts, sending notifications, or
deploying applications.

Example: Configuring post-build actions:

pipeline {
agent any
stages {
stage('Build') {
steps {
sh 'mvn clean install'
}
}
}
post {
success {
mail to: '[email protected]',
subject: "Successful Build:
${currentBuild.fullDisplayName}",
body: "The build was successful."
}
failure {
mail to: '[email protected]',
subject: "Failed Build: ${currentBuild.fullDisplayName}",
body: "The build failed."
}
}
}

18. How do you implement parallel stages in Jenkins pipeline?

Answer: Parallel stages in Jenkins pipelines allow multiple stages to run

simultaneously.

Example:
pipeline {
agent any
stages {
stage('Parallel Execution') {
parallel {
stage('Unit Tests') {
steps {
sh 'mvn test'
}
}
stage('Integration Tests') {
steps {
sh 'mvn verify'
}
}
}
}
}
}
19. What is a declarative pipeline in Jenkins?

Answer: Declarative pipeline is a more structured and simpler way to define Jenkins
pipelines. It uses a predefined syntax and supports a richer set of features out-of-
the-box compared to scripted pipelines.

Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
echo 'Building...'
}
}
stage('Test') {
steps {
echo 'Testing...'
}
}
stage('Deploy') {
steps {
echo 'Deploying...'
}
}
}
}

20. Explain how to use the Jenkins Docker plugin.

Answer: The Jenkins Docker plugin allows Jenkins to use Docker containers as build
environments. It simplifies the process of creating isolated build environments for
Jenkins jobs.

Steps to use Docker plugin:

1. Install the Docker plugin from "Manage Jenkins" -> "Manage Plugins."
2. Configure Docker settings in "Manage Jenkins" -> "Configure System."
3. Use Docker in your pipeline or freestyle job.

Example: Using Docker in a pipeline:

pipeline {
agent {
docker {
image 'maven:3-alpine'
args '-v /root/.m2:/root/.m2'
}
}
stages {
stage('Build') {
steps {
sh 'mvn clean install'
 }
}
}
}

21. What is the difference between Declarative and Scripted Pipelines in

Jenkins?

Answer: Declarative Pipeline:

• More structured and simpler to write.

• Uses a predefined syntax.
• Supports a set of predefined steps and stages.
• Easier for newcomers to understand.

Scripted Pipeline:

• More flexible but complex.

• Uses Groovy scripting language.
• Can be more powerful due to the flexibility of Groovy.
• Suitable for advanced use cases.

Example (Declarative):
pipeline {
agent any
stages {
stage('Build') {
steps {
echo 'Building...'
}
}
stage('Test') {
steps {
echo 'Testing...'
}
}
stage('Deploy') {
steps {
echo 'Deploying...'
}
}
}
}
Example (Scripted):
node {
stage('Build') {
echo 'Building...'
}
stage('Test') {
echo 'Testing...'
}
 stage('Deploy') {
echo 'Deploying...'
}
}

22. How do you use the Jenkins "credentials" binding in a pipeline?

Answer: Credentials binding allows you to securely use credentials in your Jenkins
pipeline without exposing them in your scripts.

Steps to use credentials:

1. Add credentials in Jenkins via "Manage Jenkins" -> "Manage Credentials."

2. Use the credentials directive in your pipeline to access these credentials.

Example:
pipeline {
agent any
environment {
GITHUB_CREDS = credentials('github-credentials-id')
}
stages {
stage('Checkout') {
steps {
git url: 'https://github.com/example/repo.git',
credentialsId: 'github-credentials-id'
}
}
}
}

23. How do you configure Jenkins to use a specific Java version for a job?

Answer: You can configure Jenkins to use a specific Java version by:

1. Installing the "Tool Environment" plugin.

2. Configuring the desired JDK in "Manage Jenkins" -> "Global Tool Configuration."
3. Selecting the JDK in your job configuration.

Example:
pipeline {
agent any
tools {
jdk 'JDK11'
}
stages {
stage('Build') {
steps {
sh 'java -version'
}
}
 }
}

24. What is Jenkins Shared Library and how do you use it?

Answer: Jenkins Shared Library allows you to create reusable pipeline code that can
be shared across multiple Jenkins jobs.

Steps to use a shared library:

1. Create a repository for your shared library.

2. Define the library structure (e.g., vars, src).
3. Configure the shared library in "Manage Jenkins" -> "Configure System."
4. Use the shared library in your pipeline.

Example:
@Library('my-shared-library') _
pipeline {
agent any
stages {
stage('Build') {
steps {
mySharedLibraryFunction()
}
}
}
}

25. How do you configure a Jenkins job to run periodically?

Answer: You can configure a Jenkins job to run periodically using the "Build
Triggers" section and specifying a cron schedule.

Steps:

1. Go to the job configuration page.

2. Under "Build Triggers," select "Build periodically."
3. Enter the cron expression.

Example:
H 2 * * 1-5
This schedule runs the job at 2 AM from Monday to Friday.

26. What are Jenkins agents and how do you configure them?

Answer: Jenkins agents (formerly known as slaves) are machines that execute build
jobs. They help distribute the workload of build jobs.
Steps to configure an agent:

1. Go to "Manage Jenkins" -> "Manage Nodes and Clouds."

2. Click on "New Node" and enter the required details (e.g., agent name, remote root
directory, launch method).
3. Save and launch the agent.

Example:
pipeline {
agent { label 'my-agent-label' }
stages {
stage('Build') {
steps {
echo 'Building on agent...'
}
}
}
}
27. Explain the use of the when directive in Jenkins pipeline.
Answer: The when directive allows you to specify conditions under which a stage
should be executed. It helps in controlling the flow of the pipeline based on certain
conditions.
Example:
pipeline {
agent any
stages {
stage('Build') {
when {
branch 'main'
}
steps {
echo 'Building on the main branch...'
}
}
stage('Test') {
when {
expression { return env.BRANCH_NAME == 'feature' }
}
steps {
echo 'Testing on a feature branch...'
}
}
}
}

28. How do you perform a rollback in Jenkins?

Answer: Performing a rollback in Jenkins involves redeploying a previous successful

build. This can be done manually or automated using a pipeline.

Example:
pipeline {
agent any
stages {
stage('Deploy') {
steps {
script {
def buildNumber = env.BUILD_NUMBER.toInteger() - 1
echo "Rolling back to build #${buildNumber}"
// Redeploy previous build artifacts
}
}
}
}
}

29. How do you use Docker in Jenkins pipeline?

Answer: You can use Docker in Jenkins pipeline to run build steps inside Docker
containers, providing a consistent and isolated build environment.

Example:
pipeline {
agent {
docker {
image 'maven:3-alpine'
args '-v /root/.m2:/root/.m2'
}
}
stages {
stage('Build') {
steps {
sh 'mvn clean install'
}
}
}
}

30. Explain how you can use Jenkins to monitor external jobs.

Answer: Jenkins can monitor external jobs using the "External Job" plugin or by
configuring jobs to poll external systems for job status.

Example using the "External Monitor Job" plugin:

1. Install the plugin from "Manage Jenkins" -> "Manage Plugins."

2. Create a new job and select "External Monitor Job."
3. Configure the job to monitor an external job by specifying the external job's URL or
endpoint.

Example:
pipeline {
agent any
 stages {
stage('Monitor External Job') {
steps {
script {
def externalJobStatus = sh(script: 'curl -s
http://external-job/status', returnStdout: true).trim()
if (externalJobStatus != 'SUCCESS') {
error "External job failed with status:
${externalJobStatus}"
}
}
}
}
}
}

31. How do you handle parallel testing in Jenkins?

Answer: Parallel testing can be achieved using the parallel directive in a Jenkins
pipeline, which allows running multiple test stages simultaneously.
Example:
pipeline {
agent any
stages {
stage('Parallel Tests') {
parallel {
stage('Unit Tests') {
steps {
sh 'mvn test -Punit'
}
}
stage('Integration Tests') {
steps {
sh 'mvn test -Pintegration'
}
}
}
}
}
}
32. What is the role of post in a declarative Jenkins pipeline?
Answer: The post section in a declarative Jenkins pipeline is used to define actions
that should be taken at the end of the pipeline or a specific stage, regardless of the
build result (success, failure, etc.).
Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
sh 'mvn clean install'
}
}
}
post {
 always {
echo 'This always runs.'
}
success {
echo 'This runs on success.'
}
failure {
echo 'This runs on failure.'
}
}
}

33. How do you archive artifacts in Jenkins?

Answer: Artifacts can be archived in Jenkins using the archiveArtifacts step in a

pipeline or configuring it in the post-build actions of a freestyle job.
Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
sh 'mvn clean package'
}
}
}
post {
always {
archiveArtifacts artifacts: '**/target/*.jar', fingerprint:
true
}
}
}

34. What are Jenkins build triggers and how do you use them?

Answer: Build triggers are mechanisms to start a Jenkins job based on certain events
or conditions, such as SCM changes, scheduled times, or after another job completes.

Examples of build triggers:

• SCM Polling: Jenkins checks the SCM for changes at specified intervals.
• Scheduled Builds: Jobs are triggered at specified times using cron syntax.
• Upstream/Downstream Projects: Jobs can trigger other jobs.

Example (SCM Polling):

H/5 * * * *
This schedule polls the SCM for changes every 5 minutes.

35. Explain how you can manage Jenkins plugins.

Answer: Jenkins plugins can be managed via the Jenkins dashboard under "Manage
Jenkins" -> "Manage Plugins." Here, you can install, update, and remove plugins.

Steps to install a plugin:

1. Go to "Manage Jenkins" -> "Manage Plugins."

2. Click on the "Available" tab.
3. Search for the desired plugin.
4. Select the plugin and click "Install without restart" or "Install and restart."

Example: To install the "Blue Ocean" plugin:

1. Search for "Blue Ocean."

2. Select the checkbox next to "Blue Ocean."
3. Click "Install without restart."

36. How do you handle errors in Jenkins pipelines?

Answer: Errors in Jenkins pipelines can be handled using the try-catch block in a
scripted pipeline or the post section in a declarative pipeline.
Example (Declarative):
pipeline {
agent any
stages {
stage('Build') {
steps {
sh 'mvn clean install'
}
}
}
post {
failure {
echo 'Build failed!'
}
}
}
Example (Scripted):
node {
try {
stage('Build') {
sh 'mvn clean install'
}
} catch (Exception e) {
echo 'Build failed!'
currentBuild.result = 'FAILURE'
}
}

37. What are Jenkins pipelines and how do you create them?
Answer: Jenkins pipelines are a suite of plugins that support implementing and
integrating continuous delivery pipelines into Jenkins. They define the entire lifecycle
of your project, including build, test, and deploy stages.

Example: To create a pipeline:

1. Go to the Jenkins dashboard.

2. Click on "New Item" and select "Pipeline."
3. Define your pipeline script in the Pipeline section.

Example (Declarative Pipeline):

pipeline {
agent any
stages {
stage('Build') {
steps {
echo 'Building...'
}
}
stage('Test') {
steps {
echo 'Testing...'
}
}
stage('Deploy') {
steps {
echo 'Deploying...'
}
}
}
}

38. How do you configure Jenkins to use multiple SCMs?

Answer: Jenkins supports multiple SCMs through the "Multiple SCMs" plugin or by
configuring multiple SCM steps in a pipeline.

Example (Multiple SCMs Plugin):

1. Install the "Multiple SCMs" plugin.

2. In the job configuration, select "Multiple SCMs."
3. Add the SCM repositories you want to use.

Example (Pipeline):
pipeline {
agent any
stages {
stage('Checkout') {
steps {
script {
 git url: 'https://github.com/example/repo1.git',
branch: 'main'
git url: 'https://github.com/example/repo2.git',
branch: 'develop'
}
}
}
}
}
39. Explain how you can use the stash and unstash steps in Jenkins pipeline.
Answer: The stash and unstash steps allow you to save files and directories for later
use in the pipeline, across different stages or nodes.
Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
sh 'mvn clean package'
stash includes: 'target/*.jar', name: 'build-artifacts'
}
}
stage('Test') {
steps {
unstash 'build-artifacts'
sh 'mvn test'
}
}
}
}

40. How do you handle secrets in Jenkins?

Answer: Secrets in Jenkins can be handled using the Jenkins Credentials Plugin,
which allows you to securely store and access secrets.

Steps:

1. Add secrets in Jenkins via "Manage Jenkins" -> "Manage Credentials."

2. Use the credentials directive in your pipeline to access these secrets.

Example:
pipeline {
agent any
environment {
SECRET = credentials('secret-id')
}
stages {
stage('Build') {
steps {
echo "Using secret: ${env.SECRET}"
}
}
}
}
41. How do you use the input step in Jenkins pipeline?
Answer: The input step pauses the pipeline and waits for human input before
proceeding. It is useful for approval processes or manual interventions.
Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
sh 'mvn clean install'
}
}
stage('Deploy') {
steps {
script {
input message: 'Deploy to production?', ok: 'Deploy'
sh 'deploy.sh'
}
}
}
}
}

42. How do you use the Jenkins Job DSL plugin?

Answer: The Jenkins Job DSL plugin allows you to define jobs as code using a
Groovy-based DSL. This makes it easier to create and manage multiple Jenkins jobs.

Steps:

1. Install the "Job DSL" plugin.

2. Create a new "Freestyle project" or "Pipeline" job.
3. In the job configuration, add a "Process Job DSLs" build step.
4. Write the DSL script to define your jobs.

Example:
job('example-job') {
scm {
git('https://github.com/example/repo.git')
}
triggers {
scm('H/5 * * * *')
}
steps {
maven('clean install')
}
}
43. How do you use the parallel step in a scripted Jenkins pipeline?
Answer: The parallel step in a scripted Jenkins pipeline allows multiple branches of
the pipeline to execute simultaneously.
Example:
node {
stage('Parallel Execution') {
parallel(
"Branch A": {
stage('Build A') {
echo 'Building A...'
}
},
"Branch B": {
stage('Build B') {
echo 'Building B...'
}
}
)
}
}

44. How do you handle timeouts in Jenkins pipelines?

Answer: Timeouts in Jenkins pipelines can be handled using the timeout directive,
which allows you to specify a maximum time for a stage or entire pipeline to run.
Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
timeout(time: 10, unit: 'MINUTES') {
sh 'mvn clean install'
}
}
}
}
}

45. Explain how to use the Jenkins "Global Tool Configuration."

Answer: The "Global Tool Configuration" in Jenkins allows you to define tools (e.g.,
JDK, Maven, Git) globally for all jobs to use, ensuring consistency across builds.

Steps:

1. Go to "Manage Jenkins" -> "Global Tool Configuration."

2. Configure the desired tools (e.g., JDK installations, Maven installations).
3. Reference these tools in your jobs or pipelines.

Example:
pipeline {
agent any
tools {
 maven 'Maven 3.6.3'
}
stages {
stage('Build') {
steps {
sh 'mvn clean install'
}
}
}
}
46. How do you use the lock step in Jenkins pipeline?
Answer: The lock step allows you to create a critical section in your pipeline,
ensuring that certain stages do not run concurrently with others, useful for managing
shared resources.
Example:
pipeline {
agent any
stages {
stage('Critical Section') {
steps {
lock(resource: 'shared-resource') {
sh 'critical-task.sh'
}
}
}
}
}

47. How do you use the Jenkins "Pipeline Syntax" tool?

Answer: The "Pipeline Syntax" tool helps you generate pipeline code snippets for
various steps, making it easier to write pipelines.

Steps:

1. Go to Jenkins dashboard.
2. Click on "Pipeline Syntax."
3. Select the desired step from the dropdown menu.
4. Fill in the required fields and generate the pipeline code.

Example: Generated code for a Git checkout step:

checkout([$class: 'GitSCM', branches: [[name: '*/main']],
userRemoteConfigs: [[url: 'https://github.com/example/repo.git']]])
48. How do you use the sh step in Jenkins pipeline?
Answer: The sh step allows you to execute shell commands in a Jenkins pipeline,
making it possible to run any shell script or command.
Example:
pipeline {
agent any
 stages {
stage('Build') {
steps {
sh 'mvn clean install'
}
}
}
}
49. How do you use the dir step in Jenkins pipeline?
Answer: The dir step allows you to change the current working directory in a
Jenkins pipeline, useful for navigating different directories within the workspace.
Example:
pipeline {
agent any
stages {
stage('

Build') {
steps {
dir('subdirectory') {
sh 'mvn clean install'
}
}
}
}
}

50. Explain how to use the Jenkins "Build With Parameters" feature.

Answer: The "Build With Parameters" feature allows you to pass parameters to a
Jenkins job at runtime, enabling more dynamic and customizable builds.

Steps:

1. Go to the job configuration page.

2. Select "This project is parameterized."
3. Add the required parameters (e.g., String, Boolean).
4. Use these parameters in your build steps or pipeline.

Example:
pipeline {
agent any
parameters {
string(name: 'GREETING', defaultValue: 'Hello', description:
'Greeting message')
}
stages {
stage('Greet') {
steps {
echo "${params.GREETING}, World!"
}
}
 }
}

51. How do you integrate Jenkins with Jira?

Answer: Jenkins can be integrated with Jira using the "Jira Plugin," allowing you to
update Jira issues from Jenkins builds.

Steps:

1. Install the "Jira Plugin" from "Manage Jenkins" -> "Manage Plugins."
2. Configure Jira settings in "Manage Jenkins" -> "Configure System."
3. Add a build step or post-build action to update Jira issues.

Example: Updating a Jira issue in a pipeline:

pipeline {
agent any
stages {
stage('Update Jira') {
steps {
jiraIssueSelector(idOrKey: 'JIRA-123')
jiraIssueUpdater fields: [summary: 'Updated from Jenkins']
}
}
}
}

52. How do you manage build artifacts in Jenkins?

Answer: Build artifacts in Jenkins can be managed by archiving them using

the archiveArtifacts step and accessing them via the job's build page.
Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
sh 'mvn clean package'
}
}
}
post {
always {
archiveArtifacts artifacts: '**/target/*.jar', fingerprint:
true
}
}
}

53. Explain how to use the Jenkins "Mail Notification" feature.

Answer: Jenkins can send email notifications using the "Email Extension Plugin,"
allowing you to notify stakeholders of build statuses.

Steps:

1. Install the "Email Extension Plugin" from "Manage Jenkins" -> "Manage Plugins."
2. Configure SMTP settings in "Manage Jenkins" -> "Configure System."
3. Add email notifications in the job configuration or pipeline.

Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
sh 'mvn clean install'
}
}
}
post {
success {
mail to: '[email protected]',
subject: "Build Successful:
${currentBuild.fullDisplayName}",
body: "The build was successful."
}
failure {
mail to: '[email protected]',
subject: "Build Failed: ${currentBuild.fullDisplayName}",
body: "The build failed."
}
}
}
54. How do you use the properties step in Jenkins pipeline?
Answer: The properties step allows you to set job properties in a Jenkins pipeline,
such as parameters, triggers, and environment variables.
Example:
pipeline {
agent any
properties([
parameters([
string(name: 'GREETING', defaultValue: 'Hello', description:
'Greeting message')
]),
pipelineTriggers([
cron('H/5 * * * *')
])
])
stages {
stage('Greet') {
steps {
echo "${params.GREETING}, World!"
}
}
 }
}
55. How do you use the withCredentials step in Jenkins pipeline?
Answer: The withCredentials step allows you to securely use credentials stored in
Jenkins during your pipeline execution.
Example:
pipeline {
agent any
environment {
SECRET = credentials('secret-id')
}
stages {
stage('Build') {
steps {
withCredentials([usernamePassword(credentialsId: 'secret-
id', usernameVariable: 'USERNAME', passwordVariable: 'PASSWORD')]) {
sh 'echo "Using secret: $USERNAME"'
}
}
}
}
}
56. How do you use the checkout step in Jenkins pipeline?
Answer: The checkout step allows you to check out code from various SCMs in your
Jenkins pipeline.
Example:
pipeline {
agent any
stages {
stage('Checkout') {
steps {
checkout([$class: 'GitSCM', branches: [[name: '*/main']],
userRemoteConfigs: [[url: 'https://github.com/example/repo.git']]])
}
}
}
}
57. How do you use the input step in Jenkins pipeline?
Answer: The input step pauses the pipeline and waits for human input before
proceeding. It is useful for approval processes or manual interventions.
Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
sh 'mvn clean install'
}
}
stage('Deploy') {
steps {
script {
input message: 'Deploy to production?', ok: 'Deploy'
 sh 'deploy.sh'
}
}
}
}
}

58. How do you use the Jenkins "Pipeline Syntax" tool?

Answer: The "Pipeline Syntax" tool helps you generate pipeline code snippets for
various steps, making it easier to write pipelines.

Steps:

1. Go to Jenkins dashboard.
2. Click on "Pipeline Syntax."
3. Select the desired step from the dropdown menu.
4. Fill in the required fields and generate the pipeline code.

Example: Generated code for a Git checkout step:

checkout([$class: 'GitSCM', branches: [[name: '*/main']],
userRemoteConfigs: [[url: 'https://github.com/example/repo.git']]])
59. How do you use the sh step in Jenkins pipeline?
Answer: The sh step allows you to execute shell commands in a Jenkins pipeline,
making it possible to run any shell script or command.
Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
sh 'mvn clean install'
}
}
}
}
60. How do you use the dir step in Jenkins pipeline?
Answer: The dir step allows you to change the current working directory in a
Jenkins pipeline, useful for navigating different directories within the workspace.
Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
dir('subdirectory') {
sh 'mvn clean install'
}
}
 }
}
}

61. Explain how to use the Jenkins "Build With Parameters" feature.

Answer: The "Build With Parameters" feature allows you to pass parameters to a
Jenkins job at runtime, enabling more dynamic and customizable builds.

Steps:

1. Go to the job configuration page.

2. Select "This project is parameterized."
3. Add the required parameters (e.g., String, Boolean).
4. Use these parameters in your build steps or pipeline.

Example:
pipeline {
agent any
parameters {
string(name: 'GREETING', defaultValue: 'Hello', description:
'Greeting message')
}
stages {
stage('Greet') {
steps {
echo "${params.GREETING}, World!"
}
}
}
}

62. How do you integrate Jenkins with Jira?

Answer: Jenkins can be integrated with Jira using the "Jira Plugin," allowing you to
update Jira issues from Jenkins builds.

Steps:

1. Install the "Jira Plugin" from "Manage Jenkins" -> "Manage Plugins."
2. Configure Jira settings in "Manage Jenkins" -> "Configure System."
3. Add a build step or post-build action to update Jira issues.

Example: Updating a Jira issue in a pipeline:

pipeline {
agent any
stages {
stage('Update Jira') {
steps {
 jiraIssueSelector(idOrKey: 'JIRA-123')
jiraIssueUpdater fields: [summary: 'Updated from Jenkins']
}
}
}
}

63. How do you manage build artifacts in Jenkins?

Answer: Build artifacts in Jenkins can be managed by archiving them using

the archiveArtifacts step and accessing them via the job's build page.
Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
sh 'mvn clean package'
}
}
}
post {
always {
archiveArtifacts artifacts: '**/target/*.jar', fingerprint:
true
}
}
}

64. Explain how to use the Jenkins "Mail Notification" feature.

Answer: Jenkins can send email notifications using the "Email Extension Plugin,"
allowing you to notify stakeholders of build statuses.

Steps:

1. Install the "Email Extension Plugin" from "Manage Jenkins" -> "Manage Plugins."
2. Configure SMTP settings

in "Manage Jenkins" -> "Configure System." 3. Add email notifications in the job
configuration or pipeline.

Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
sh 'mvn clean install'
}
}
}
 post {
success {
mail to: '[email protected]',
subject: "Build Successful:
${currentBuild.fullDisplayName}",
body: "The build was successful."
}
failure {
mail to: '[email protected]',
subject: "Build Failed: ${currentBuild.fullDisplayName}",
body: "The build failed."
}
}
}
65. How do you use the properties step in Jenkins pipeline?
Answer: The properties step allows you to set job properties in a Jenkins pipeline,
such as parameters, triggers, and environment variables.
Example:
pipeline {
agent any
properties([
parameters([
string(name: 'GREETING', defaultValue: 'Hello', description:
'Greeting message')
]),
pipelineTriggers([
cron('H/5 * * * *')
])
])
stages {
stage('Greet') {
steps {
echo "${params.GREETING}, World!"
}
}
}
}
66. How do you use the withCredentials step in Jenkins pipeline?
Answer: The withCredentials step allows you to securely use credentials stored in
Jenkins during your pipeline execution.
Example:
pipeline {
agent any
environment {
SECRET = credentials('secret-id')
}
stages {
stage('Build') {
steps {
withCredentials([usernamePassword(credentialsId: 'secret-
id', usernameVariable: 'USERNAME', passwordVariable: 'PASSWORD')]) {
sh 'echo "Using secret: $USERNAME"'
}
}
}
}
}
67. How do you use the checkout step in Jenkins pipeline?
Answer: The checkout step allows you to check out code from various SCMs in your
Jenkins pipeline.
Example:
pipeline {
agent any
stages {
stage('Checkout') {
steps {
checkout([$class: 'GitSCM', branches: [[name: '*/main']],
userRemoteConfigs: [[url: 'https://github.com/example/repo.git']]])
}
}
}
}
68. How do you use the input step in Jenkins pipeline?
Answer: The input step pauses the pipeline and waits for human input before
proceeding. It is useful for approval processes or manual interventions.
Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
sh 'mvn clean install'
}
}
stage('Deploy') {
steps {
script {
input message: 'Deploy to production?', ok: 'Deploy'
sh 'deploy.sh'
}
}
}
}
}

69. How do you use the Jenkins "Pipeline Syntax" tool?

Answer: The "Pipeline Syntax" tool helps you generate pipeline code snippets for
various steps, making it easier to write pipelines.

Steps:

1. Go to Jenkins dashboard.
2. Click on "Pipeline Syntax."
3. Select the desired step from the dropdown menu.
4. Fill in the required fields and generate the pipeline code.
Example: Generated code for a Git checkout step:
checkout([$class: 'GitSCM', branches: [[name: '*/main']],
userRemoteConfigs: [[url: 'https://github.com/example/repo.git']]])
70. How do you use the sh step in Jenkins pipeline?
Answer: The sh step allows you to execute shell commands in a Jenkins pipeline,
making it possible to run any shell script or command.
Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
sh 'mvn clean install'
}
}
}
}
71. How do you use the dir step in Jenkins pipeline?
Answer: The dir step allows you to change the current working directory in a
Jenkins pipeline, useful for navigating different directories within the workspace.
Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
dir('subdirectory') {
sh 'mvn clean install'
}
}
}
}
}

72. Explain how to use the Jenkins "Build With Parameters" feature.

Answer: The "Build With Parameters" feature allows you to pass parameters to a
Jenkins job at runtime, enabling more dynamic and customizable builds.

Steps:

1. Go to the job configuration page.

2. Select "This project is parameterized."
3. Add the required parameters (e.g., String, Boolean).
4. Use these parameters in your build steps or pipeline.

Example:
pipeline {
 agent any
parameters {
string(name: 'GREETING', defaultValue: 'Hello', description:
'Greeting message')
}
stages {
stage('Greet') {
steps {
echo "${params.GREETING}, World!"
}
}
}
}

73. How do you integrate Jenkins with Jira?

Answer: Jenkins can be integrated with Jira using the "Jira Plugin," allowing you to
update Jira issues from Jenkins builds.

Steps:

1. Install the "Jira Plugin" from "Manage Jenkins" -> "Manage Plugins."
2. Configure Jira settings in "Manage Jenkins" -> "Configure System."
3. Add a build step or post-build action to update Jira issues.

Example: Updating a Jira issue in a pipeline:

pipeline {
agent any
stages {
stage('Update Jira') {
steps {
jiraIssueSelector(idOrKey: 'JIRA-123')
jiraIssueUpdater fields: [summary: 'Updated from Jenkins']
}
}
}
}

74. How do you manage build artifacts in Jenkins?

Answer: Build artifacts in Jenkins can be managed by archiving them using

the archiveArtifacts step and accessing them via the job's build page.
Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
sh 'mvn clean package'
}
}
}
 post {
always {
archiveArtifacts artifacts: '**/target/*.jar', fingerprint:
true
}
}
}

75. Explain how to use the Jenkins "Mail Notification" feature.

Answer: Jenkins can send email notifications using the "Email Extension Plugin,"
allowing you to notify stakeholders of build statuses.

Steps:

1. Install the "Email Extension Plugin" from "Manage Jenkins" -> "Manage Plugins."
2. Configure SMTP settings in "Manage Jenkins" -> "Configure System."
3. Add email notifications in the job configuration or pipeline.

Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
sh 'mvn clean install'
}
}
}
post {
success {
mail to: '[email protected]',
subject: "Build Successful:
${currentBuild.fullDisplayName}",
body: "The build was successful."
}
failure {
mail to: '[email protected]',
subject: "Build Failed: ${currentBuild.fullDisplayName}",
body: "The build failed."
}
}
}
76. How do you use the properties step in Jenkins pipeline?
Answer: The properties step allows you to set job properties in a Jenkins pipeline,
such as parameters, triggers, and environment variables.
Example:
pipeline {
agent any
properties([
parameters([
string(name: 'GREETING', defaultValue: 'Hello', description:
'Greeting message')
 ]),
pipelineTriggers([
cron('H/5 * * * *')
])
])
stages {
stage('Greet') {
steps {
echo "${params.GREETING}, World!"
}
}
}
}
77. How do you use the withCredentials step in Jenkins pipeline?
Answer: The withCredentials step allows you to securely use credentials stored in
Jenkins during your pipeline execution.
Example:
pipeline {
agent any
environment {
SECRET = credentials('secret-id')
}
stages {
stage('Build') {
steps {
withCredentials([usernamePassword(credentialsId: 'secret-
id', usernameVariable: 'USERNAME', passwordVariable: 'PASSWORD')]) {
sh 'echo "Using secret: $USERNAME"'
}
}
}
}
}
78. How do you use the checkout step in Jenkins pipeline?
Answer: The checkout step allows you to check out code from various SCMs in your
Jenkins pipeline.
Example:
pipeline {
agent any
stages {
stage('Checkout') {
steps {
checkout([$class: 'GitSCM', branches: [[name: '*/main']],
userRemoteConfigs: [[url: 'https://github.com/example/repo.git']]])
}
}
}
}
79. How do you use the input step in Jenkins pipeline?
**Answer:

** The input step pauses the pipeline and waits for human input before proceeding.
It is useful for approval processes or manual interventions.
Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
sh 'mvn clean install'
}
}
stage('Deploy') {
steps {
script {
input message: 'Deploy to production?', ok: 'Deploy'
sh 'deploy.sh'
}
}
}
}
}

80. How do you use the Jenkins "Pipeline Syntax" tool?

Answer: The "Pipeline Syntax" tool helps you generate pipeline code snippets for
various steps, making it easier to write pipelines.

Steps:

1. Go to Jenkins dashboard.
2. Click on "Pipeline Syntax."
3. Select the desired step from the dropdown menu.
4. Fill in the required fields and generate the pipeline code.

Example: Generated code for a Git checkout step:

checkout([$class: 'GitSCM', branches: [[name: '*/main']],
userRemoteConfigs: [[url: 'https://github.com/example/repo.git']]])
81. How do you use the sh step in Jenkins pipeline?
Answer: The sh step allows you to execute shell commands in a Jenkins pipeline,
making it possible to run any shell script or command.
Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
sh 'mvn clean install'
}
}
}
}
82. How do you use the dir step in Jenkins pipeline?
Answer: The dir step allows you to change the current working directory in a
Jenkins pipeline, useful for navigating different directories within the workspace.
Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
dir('subdirectory') {
sh 'mvn clean install'
}
}
}
}
}

83. Explain how to use the Jenkins "Build With Parameters" feature.

Answer: The "Build With Parameters" feature allows you to pass parameters to a
Jenkins job at runtime, enabling more dynamic and customizable builds.

Steps:

1. Go to the job configuration page.

2. Select "This project is parameterized."
3. Add the required parameters (e.g., String, Boolean).
4. Use these parameters in your build steps or pipeline.

Example:
pipeline {
agent any
parameters {
string(name: 'GREETING', defaultValue: 'Hello', description:
'Greeting message')
}
stages {
stage('Greet') {
steps {
echo "${params.GREETING}, World!"
}
}
}
}

84. How do you integrate Jenkins with Jira?

Answer: Jenkins can be integrated with Jira using the "Jira Plugin," allowing you to
update Jira issues from Jenkins builds.

Steps:

1. Install the "Jira Plugin" from "Manage Jenkins" -> "Manage Plugins."
 2. Configure Jira settings in "Manage Jenkins" -> "Configure System."
3. Add a build step or post-build action to update Jira issues.

Example: Updating a Jira issue in a pipeline:

pipeline {
agent any
stages {
stage('Update Jira') {
steps {
jiraIssueSelector(idOrKey: 'JIRA-123')
jiraIssueUpdater fields: [summary: 'Updated from Jenkins']
}
}
}
}

85. How do you manage build artifacts in Jenkins?

Answer: Build artifacts in Jenkins can be managed by archiving them using

the archiveArtifacts step and accessing them via the job's build page.
Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
sh 'mvn clean package'
}
}
}
post {
always {
archiveArtifacts artifacts: '**/target/*.jar', fingerprint:
true
}
}
}

86. Explain how to use the Jenkins "Mail Notification" feature.

Answer: Jenkins can send email notifications using the "Email Extension Plugin,"
allowing you to notify stakeholders of build statuses.

Steps:

1. Install the "Email Extension Plugin" from "Manage Jenkins" -> "Manage Plugins."
2. Configure SMTP settings in "Manage Jenkins" -> "Configure System."
3. Add email notifications in the job configuration or pipeline.

Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
sh 'mvn clean install'
}
}
}
post {
success {
mail to: '[email protected]',
subject: "Build Successful:
${currentBuild.fullDisplayName}",
body: "The build was successful."
}
failure {
mail to: '[email protected]',
subject: "Build Failed: ${currentBuild.fullDisplayName}",
body: "The build failed."
}
}
}
87. How do you use the properties step in Jenkins pipeline?
Answer: The properties step allows you to set job properties in a Jenkins pipeline,
such as parameters, triggers, and environment variables.
Example:
pipeline {
agent any
properties([
parameters([
string(name: 'GREETING', defaultValue: 'Hello', description:
'Greeting message')
]),
pipelineTriggers([
cron('H/5 * * * *')
])
])
stages {
stage('Greet') {
steps {
echo "${params.GREETING}, World!"
}
}
}
}
88. How do you use the withCredentials step in Jenkins pipeline?
Answer: The withCredentials step allows you to securely use credentials stored in
Jenkins during your pipeline execution.
Example:
pipeline {
agent any
environment {
SECRET = credentials('secret-id')
}
stages {
 stage('Build') {
steps {
withCredentials([usernamePassword(credentialsId: 'secret-
id', usernameVariable: 'USERNAME', passwordVariable: 'PASSWORD')]) {
sh 'echo "Using secret: $USERNAME"'
}
}
}
}
}
89. How do you use the checkout step in Jenkins pipeline?
Answer: The checkout step allows you to check out code from various SCMs in your
Jenkins pipeline.
Example:
pipeline {
agent any
stages {
stage('Checkout') {
steps {
checkout([$class: 'GitSCM', branches: [[name: '*/main']],
userRemoteConfigs: [[url: 'https://github.com/example/repo.git']]])
}
}
}
}
90. How do you use the input step in Jenkins pipeline?
Answer: The input step pauses the pipeline and waits for human input before
proceeding. It is useful for approval processes or manual interventions.
Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
sh 'mvn clean install'
}
}
stage('Deploy') {
steps {
script {
input message: 'Deploy to production?', ok: 'Deploy'
sh 'deploy.sh'
}
}
}
}
}

91. How do you use the Jenkins "Pipeline Syntax" tool?

Answer: The "Pipeline Syntax" tool helps you generate pipeline code snippets for
various steps, making it easier to write pipelines.
Steps:

1. Go to Jenkins dashboard.
2. Click on "Pipeline Syntax."
3. Select the desired step from the dropdown menu.
4. Fill in the required fields and generate the pipeline code.

Example: Generated code for a Git checkout step:

checkout([$class: 'GitSCM', branches: [[name: '*/main']],
userRemoteConfigs: [[url: 'https://github.com/example/repo.git']]])
92. How do you use the sh step in Jenkins pipeline?
Answer: The sh step allows you to execute shell commands in a Jenkins pipeline,
making it possible to run any shell script or command.
Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
sh 'mvn clean install'
}
}
}
}
93. How do you use the dir step in Jenkins pipeline?
Answer: The dir step allows you to change the current working directory in a
Jenkins pipeline, useful for navigating different directories within the workspace.
Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
dir('subdirectory') {
sh 'mvn clean install'
}
}
}
}
}

94. Explain how to use the Jenkins "Build With Parameters" feature.

Answer: The "Build With Parameters" feature allows you to pass parameters to a
Jenkins job at runtime, enabling more dynamic and customizable builds.

Steps:

1. Go to the job configuration page.

 2. Select "This project is parameterized."
3. Add the required parameters (e.g., String, Boolean).
4. Use these parameters in your build steps or pipeline.

Example:
pipeline {
agent

any
parameters {
string(name: 'GREETING', defaultValue: 'Hello', description:
'Greeting message')
}
stages {
stage('Greet') {
steps {
echo "${params.GREETING}, World!"
}
}
}
}

95. How do you integrate Jenkins with Jira?

Answer: Jenkins can be integrated with Jira using the "Jira Plugin," allowing you to
update Jira issues from Jenkins builds.

Steps:

1. Install the "Jira Plugin" from "Manage Jenkins" -> "Manage Plugins."
2. Configure Jira settings in "Manage Jenkins" -> "Configure System."
3. Add a build step or post-build action to update Jira issues.

Example: Updating a Jira issue in a pipeline:

pipeline {
agent any
stages {
stage('Update Jira') {
steps {
jiraIssueSelector(idOrKey: 'JIRA-123')
jiraIssueUpdater fields: [summary: 'Updated from Jenkins']
}
}
}
}

96. How do you manage build artifacts in Jenkins?

Answer: Build artifacts in Jenkins can be managed by archiving them using

the archiveArtifacts step and accessing them via the job's build page.
Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
sh 'mvn clean package'
}
}
}
post {
always {
archiveArtifacts artifacts: '**/target/*.jar', fingerprint:
true
}
}
}

97. Explain how to use the Jenkins "Mail Notification" feature.

Answer: Jenkins can send email notifications using the "Email Extension Plugin,"
allowing you to notify stakeholders of build statuses.

Steps:

1. Install the "Email Extension Plugin" from "Manage Jenkins" -> "Manage Plugins."
2. Configure SMTP settings in "Manage Jenkins" -> "Configure System."
3. Add email notifications in the job configuration or pipeline.

Example:
pipeline {
agent any
stages {
stage('Build') {
steps {
sh 'mvn clean install'
}
}
}
post {
success {
mail to: '[email protected]',
subject: "Build Successful:
${currentBuild.fullDisplayName}",
body: "The build was successful."
}
failure {
mail to: '[email protected]',
subject: "Build Failed: ${currentBuild.fullDisplayName}",
body: "The build failed."
}
}
}
98. How do you use the properties step in Jenkins pipeline?
Answer: The properties step allows you to set job properties in a Jenkins pipeline,
such as parameters, triggers, and environment variables.
Example:
pipeline {
agent any
properties([
parameters([
string(name: 'GREETING', defaultValue: 'Hello', description:
'Greeting message')
]),
pipelineTriggers([
cron('H/5 * * * *')
])
])
stages {
stage('Greet') {
steps {
echo "${params.GREETING}, World!"
}
}
}
}
99. How do you use the withCredentials step in Jenkins pipeline?
Answer: The withCredentials step allows you to securely use credentials stored in
Jenkins during your pipeline execution.
Example:
pipeline {
agent any
environment {
SECRET = credentials('secret-id')
}
stages {
stage('Build') {
steps {
withCredentials([usernamePassword(credentialsId: 'secret-
id', usernameVariable: 'USERNAME', passwordVariable: 'PASSWORD')]) {
sh 'echo "Using secret: $USERNAME"'
}
}
}
}
}
100. How do you use the checkout step in Jenkins pipeline?
Answer: The checkout step allows you to check out code from various SCMs in your
Jenkins pipeline.
Example:
pipeline {
agent any
stages {
stage('Checkout') {
steps {
checkout([$class: 'GitSCM', branches: [[name: '*/main']],
userRemoteConfigs: [[url: 'https://github.com/example/repo.git']]])
 }
}
}
}