Skip to content
This repository was archived by the owner on Jan 25, 2022. It is now read-only.
This repository was archived by the owner on Jan 25, 2022. It is now read-only.

jpi release --release pushes plugins to wrong place? #99

@melezhik

Description

@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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions