Fix Jenkins Pipeline Errors: Plugin Updates, Maven Build Failures, Git Config

1. Replace plugin update site with domestic mirror

Reason: In Manage Jenkins → Manage Plugins, the Updates tab shows no data and reports a timeout error when checking update sites.

Analysis: The configured update site URL is https://updates.jenkins.io/update-center.json, which is unreachable from the server.

Solution: Change the update site to a reachable domestic mirror, e.g.

https://mirrors.tuna.tsinghua.edu.cn/jenkins/updates/update-center.json

or

http://mirror.xmission.com/jenkins/updates/update-center.json

After submitting, click “Check now” and restart Jenkins if needed.

2. Maven pipeline build reports missing server JVM

Command executed: + mvn clean deploy Error output indicates a missing server JVM library (libjvm.so) and suggests installing a JDK/JRE that includes it.

Investigation showed the Jenkins pod and Maven container were functioning, so the issue stemmed from the build node’s Java installation.

Solution: Use a build node with a proper JDK that contains the required server JVM libraries.

3. Jenkins pipeline fails with Git config lock file error

Error message:

error: could not lock config file .git/config: File exists

Investigation revealed leftover .git/config.lock files in Jenkins cache directories.

Solution: Locate and delete the lock file, e.g.

find / -name "config.lock" -type f
rm /path/to/config.lock

4. Maven pipeline reports "unable to allocate file descriptor table" error

Root cause: The build node’s file descriptor limit was too low.

Solution steps:

Check current limit with ulimit -n.

If low, increase limits in /etc/security/limits.conf:

* soft nofile 65535
* hard nofile 65535
ulimit -n 65535

Adjust Docker service limits by adding --default-ulimit nofile=65535:65535 to /usr/lib/systemd/system/docker.service and restart Docker:

systemctl daemon-reload
systemctl restart docker

After applying these changes, the pipeline builds successfully.