Freestyle job creation in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new freestyle job named 'MyJob'.

Jenkins

job = Jenkins.createJob('[1]')

Drag options to blanks, or click blank then click option'

ATestJob

BMyJob

CBuildProject

DDeployApp

Attempts:

3 left

💡 Hint

Common Mistakes

Using a different job name than 'MyJob'.

Forgetting to put the job name in quotes.

The job name must be 'MyJob' to match the requirement.

2fill in blank

medium

Complete the code to add a shell build step that echoes 'Hello World'.

Jenkins

job.addBuildStep(new Shell('[1]'))

Drag options to blanks, or click blank then click option'

Aecho Hello World

Becho Hello

Cprint('Hello World')

Decho 'Hello'

Attempts:

3 left

💡 Hint

Common Mistakes

Using incomplete echo commands.

Using print instead of echo in shell.

The shell command must exactly echo 'Hello World' as a single string.

3fill in blank

hard

Fix the error in the code to set the job description to 'Sample Job'.

Jenkins

job.setDescription([1])

Drag options to blanks, or click blank then click option'

A'Sample Job'

BSample Job

C"Sample Job"

DSample_Job

Attempts:

3 left

💡 Hint

Common Mistakes

Not using quotes around the description string.

Using variable names instead of string literals.

The description must be a string literal, so it needs quotes.

4fill in blank

hard

Fill both blanks to configure the job to trigger on SCM changes and set the SCM URL.

Jenkins

job.setTriggers(new SCMTrigger('[1]'))
job.setScm(new GitSCM('[2]'))

Drag options to blanks, or click blank then click option'

AH/5 * * * *

Bhttps://github.com/example/repo.git

CH/10 * * * *

[e-mail]:example/repo.git

Attempts:

3 left

💡 Hint

Common Mistakes

Using SSH URL instead of HTTPS for SCM.

Using wrong cron syntax for trigger.

The trigger uses a cron syntax 'H/5 * * * *' to poll every 5 minutes, and the SCM URL must be the HTTPS GitHub repo URL.

5fill in blank

hard

Fill all three blanks to create a freestyle job with a description, a shell build step, and a post-build email notification.

Jenkins

job = Jenkins.createJob('[1]')
job.setDescription('[2]')
job.addBuildStep(new Shell('[3]'))
job.addPublisher(new EmailNotifier('[e-mail]'))

Drag options to blanks, or click blank then click option'

ADeployApp

BDeployment job for production

Cecho Deployment started

DTestJob

Attempts:

3 left

💡 Hint

Common Mistakes

Using mismatched job names and descriptions.

Forgetting to add the shell build step.

The job name is 'DeployApp', the description explains the job purpose, and the shell step echoes a deployment start message.

Practice

1. What is the main purpose of a freestyle job in Jenkins?

easy

A. To monitor server hardware status

B. To create complex pipelines with multiple stages

C. To manage Jenkins user permissions

D. To run simple automated tasks configured via the Jenkins UI

Solution

1. Step 1: Understand freestyle job basics

   Freestyle jobs are designed for simple automation tasks in Jenkins, easy to set up through the UI.

2. Step 2: Compare options

   Monitoring server hardware, creating complex pipelines, and managing user permissions are other Jenkins features or unrelated tasks, not freestyle jobs.

3. Final Answer:

   To run simple automated tasks configured via the Jenkins UI -> Option D

4. Quick Check:

   Freestyle job = simple automation [OK]

Hint: Freestyle jobs are for simple tasks, not complex pipelines [OK]

Common Mistakes:

• Confusing freestyle jobs with pipeline jobs
• Thinking freestyle jobs manage users or hardware
• Assuming freestyle jobs require scripting

2. Which of the following is the correct way to start creating a freestyle job in Jenkins?

easy

A. Go to 'Manage Jenkins' and select 'Create Freestyle Job'

B. Run the command 'jenkins create freestyle' in the terminal

C. Click 'New Item', enter a name, select 'Freestyle project', then click OK

D. Edit the Jenkinsfile to add a freestyle job

Solution

1. Step 1: Recall Jenkins UI steps

   To create a freestyle job, you click 'New Item', name it, choose 'Freestyle project', and confirm.

2. Step 2: Eliminate incorrect options

   Going to 'Manage Jenkins', running terminal commands, and editing a Jenkinsfile are not how freestyle jobs are created.

3. Final Answer:

   Click 'New Item', enter a name, select 'Freestyle project', then click OK -> Option C

4. Quick Check:

   Create freestyle job = New Item + Freestyle project [OK]

Hint: Start with 'New Item' and pick 'Freestyle project' [OK]

Common Mistakes:

• Looking for freestyle job creation in 'Manage Jenkins'
• Trying to create freestyle jobs via terminal commands
• Editing Jenkinsfile instead of using UI

3. Given a freestyle job configured to run a shell command echo Hello Jenkins, what will be the output in the build console?

medium

A. Hello Jenkins

B. echo Hello Jenkins

C. Error: command not found

D. Build failed

Solution

1. Step 1: Understand shell command execution in freestyle job

   The shell command echo Hello Jenkins prints the text 'Hello Jenkins' to the console.

2. Step 2: Analyze output options

   'Hello Jenkins' matches the expected output. 'echo Hello Jenkins' shows the command itself, which is not the output. Error and build failure do not occur here.

3. Final Answer:

   Hello Jenkins -> Option A

4. Quick Check:

   echo command prints text [OK]

Hint: echo prints text, not the command itself [OK]

Common Mistakes:

• Confusing command output with command text
• Assuming shell commands fail without reason
• Expecting build failure without errors

4. You created a freestyle job but the build fails immediately with 'No such file or directory' error when running a shell command. What is the most likely cause?

medium

A. The freestyle job was not saved properly

B. The shell command references a file that does not exist on the Jenkins agent

C. Jenkins server is offline

D. The job type should be pipeline, not freestyle

Solution

1. Step 1: Understand the error message

   'No such file or directory' means the shell command tries to access a missing file on the Jenkins agent machine.

2. Step 2: Evaluate other options

   The freestyle job was not saved properly is unlikely because saving issues cause different errors. Jenkins server is offline would prevent any build start. The job type should be pipeline, not freestyle is unrelated to file errors.

3. Final Answer:

   The shell command references a file that does not exist on the Jenkins agent -> Option B

4. Quick Check:

   File missing on agent = 'No such file' error [OK]

Hint: Check file paths on Jenkins agent for shell commands [OK]

Common Mistakes:

• Assuming job type causes file errors
• Ignoring agent environment differences
• Thinking Jenkins server offline causes this error

5. You want to create a freestyle job that triggers automatically every day at 2 AM and runs a shell script. Which configuration steps are needed?

hard

A. Set 'Build Triggers' to 'Build periodically' with schedule '0 2 * * *' and add shell command in 'Build' section

B. Add a cron job on the Jenkins server to run the job at 2 AM

C. Configure 'Poll SCM' with schedule '0 2 * * *' and add shell command in 'Post-build Actions'

D. Use 'Build after other projects are built' trigger and add shell command in 'Build' section

Solution

1. Step 1: Identify correct trigger for scheduled builds

   In freestyle jobs, 'Build periodically' with cron syntax schedules automatic runs at specified times.

2. Step 2: Place shell command in the 'Build' section

   The shell script should be added under 'Build' steps, not post-build or external cron.

3. Final Answer:

   Set 'Build Triggers' to 'Build periodically' with schedule '0 2 * * *' and add shell command in 'Build' section -> Option A

4. Quick Check:

   Scheduled build = 'Build periodically' + shell in 'Build' [OK]

Hint: Use 'Build periodically' with cron for scheduled freestyle jobs [OK]

Common Mistakes:

• Using external cron instead of Jenkins triggers
• Putting shell commands in post-build actions
• Confusing 'Poll SCM' with scheduled builds