Reputation: 290
Basically what it says on the tin. I have two instances of Artifactory running and I want to set up a local repo on Artifactory instance A to be a remote repo on Artifactory instance B. I type in the correct path (and every plausible variation of it) and when I click "Test" it says everything is good to go. I set up the correct password authentication, too, and clicking "Test" also says everything is good. I made sure that no repo was blacked out or anything and I checked the system logs to ensure that nothing went wrong silently.
And yet, I can't actually query any data from that repo. Artifactory says the remote repo contains zero Artifacts. If I try to download a specific file from that repo, I get a 404.
I tried messing about randomly with the settings, which I suppose unsurprisingly didn't work. But I get no error message, no warnings, no odd behaviors. I don't know what else to try.
Upvotes: 0
Views: 305
Reputation: 290
So my mistake turned out to be that the repository key it asks for isn't the repository key of the remote repo, but the repository key of the local repo you want to create. I suppose this is there to let you have a remote repo with a different public-facing name than the actual repo it pulls from. Otherwise you have to type in myartifactory.com/my-repo-local and then my-repo-local again in the repository key.
Upvotes: 0