Jenkins WAR file execution - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Jenkins WAR file startup command output

You run the command java -jar jenkins.war on a Linux server. What is the expected output you will see in the console upon successful startup?

A Started Jenkins in 5 seconds (JVM running for 6)

B Error: Could not find or load main class jenkins.war

C

Running from: /home/user
INFO: Jenkins is fully up and running

D Usage: java [-options] class [args...]

💡 Hint

Look for the message that confirms Jenkins started successfully.

When you run 'java -jar jenkins.war', Jenkins starts and prints a message like 'Started Jenkins in X seconds'. This confirms the server is running.

🧠 Conceptual

intermediate

Default Jenkins port when running WAR file

When you run Jenkins using the WAR file without specifying any port, which port does Jenkins listen on by default?

A 9090

B 80

C 443

D 8080

💡 Hint

Think about common web server ports and Jenkins default settings.

Jenkins by default listens on port 8080 when started from the WAR file without any port option.

❓ Configuration

advanced

Running Jenkins WAR on a custom port

You want to run Jenkins WAR file on port 9090 instead of the default 8080. Which command will correctly start Jenkins on port 9090?

A java -jar jenkins.war --httpPort=9090

B java -jar jenkins.war --port 9090

C java -jar jenkins.war -p 9090

D java -jar jenkins.war --setPort=9090

💡 Hint

Check the official Jenkins WAR file command line options for setting HTTP port.

The correct syntax to specify a custom HTTP port is '--httpPort=PORT'. Other options are invalid or unrecognized.

❓ Troubleshoot

advanced

Jenkins WAR file fails to start with port in use error

You run java -jar jenkins.war but get an error saying the port 8080 is already in use. What is the best immediate action to fix this?

A Reinstall Java on the server

B Kill the process using port 8080 or run Jenkins on a different port

C Delete the jenkins.war file and download it again

D Restart the server without changing anything

💡 Hint

Think about what causes port conflicts and how to resolve them quickly.

Port 8080 is already used by another process. You can either stop that process or run Jenkins on a different port to avoid conflict.

✅ Best Practice

expert

Securing Jenkins WAR file execution

Which practice is the best to secure Jenkins when running it directly from the WAR file on a production server?

A Disable Jenkins security to simplify access

B Run Jenkins as root user for full access

C Run Jenkins behind a reverse proxy with HTTPS and authentication

D Open Jenkins port 8080 to the internet without firewall

💡 Hint

Think about common security practices for web applications.

Running Jenkins behind a reverse proxy with HTTPS and authentication protects it from unauthorized access and secures data in transit.

Practice

1. What does running java -jar jenkins.war do in Jenkins?

easy

A. Deletes Jenkins configuration files

B. Installs Jenkins permanently on the system

C. Updates Jenkins to the latest version

D. Starts Jenkins server without installing it

Solution

1. Step 1: Understand the command purpose

   The command java -jar jenkins.war runs the Jenkins server directly from the WAR file without installation.

2. Step 2: Differentiate from installation

   This method does not install Jenkins permanently but starts it temporarily for use or testing.

3. Final Answer:

   Starts Jenkins server without installing it -> Option D

4. Quick Check:

   Run WAR file = Start Jenkins temporarily [OK]

Hint: WAR file runs Jenkins without install, just start it [OK]

Common Mistakes:

• Thinking it installs Jenkins permanently
• Confusing it with Jenkins update command
• Assuming it deletes files

2. Which command correctly starts Jenkins on port 9090 using the WAR file?

easy

A. java -jar jenkins.war --httpPort=9090

B. java -jar jenkins.war -p 9090

C. java -jar jenkins.war --port 9090

D. java -jar jenkins.war -httpPort 9090

Solution

1. Step 1: Recall Jenkins WAR port option syntax

   The correct option to specify port is --httpPort=9090 when running the WAR file.

2. Step 2: Check other options for correctness

   Options B, C, and D use incorrect flags or syntax not recognized by Jenkins WAR execution.

3. Final Answer:

   java -jar jenkins.war --httpPort=9090 -> Option A

4. Quick Check:

   Use --httpPort=number to set port [OK]

Hint: Use --httpPort=PORT to set Jenkins port [OK]

Common Mistakes:

• Using -p or --port which Jenkins WAR does not recognize
• Missing equal sign in option
• Using single dash for long option

3. What will be the output if you run java -jar jenkins.war --httpPort=8080 when port 8080 is already in use?

medium

A. Error: Address already in use, Jenkins fails to start

B. Jenkins automatically switches to port 8081

C. Jenkins starts successfully on port 8080

D. Jenkins ignores the port option and uses default

Solution

1. Step 1: Understand port conflict behavior

   If the specified port (8080) is busy, Jenkins cannot bind to it and will fail to start with an error.

2. Step 2: Check Jenkins automatic port fallback

   Jenkins WAR does not automatically switch ports; it requires manual change if port is busy.

3. Final Answer:

   Error: Address already in use, Jenkins fails to start -> Option A

4. Quick Check:

   Port busy = Jenkins start error [OK]

Hint: Busy port causes Jenkins start error, no auto-switch [OK]

Common Mistakes:

• Assuming Jenkins auto-switches ports
• Thinking Jenkins ignores port option
• Believing Jenkins starts anyway on busy port

4. You ran java -jar jenkins.war --httpPort=abc and Jenkins did not start. What is the likely cause?

medium

A. Jenkins requires root privileges to start

B. Jenkins WAR file is corrupted

C. Invalid port number format causes startup failure

D. Java is not installed on the system

Solution

1. Step 1: Analyze the port option value

   The port option --httpPort=abc uses non-numeric characters, which is invalid for a port number.

2. Step 2: Understand Jenkins port validation

   Jenkins expects a numeric port; invalid format causes startup failure with error.

3. Final Answer:

   Invalid port number format causes startup failure -> Option C

4. Quick Check:

   Port must be numeric for Jenkins to start [OK]

Hint: Port must be a number, not letters [OK]

Common Mistakes:

• Blaming Jenkins WAR file corruption
• Assuming Java is missing without checking
• Thinking root privileges are always needed

5. You want to run Jenkins WAR file on port 7070 and also specify a custom Jenkins home directory at /data/jenkins_home. Which command is correct?

hard

A. java -jar jenkins.war --httpPort=7070 --jenkinsHome=/data/jenkins_home

B. java -Djenkins.home=/data/jenkins_home -jar jenkins.war --httpPort=7070

C. java -jar jenkins.war --httpPort=7070 --jenkins.home=/data/jenkins_home

D. java -jar jenkins.war --httpPort=7070 -DjenkinsHome=/data/jenkins_home

Solution

1. Step 1: Set port option correctly

   The port is set with --httpPort=7070, which is correct syntax.

2. Step 2: Set Jenkins home directory properly

   Jenkins home is set via Java system property -Djenkins.home=path, not as a command option.

3. Step 3: Verify option correctness

   The correct command places the -Djenkins.home= option before -jar to set the system property properly.

4. Final Answer:

   java -Djenkins.home=/data/jenkins_home -jar jenkins.war --httpPort=7070 -> Option B

5. Quick Check:

   Use -Djenkins.home=PATH for custom Jenkins home [OK]

Hint: Use -Djenkins.home=PATH to set Jenkins home [OK]

Common Mistakes:

• Using --jenkinsHome or --jenkins.home as options
• Confusing Java system properties with command options
• Missing -D prefix for system properties
• Placing -D option after -jar which is incorrect