Resolving Common Jenkins Issues: Plugin Compatibility, CSP, Path Configuration, Clone Timeouts, and More

1. Performance plugin compatibility issue : In Jenkins v2.298 with Performance v3.19 the plugin causes UI table/div misalignment and prevents saving configuration. Solutions are to switch the freestyle job to a pipeline job, manually edit the project's config.xml, or downgrade Jenkins to v2.263.4 LTS.

2. CSP security policy blocks Robot Framework logs : The default CSP is

sandbox; default-src 'none'; img-src 'self'; style-src 'self';

. Workaround is to create a job with a startup trigger and run Groovy to clear CSP:

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

.

3. Custom Jenkins relative access path when behind Nginx: edit jenkins.xml and add the argument --prefix="/jenkins" to the arguments node, then restart Jenkins.

4. Git clone failure (signal 15) : The clone is killed after the default 10‑minute timeout. Increase the clone timeout in the Jenkins job configuration to accommodate large repositories or slow networks.

5. Build step marked failure : Ensure batch or shell scripts end with exit 0 so Jenkins treats the step as successful.

6. Replace vulnerable commons-fileupload jar in Jenkins running under Tomcat: download the latest commons-fileupload-1.4.jar and create a symbolic link with

mklink webapps\jenkins\WEB-INF\lib\commons-fileupload-1.3.1-jenkins-2.jar webapps\jenkins\WEB-INF\lib\commons-fileupload-1.4.jar

, then delete the old jar and restart Tomcat.

7. Disable CSRF protection for older Jenkins versions via the global security UI, or for newer versions add the JVM argument

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

to the startup script.

8. Disk‑space optimization : Discard old builds (e.g., keep only the last 30 builds or builds from the past 2 days), optionally use the Disk Usage plugin (with caution), schedule a job to clean Tomcat logs, and set build timeouts to prevent long‑running jobs from exhausting memory.

9. Set global environment variables in "Manage Jenkins → Configure System → Global properties" to avoid hard‑coding values such as log paths or API endpoints in pipelines.

10. Unified script management with the Managed Script plugin: install the plugin, create a managed Groovy file via "Managed files → Add a new Config → Groovy file", then invoke it in jobs using the "Execute managed script" build step.

11. Lightweight backup using the ThinBackup plugin: perform full or incremental backups of Jenkins configuration (excluding build history and artifacts) and restore via the plugin UI when needed.