Running Jenkins from a WAR file and configuring its environment

Introduction

The author thanks readers for their interest and explains that many have asked how to run Jenkins as a WAR file and configure the necessary environment.

Running Jenkins from the WAR

1. Download the Jenkins WAR package.

2. Start Jenkins with the command nohup java -jar jenkins.war &. After this step Jenkins runs the same way as previous installation methods.

Error handling

Error 1

Network problems may prevent plugin installation; simply retry the operation.

Error 2

"HTTP ERROR 403 No valid crumb was included in the request" occurs due to proxy settings. The fix is to navigate to System Management → Global Security Configuration → CSRF Protection and enable Proxy Compatibility .

AWT configuration issues can be addressed by running the container with the JVM option -Djava.awt.headless=true (see the Jenkins redirect link for details).

Installing required Linux packages

Install the following fonts and X server packages, then restart the Jenkins service:

yum install dejavu-sans-fonts
yum install fontconfig
yum install xorg-x11-server-Xvfb

Configuring global tools

Maven configuration

Select "Settings file from the file system" and provide the full path to the settings.xml located in the Maven conf directory on the server.

JDK configuration

Click "Add JDK", uncheck "Install automatically", then set the JDK name (e.g., JDK17) and the JAVA_HOME path, such as /tools/jdk/jdk-17.0.4.

Git configuration

Enter the Git name (e.g., "git") and the installation directory (e.g., /usr/bin/git) to complete the Git tool setup.

Maven tool configuration

Add a new Maven tool, uncheck automatic installation, set the name (e.g., "apache-maven-3.8.4"), and provide the Maven home path, such as /tools/apache-maven-3.8.4.

After completing these steps, the Jenkins WAR instance is up and running with all required environment settings.