Comment 3 for bug 2055280

I agree - they do not check argc there, causing the startup segfault.

I have done the test in lxc container:

$lxc launch ubuntu-daily:noble

There i have installed jenkins weekly release:
---
sudo wget -O /usr/share/keyrings/jenkins-keyring.asc \
  https://pkg.jenkins.io/debian/jenkins.io-2023.key
echo deb [signed-by=/usr/share/keyrings/jenkins-keyring.asc] \
  https://pkg.jenkins.io/debian binary/ | sudo tee \
  /etc/apt/sources.list.d/jenkins.list > /dev/null
sudo apt-get update
sudo apt-get install jenkins
--

and configured a pipeline to build a maven project[1]

I have configured an agent to connect and ran it as following:

JAVA_HOME=/usr/lib/jvm/java-17-openjdk-amd64/ java -jar agent.jar -url http://<ip>:8080/ -secret @secret-file -name "self-server" -workDir "/home/test/work"

The build successfully clones the project, starts maven and builds it.

I wonder if there is something specific in your setup (e.g. a docker container used as an agent) that may contribute to the issue?

[1] https://github.com/vpa1977/spring-petclinic/tree/spring-boot-2.7.3