jpi release --release pushes plugins to wrong place?

[melezhik]

Hi! According to jenkins.trb docs (https://github.com/jenkinsci/jenkins.rb/wiki/Getting-Started-With-Ruby-Plugins#wiki-sharing-your-plugin-with-the-community)

$ jpi release --release 
bundling...
Using json (1.7.7) 
Using slop (3.0.4) 
Using jenkins-plugin-runtime (0.2.3) 
Using logger (1.2.8) 
Using term-ansicolor (1.1.1) 
Using simple_console (0.0.1) from git://github.com/melezhik/simple_console.git (at master) 
Using bundler (1.3.2) 
Your bundle is complete! It was installed into ./pkg/vendor/gems
chef plugin 0.0.6 built to pkg/chef.hpi
deploying as a release
Generating POM
Uploading pkg/chef.hpi
See http://maven.jenkins-ci.org/content/repositories/releases/org/jenkins-ci/ruby-plugins/chef/0.0.6

According https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins new pligins should appear at http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/ which is not http://maven.jenkins-ci.org/content/repositories/releases/org/jenkins-ci/ruby-plugins/

So I just need that my plugin would be listed at official jenkins repository to be installed via jenkins server GUI

[alvarolorentedev]

@melezhik did you found any solution for this?

[melezhik]

@kanekotic no I have not , indeed I have not looked a solution at all, as usually I install my plugin via hpi file gets downloaded from URL. By creating this issue I just wanted to pay an attention on inconvenience

[alvarolorentedev]

@melezhik so it is actually not a problem wit 0.4.1, the code is correct but the message printed is wrong so I added a PR. Also I have noticed that for the wiki to update it is necessary to edit it.

[melezhik]

@kanekotic thanks, I am not actively using jpi right now, but I will try to check if issue is gone when I get a chance ...