Proxy/Replicate via Artifactory

When attempting to create a remote-repository in Jfrog Artifactory, the artifacts can be somewhat accessed but we get a html file and not the actual artifact

Using these are URL in artifactory generic remote doesn’t really work

The 2nd allows download of the html file in place of artifact and it looks like the binaries repo is doing a redirection into an s3 bucket but Artifactory isn’t handling the redir well

<!DOCTYPE html>
<html lang="en">
    <title>SonarSource Downloads-CDN</title>
    <link rel="icon" type="image/x-icon" href="./site-resources/favicon.ico">
<div id="navigation"></div>
<div id="listing"></div>

<script type="text/javascript" src="./site-resources/jquery.min.js"></script>
<script type="text/javascript">
  var S3BL_IGNORE_PATH = true;
  var BUCKET_URL = '';
  var BUCKET_WEBSITE_URL = document.location.origin;
  var EXCLUDE_FILE = [/^site-resources.*$/];
<script type="text/javascript" src="./site-resources/list.js"></script>
<!-- docs: -->


Has anyone successfully wrapped the remote repo with an Artifactory cache?

Hey there. isn’t really meant to function as a remotely accessible repo – for most artifacts that you would use in a build, they’re sitting in the normal Maven repos (like sonar-java).

What are you trying to do that you need to mirror the binaries site?

1 Like

Given that the artifacts existing in maven-central as Colin said, the right approach is

  • Setup Artifactory or SonatType nexus caching proxy repo for maven-central (which any java shop will already have)
  • Have people pull content from there:

e.g., https://… my-repo-manager/…/maven-centrel-remote/org/sonarsource/scanner/cli/sonar-scanner-cli/…

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.