Open pipelineRat opened 4 months ago
Additionally, for more details.
The maven build alone completes just fine when using jf mvn install
and sources maven dependencies for the build just fine.
The issue only occurs when using jf mvn deploy
and the jfrog client tool attempts to deploy artifacts
Further testing steps.
I found that nslookup artifactory.< domain >
was not resolving.
So I tried adding DNS to my daemon.json and restarting my dockerd service.
While that allowed the running windows container execution of nslookup artifactory.< domain >
to lookup and return the proper IP address.
This had no affect on the execution of jf mvn deploy --build-name test --build-number 777
I am still experiencing:
Caused by: java.io.IOException: JFrog service failed. Received 504: <HEAD><TITLE>Unknown Host</TITLE></HEAD>
<BODY BGCOLOR="white" FGCOLOR="black"><H1>Unknown Host</H1><HR>
<FONT FACE="Helvetica,Arial"><B>
Description: Unable to locate the server named "<em>REDACTED</em>" --- the server doe
s not have a DNS entry. Perhaps there is a misspelling in the server name, or the server no longer exists. Double-c
heck the name and try again.</B></FONT>
<HR>
<!-- default "Unknown Host" response (504) -->
</BODY>
Does anyone have any insight into the above error at all?
Update
I have tried adding the ip and hostname to the C:\Windows\System32\drivers\etc\hosts
Add-Content -Path C:\Windows\System32\drivers\etc\hosts -Value 'XXX.XXX.XXX.XXX hostname.domain'
and including "-Djdk.net.hosts.file=C:\Windows\System32\drivers\etc\hosts"
in my execution of:jf mvn deploy --build-name test --build-number 777 "-Djdk.net.hosts.file=C:\Windows\System32\drivers\etc\hosts"
Which gets the execution further along, but it fails with an unkownHostException on my proxy's hostname
If I add the proxy hostname.domain and IP to my hosts file, it turns right back around to an unknown host on the artifactory address
Describe the bug
Jfrog Client, when performing jf mvn deploy, fails to locate private artifactory server when attempting to deploy artifacts. This is occurring on Windows Platforms and Docker Containers.
I have a separate Linux Container that deploys to the same Artifactory instance with jfrog cli, but has no issue with deploying artifacts at all.
Current behavior