Open michael-doubez opened 2 months ago
@michael-doubez
Thank you for using the Jenkins JFrog plugin!
We tested the latest version (1.5.5) but were unable to reproduce the issue you mentioned - this pattern worked: *.jfrog.io
.
Since version 1.5.0, we've made several enhancements to the proxy pattern:
One of these updates may resolve your issue.
Could you please try with the latest version and let us know if it works? You might also want to try adding releases.jfrog.io to the No Proxy Host list.
Describe the bug
My jenkins is behind a proxy but my JFrog artifactory is on the local network.
When configuring NoProxy with a wildcard
*.mynetwork
, jfrog plugin still apply the proxy and the step fails. When I remove the proxy configuration completely, the step succeeds anew.Digging into #19 , I notice the implementation is using a
java.util.regex.Pattern
but noproxy expects a wildcard pattern.As an additonnal note, in the doc, you expect comma separated values but Jenkins expect one host per line. (implementation is correct)
Current behavior
Reproduction steps
Expected behavior
Proxy not used because url matches the noproxy config.
JFrog plugin version
1.5.0
JFrog CLI version
latest
Operating system type and version
Linux
JFrog Artifactory version
Enterprise Plus 7.77.11
JFrog Xray version
No response