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.