Hey, Blank repo path in the dependencies section is usually a result of local cache or deferent source which is not Artifactory that those dependencies came from. Regarding the build artifacts, because the deployment was accoured to Artifactory (verify in the build log) they suppose to exists in it. Maybe they were deleted or there is a problem in the build.
Lior > On Aug 12, 2015, at 11:35 PM, rduncan <[email protected]> wrote: > > Hi. We have a project where artifacts created with Ant/Ivy are being > published via ivy:publish and the build information is being created via the > TeamCity Artifactory plugin. While we see the (two) jars the published > modules section of the build information, and we see the proper > dependencies, the repo paths are blank in both cases. > > What needs to be configured in order for the repo paths to be completed so > that the artifact links are navigable? > > -Rich > > > > -- > View this message in context: > http://forums.jfrog.org/Repo-Path-for-artifacts-and-dependencies-deployed-using-TeamCity-Artifactory-Plugin-tp7580420.html > Sent from the Artifactory - Users mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > _______________________________________________ > Artifactory-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/artifactory-users
------------------------------------------------------------------------------
_______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
