[JENKINS-72605] agent.jar -cert argument does not work

[jenkins-infra-bot]

The -cert command line argument to agent.jar is documented to take a file path if it starts with @.

 -cert VAL       : Specify additional X.509 encoded PEM
   certificates to trust when connecting to
   Jenkins root URLs. If starting with @ then
   the remainder is assumed to be the name of
   the certificate file to read.
 

This clashes with the args4j feature not disabled for remoting (and in fact documented by core in the launch suggestions for the -secret argument), and the differing behavior between what args4j does (split by line) and how remoting would handle it (full file contents) means this doesn't work.

---

Originally reported by danielbeck, imported from: agent.jar -cert argument does not work

• assignee: jthompson
• status: Open
• priority: Minor
• component(s): remoting
• resolution: Unresolved
• votes: 0
• watchers: 1
• imported: 2025-11-25

Raw content of original issue

The -cert command line argument to agent.jar is documented to take a file path if it starts with @.

 -cert VAL                       : Specify additional X.509 encoded PEM
                                   certificates to trust when connecting to
                                   Jenkins root URLs. If starting with @ then
                                   the remainder is assumed to be the name of
                                   the certificate file to read.
 

This clashes with the args4j feature not disabled for remoting (and in fact documented by core in the launch suggestions for the -secret argument), and the differing behavior between what args4j does (split by line) and how remoting would handle it (full file contents) means this doesn't work.