How to Fix Common Jenkins Compatibility Issues and Optimize Your CI/CD Pipeline

1. Performance Plugin Compatibility

In freestyle projects, the Performance plugin (v3.19) conflicts with Jenkins v2.298, causing UI misalignment and preventing configuration saves. Three work‑arounds are provided:

Convert the freestyle project to a pipeline job.

Manually edit config.xml on the server to enable saving.

Downgrade Jenkins to v2.263.4 LTS (after backing up and checking other plugin compatibilities).

2. Modifying Jenkins CSP (Content Security Policy)

When using the Robot Framework plugin, Jenkins blocks the preview of test reports because the default CSP only allows CSS and images from the Jenkins server. The fix requires the Startup Trigger and Groovy plugins:

Create a job that runs a startup command.

In "Build Triggers", enable "Build when node starts" with an empty label and a quiet period of 0.

In the "Build" step, select "Execute system Groovy" and run the following command:

System.setProperty("hudson.model.DirectoryBrowserSupport.CSP", "")

After restarting Jenkins, the Robot Framework report loads correctly.

3. Customizing Jenkins Relative URL Path

When Jenkins is behind an Nginx reverse proxy that also serves other applications, you may need to expose Jenkins under /jenkins instead of the root URL.

Edit jenkins.xml in the Jenkins installation directory.

Locate the arguments node under service and append --prefix="/jenkins".

Restart the Jenkins service and verify access via http://localhost:29908/jenkins.

Test the proxy configuration.

4. Fixing Git Clone Failures (Killed by signal 15)

Large repositories or slow network connections can exceed the default 10‑minute clone timeout, causing Jenkins to kill the job. Increase the timeout in the job configuration or globally to prevent the failure.

5. Windows Nodes Unable to Run JNLP Files

If double‑clicking a .jnlp file on a Windows node does nothing, run it from the command line with javaws slave-agent.jnlp to see the error. Adjust the Java security settings as needed.

6. Disabling CSRF Protection

Older Jenkins versions allowed disabling CSRF via the UI, but newer versions require a startup parameter. Add the following JVM argument when launching Jenkins (whether as a WAR in Tomcat or as a standalone JAR):

-Dhudson.security.csrf.GlobalCrumbIssuerConfiguration.DISABLE_CSRF_PROTECTION=true

7. Adjusting JVM Memory Settings

Default JVM memory is insufficient for Jenkins, leading to OutOfMemoryError: PermGen space. Set appropriate options before startup, for example:

set JAVA_OPTS=-server -Xms5000M -Xmx5000M -Xss512k -XX:+AggressiveOpts -XX:+UseBiasedLocking -XX:PermSize=256M -XX:MaxPermSize=512M -XX:+DisableExplicitGC -XX:MaxTenuringThreshold=31 -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+CMSParallelRemarkEnabled -XX:+UseCMSCompactAtFullCollection -XX:LargePageSizeInBytes=128m -XX:+UseFastAccessorMethods -XX:+UseCMSInitiatingOccupancyOnly -Djava.awt.headless=true

Key flags: -Xms: initial heap size. -Xmx: maximum heap size. -XX:PermSize and -XX:MaxPermSize: permanent generation sizes.

8. Reducing Disk Space Usage

When a job accumulates many builds, disk space can run out. Recommended actions:

Discard old builds (e.g., keep only the last 30 builds or builds from the past 2 days).

Use the Disk Usage plugin (though it may cause server lag).

Schedule a periodic task to delete Tomcat log files.

9. Setting Build Timeouts

Long‑running jobs consume memory and can crash Jenkins. Configure a global build timeout so jobs are aborted after a defined period.

10. Defining Global Environment Variables

Set common values (e.g., log directories, API endpoints) once via Manage Jenkins → Configure System → Global properties → Environment variables to simplify pipeline scripts and improve maintainability.

11. Managing Scripts with the Managed Script Plugin

Install the Managed Script plugin to store reusable scripts centrally. After installation:

Navigate to Manage Jenkins → Managed files → Add a new Config and choose "Groovy file".

Enter the script content and save.

In a job, select "Execute managed script" to run the stored script.

12. Lightweight Backup with ThinBackup

ThinBackup allows full or incremental backups of Jenkins configuration without saving build history or artifacts, enabling quick backups without stopping Jenkins. Restoring is performed via the plugin’s UI.