Describe the bug
Hi,
I'm facing an issue with jfrog plugin due to special chars (e.g # char) used with the jenkins http proxy defined. The CliEnvConfigurator in setupProxy method just concatenates proxy info (scheme + username:password@host:port). So if the password has a special chars, the value set in env variables HTTPS_PROXY leader to ambigous errors( For instance : https://myusername: my#p@ssword@myproxyhost:myproxyport).
Regards
Current behavior
My configuration is :
- A Jenkins instance + a slave with a corporation proxy defined
- a jfrog plugin installed manually and configure with the corporation jfrog service
- the jf mvn-config set
- a pipeline which execute jf 'mvn clean deploy'
Reproduction steps
- Define a jenkins proxy configuration
- Install jfrog plugin, install and configure the jfrog cli
- Install and configure maven
- Create a scripted pipeline with a step executing jf 'mvn --version'
Expected behavior
No response
JFrog plugin version
1.5.5
JFrog CLI version
2.61
Operating system type and version
Réel 8
JFrog Artifactory version
7.104
JFrog Xray version
No response
Describe the bug
Hi,
I'm facing an issue with jfrog plugin due to special chars (e.g # char) used with the jenkins http proxy defined. The CliEnvConfigurator in setupProxy method just concatenates proxy info (scheme + username:password@host:port). So if the password has a special chars, the value set in env variables HTTPS_PROXY leader to ambigous errors( For instance : https://myusername: my#p@ssword@myproxyhost:myproxyport).
Regards
Current behavior
My configuration is :
Reproduction steps
Expected behavior
No response
JFrog plugin version
1.5.5
JFrog CLI version
2.61
Operating system type and version
Réel 8
JFrog Artifactory version
7.104
JFrog Xray version
No response