We just upgraded to artifactory 3.0.3 and enabled rubygems support. We set up
a rubygems caching proxy that works beautifully, and a local gem repository
that unfortunately does not work.
It is not a permissions issue because I can deploy to that repository
through the UI and I have deploy permissions to that repository.
Here is a trace of gem push with verbose logging on, with no other gems in
the repo. There is nothing useful in the artifactory log, no errors.
Now, after I uploaded the gem manually though the UI, I get the following
error ( I nuked my API key so I could show those requests going back and
And the artifactory log shows that it tried to post, but failed because I
don't have delete permissions. This doesn't make any sense because when I
tried to post before from the gem command, it didn't even try to POST.
When I try to publish a different gem that is not already in the gem repo, I
get the same error as the first time.
I would greatly appreciate any help that can be provided. As you can see, it
gets the API key just fine, but then for some reason the connection resets.
One other thing that is odd. Even though I manually uploaded the gem, and
made the REST call to reindex everything, the gem index is completely empty,
and using the gem repo as a source in a Gemfile or from gem directly does
not allow gem to find my gem.
View this message in context: http://forums.jfrog.org/Ruby-gems-repository-not-working-tp7579411.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.
Get latest updates about Open Source Projects, Conferences and News.