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.