Freestyle job creation in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Jenkins Freestyle Job: Build Trigger Output

You have a Jenkins freestyle job configured to run a shell command:

echo Hello Jenkins

What will be the output in the Jenkins console log after the build runs?

Jenkins

echo Hello Jenkins

A Build failed

B echo Hello Jenkins

C Hello Jenkins

D No output

💡 Hint

The shell command output is shown in the console log.

The shell command 'echo Hello Jenkins' prints 'Hello Jenkins' to the console log of the build.

❓ Configuration

intermediate

Setting Build Triggers in Freestyle Job

Which option correctly configures a Jenkins freestyle job to trigger builds every 15 minutes using the built-in scheduler syntax?

A H/15 * * * *

B */15 * * * *

C 15 * * * *

D 0 15 * * *

💡 Hint

Jenkins uses 'H' to distribute load evenly.

The 'H/15 * * * *' syntax triggers the job every 15 minutes with a hashed start time to avoid all jobs running simultaneously.

❓ Troubleshoot

advanced

Freestyle Job Fails to Archive Artifacts

A Jenkins freestyle job is configured to archive artifacts from the path 'build/output/*.jar'. After a successful build, no artifacts are archived. What is the most likely cause?

A The archive step is placed before the build step

B The build did not produce any .jar files in 'build/output/'

C The workspace was cleaned before archiving

D The Jenkins user lacks permission to read the files

💡 Hint

Check if the files exist in the specified path after build.

If no .jar files exist in 'build/output/', the archive step finds nothing to archive, resulting in no artifacts saved.

🔀 Workflow

advanced

Freestyle Job Post-build Actions Order

In a Jenkins freestyle job, you want to run a shell script after archiving artifacts and then send an email notification. Which order of post-build actions is correct?

A Email notification → Execute shell → Archive artifacts

B Execute shell → Archive artifacts → Email notification

C Email notification → Archive artifacts → Execute shell

D Archive artifacts → Execute shell → Email notification

💡 Hint

Archiving should happen before any post-build scripts that depend on artifacts.

Artifacts must be archived first so they are available for any scripts or notifications that follow.

✅ Best Practice

expert

Securing Credentials in Freestyle Jobs

What is the best practice to securely use credentials in a Jenkins freestyle job without exposing them in the build logs?

A Use Jenkins Credentials Plugin and inject credentials via environment variables

B Hardcode credentials in the shell build step

C Store credentials in a plain text file in the workspace

D Pass credentials as command line arguments in the build step

💡 Hint

Jenkins has a plugin designed for managing secrets safely.

Using the Credentials Plugin and injecting credentials as environment variables keeps secrets out of logs and source code.

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