I would like to host my plugin on jenkins-ci.org

[Gesh Markov]

Hi guys,

I am new to this group, so Hi, everyone.

I wrote a little plugin over the weekend and would like to host it on
the jenkins-ci.org as I read on the wiki, that that is the place to go
for.

Here is a link to the source-code and the short documentation I got so
far. I will update on that as I get to the final version of the plugin
as I envisioned so far, but it summarizes the use of the plugin.

https://github.com/markov/jenkins-maven-metadata-plugin

What are the next steps? What would I have to do?

Thanks guys,
Gesh

[domi]

Hi Gesh,
welcome :)
looking at the documentation, I'm not sure whether this plugin is about the same as this: https://wiki.jenkins-ci.org/display/JENKINS/Repository+Connector+Plugin
let me know if it would make sense to merge these - otherwise I'm happy to clone yours into jenkinsci
…I have already added you as committer...
reagrds Domi

On 16.04.2012, at 10:07, Gesh Markov wrote:

> Hi guys,
>
> I am new to this group, so Hi, everyone.
>
> I wrote a little plugin over the weekend and would like to host it on
> the jenkins-ci.org as I read on the wiki, that that is the place to go
> for.
>
> Here is a link to the source-code and the short documentation I got so
> far. I will update on that as I get to the final version of the plugin
> as I envisioned so far, but it summarizes the use of the plugin.
>
> https://github.com/markov/jenkins-maven-metadata-plugin
>
> What are the next steps? What would I have to do?
>
> Thanks guys,
> Gesh

[Gesh Markov]

Hi Domi,

thanks for the quick reply. It looks quite similar, but there are some differences.

The repository connector downloads the artifact, while mine just sets environment variables to the location of the artifacts and lets the build steps decide what to do with that. And in my case I am not downloading anything.

It also has only 1 global repository, while mine allows for repository configuration per job.

But thanks for the tip, I will definitely add it as a reference to my documentation in case that's what people need. For my needs the Repository Connector Plugin would be too much.

As for merging both plugins - I am not sure. The repo connector works as a build step while mine as a parameter definition, so they wouldn't be mutually exclusive and can both be installed and work together. On the other hand having one plugin fulfil both tasks would make it easier to discover (granted if I knew the other plugin existed I might have opted for extending that instead of coding one from scratch).

What would you recommend? Are you the maintainer of the repo connector plugin, or is it just coincidence of names?

Cheers,

Gesh

On Monday, April 16, 2012 10:22:00 AM UTC+2, domi wrote:

Hi Gesh,
welcome :)
looking at the documentation, I'm not sure whether this plugin is about the same as this: https://wiki.jenkins-ci.org/display/JENKINS/Repository+Connector+Plugin
let me know if it would make sense to merge these - otherwise I'm happy to clone yours into jenkinsci
…I have already added you as committer...
reagrds Domi

On 16.04.2012, at 10:07, Gesh Markov wrote:

> Hi guys,

>
> I am new to this group, so Hi, everyone.
>
> I wrote a little plugin over the weekend and would like to host it on
> the jenkins-ci.org as I read on the wiki, that that is the place to go
> for.
>
> Here is a link to the source-code and the short documentation I got so
> far. I will update on that as I get to the final version of the plugin
> as I envisioned so far, but it summarizes the use of the plugin.
>
> https://github.com/markov/jenkins-maven-metadata-plugin
>
> What are the next steps? What would I have to do?
>
> Thanks guys,
> Gesh

[domi]

No big worries, I just forked yours…: https://github.com/jenkinsci/maven-metadata-plugin
…and renamed it to 'maven-metadata-plugin' - as none of the plugins usually has the 'jenkins' prefix.
…and yes, I'm the maintainer of the repository-connector :)
don't forget to update the artifactId and add a plugin docu page on the wiki…
welcome again :)
regards Domi

On 16.04.2012, at 10:07, Gesh Markov wrote:

> Hi guys,
>
> I am new to this group, so Hi, everyone.
>
> I wrote a little plugin over the weekend and would like to host it on
> the jenkins-ci.org as I read on the wiki, that that is the place to go
> for.
>
> Here is a link to the source-code and the short documentation I got so
> far. I will update on that as I get to the final version of the plugin
> as I envisioned so far, but it summarizes the use of the plugin.
>
> https://github.com/markov/jenkins-maven-metadata-plugin
>
> What are the next steps? What would I have to do?
>
> Thanks guys,
> Gesh

[Jesse Farinacci]

Greetings,

On Mon, Apr 16, 2012 at 10:17 AM, domi <[hidden email]> wrote:
> No big worries, I just forked yours…: https://github.com/jenkinsci/maven-metadata-plugin
> welcome again :)

http://ci.jenkins-ci.org/job/plugins_maven-metadata/

Welcome aboard,
-Jesse

--
There are 10 types of people in this world, those
that can read binary and those that can not.

[Gesh Markov]

Thanks for the quick responses. I have just a few more question.

How do I release the plugin and make it discoverable by installed jenkins servers?

Is there a template for the Wiki plugin page I can clone from?

Thanks,

Gesh

On Monday, April 16, 2012 10:07:07 AM UTC+2, Gesh Markov wrote:

Hi guys,

I am new to this group, so Hi, everyone.

I wrote a little plugin over the weekend and would like to host it on
the jenkins-ci.org as I read on the wiki, that that is the place to go
for.

Here is a link to the source-code and the short documentation I got so
far. I will update on that as I get to the final version of the plugin
as I envisioned so far, but it summarizes the use of the plugin.

https://github.com/markov/jenkins-maven-metadata-plugin

What are the next steps? What would I have to do?

Thanks guys,
Gesh

On Monday, April 16, 2012 10:07:07 AM UTC+2, Gesh Markov wrote:

Hi guys,

I am new to this group, so Hi, everyone.

I wrote a little plugin over the weekend and would like to host it on
the jenkins-ci.org as I read on the wiki, that that is the place to go
for.

Here is a link to the source-code and the short documentation I got so
far. I will update on that as I get to the final version of the plugin
as I envisioned so far, but it summarizes the use of the plugin.

https://github.com/markov/jenkins-maven-metadata-plugin

What are the next steps? What would I have to do?

Thanks guys,
Gesh

[domi]

As your plugin is based on Jenkins 1.447 - you should be fine by updating/adding the <scm> info in the pom.xml and just doing a maven release. 

(example pom: https://github.com/jenkinsci/managed-scripts-plugin/blob/master/pom.xml)

This will publish the artifacts to 'http://repo.jenkins-ci.org'. After that the infrastructure backend processes

will take care of the rest and record your plugin in the update center and make it available for everyone.

For the wiki page, just copy an existing one you like and and change the pluginId in the confluence hudson/jenkins-info-plugin at the very top of each plugin page.

e.g. this one: https://wiki.jenkins-ci.org/display/JENKINS/Managed+Script+Plugin

I recommend you have the following things on your wiki page:

- excerpt (this will be reused in the plugin overview page)

- description

- release history with notes about the new features/fixes of each release

- add some labels to add your plugin to some groups (e.g. plugin-maven)

You should also add your Wiki page as <url> in the pom.xml

regards Domi

On 16.04.2012, at 17:35, Gesh Markov wrote:

Thanks for the quick responses. I have just a few more question.

How do I release the plugin and make it discoverable by installed jenkins servers?

Is there a template for the Wiki plugin page I can clone from?

Thanks,

Gesh

On Monday, April 16, 2012 10:07:07 AM UTC+2, Gesh Markov wrote:

Hi guys,

I am new to this group, so Hi, everyone.

I wrote a little plugin over the weekend and would like to host it on
the jenkins-ci.org as I read on the wiki, that that is the place to go
for.

Here is a link to the source-code and the short documentation I got so
far. I will update on that as I get to the final version of the plugin
as I envisioned so far, but it summarizes the use of the plugin.

https://github.com/markov/jenkins-maven-metadata-plugin

What are the next steps? What would I have to do?

Thanks guys,
Gesh

On Monday, April 16, 2012 10:07:07 AM UTC+2, Gesh Markov wrote:

Hi guys,

I am new to this group, so Hi, everyone.

I wrote a little plugin over the weekend and would like to host it on
the jenkins-ci.org as I read on the wiki, that that is the place to go
for.

Here is a link to the source-code and the short documentation I got so
far. I will update on that as I get to the final version of the plugin
as I envisioned so far, but it summarizes the use of the plugin.

https://github.com/markov/jenkins-maven-metadata-plugin

What are the next steps? What would I have to do?

Thanks guys,
Gesh

[Georgi Markov]

Thanks Domi, thanks Jesse,

I followed your instructions and got into some trouble with authenticating against github and jenkins-ci.org, since I have different usernames and passwords but if I specified them on the command line as suggested no this page https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins the release plugin was using the same username:password for both connections, and innevitably one failed. I will update the wiki page to reflect that.

Eventually I used the settings.xml for jenkins-ci.org and an .ssh/config file for github and that worked with no extra arguments on the command line.

Cheers guys, thanks again for the support,

Gesh

On Monday, 16 April 2012 18:28:03 UTC+2, domi wrote:

As your plugin is based on Jenkins 1.447 - you should be fine by updating/adding the <scm> info in the pom.xml and just doing a maven release. 

(example pom: https://github.com/jenkinsci/managed-scripts-plugin/blob/master/pom.xml)

This will publish the artifacts to 'http://repo.jenkins-ci.org'. After that the infrastructure backend processes

will take care of the rest and record your plugin in the update center and make it available for everyone.

For the wiki page, just copy an existing one you like and and change the pluginId in the confluence hudson/jenkins-info-plugin at the very top of each plugin page.

e.g. this one: https://wiki.jenkins-ci.org/display/JENKINS/Managed+Script+Plugin

I recommend you have the following things on your wiki page:

- excerpt (this will be reused in the plugin overview page)

- description

- release history with notes about the new features/fixes of each release

- add some labels to add your plugin to some groups (e.g. plugin-maven)

You should also add your Wiki page as <url> in the pom.xml

regards Domi

On 16.04.2012, at 17:35, Gesh Markov wrote:

Thanks for the quick responses. I have just a few more question.

How do I release the plugin and make it discoverable by installed jenkins servers?

Is there a template for the Wiki plugin page I can clone from?

Thanks,

Gesh

On Monday, April 16, 2012 10:07:07 AM UTC+2, Gesh Markov wrote:

Hi guys,

I am new to this group, so Hi, everyone.

I wrote a little plugin over the weekend and would like to host it on
the jenkins-ci.org as I read on the wiki, that that is the place to go
for.

Here is a link to the source-code and the short documentation I got so
far. I will update on that as I get to the final version of the plugin
as I envisioned so far, but it summarizes the use of the plugin.

https://github.com/markov/jenkins-maven-metadata-plugin

What are the next steps? What would I have to do?

Thanks guys,
Gesh

On Monday, April 16, 2012 10:07:07 AM UTC+2, Gesh Markov wrote:

Hi guys,

I am new to this group, so Hi, everyone.

I wrote a little plugin over the weekend and would like to host it on
the jenkins-ci.org as I read on the wiki, that that is the place to go
for.

Here is a link to the source-code and the short documentation I got so
far. I will update on that as I get to the final version of the plugin
as I envisioned so far, but it summarizes the use of the plugin.

https://github.com/markov/jenkins-maven-metadata-plugin

What are the next steps? What would I have to do?

Thanks guys,
Gesh