Evolution of the Hudson plugin for Jenkins
Thomas Segismont
tsegismo at redhat.com
Mon Nov 25 10:04:11 UTC 2013
Le 24/11/2013 18:44, Jérémie a écrit :
> Hi all
>
> I would like to make compatible the Hundson plugin with Jenkins.
> I already have a working prototype:
> https://github.com/jerr/jboss-rhq/commit/ea95ebcbf5bc4b5d19268ef88815668499ff8d66
>
> Before creating a Bugzilla ticket I would like to have your opinion. Is
> it better to create a new plugin or to modify the existing hudson plugin
>
> Thank you for your help.
>
>
> Regards,
> Jérémie
>
>
> _______________________________________________
> rhq-devel mailing list
> rhq-devel at lists.fedorahosted.org
> https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
>
Hi Jérémie,
Hudson/Jenkins are so similar that we should keep just one, I think.
With respect to the changes you pushed on Github, here are my comments:
* keep the server/service names in the plugin descriptors (for
compatibility with existing resources)
* change the HudsonDiscoveryComponent discovery class to give new server
resources an appropriate name and description
* add a new "server-type" read-only plugin configuration property to the
server resource; its value will be set in HudsonDiscoveryComponent and
will help to differentiate Jenkins and Hudson servers (you will no
longer need to check that in child resource components).
Thanks for making this plugin evolve!
Cheers,
Thomas
More information about the rhq-devel
mailing list