Allow download of dependencies from internal sources about build-info-go HOT 5 OPEN

@dg424,
We recommend using JFrog CLI's jf docker pull command to pull docker images from Artifactory.

from build-info-go.

It is not a docker image. bi-cli mvn option tries to download a file directly from the internet - the line I mentioned. The ask is how to get bi-cli to use our local Artifactory instead ? Note that this is a jar file download as we're currently testing the maven/mvn option.

from build-info-go.

@ddag,
JFrog CLI uses build-info-go as a depdemcy and allows running the `jf mvn' command to resolve maven depdemcies from Artifactory as well as generating build-info.

from build-info-go.

Ok, I had to do jf mvn-config first which created .jfrog/projects/maven.yml. After this, the build worked and the jar was deployed to our artifactory server, but build info was not published and I got this:

[main] INFO org.jfrog.build.extractor.maven.BuildDeploymentHelper - Artifactory Build Info Recorder: publish build info set to false, build info will not be published...

from build-info-go.

@dg424,
Here's how you can generate build-info and publish it to Artifactory for your maven build with jfrog-cli:

jf mvn install --build-name b1 --build-number 1
jf rt bp b1 1

You can read more about this in the JFrog CLI documentation. Let us know if you have follow-up questions.

from build-info-go.