Integrating Hudson v2 securely

[Simon Champion]

We have a large multi-project Jira installation. We currently use Jenkins as our CI platform, with the Marvelution Jira/Jenkins plugins to integrate everything. All is working fine.

We are taking over control an existing project which uses its own Jira with Hudson (v2.2), and the old Marvelution Jira/Hudson plugin. We need to port this project into our Jira, but it will retain its existing Hudson server. I'm not sure of the approach I should be taking.

I don't think I can keep using the old Hudson plugin, as (a) that doesn't appear to be supported and more, and (b) it seems to have some functionality gaps that make it unusable in a larger enterprise environment (ref: https://marvelution.atlassian.net/wiki/display/MARVJIRAHUDSON/Documentation+Homeand https://marvelution.atlassian.net/wiki/display/JJI/Documentation+Home).

On the other hand, I understand (https://marvelution.atlassian.net/browse/JJI-102) that the more up-to-date Jenkins plugin does not work with recent versions of Hudson. But that seems like it's just the plugin at the Jenkins end that this applies to, so does that mean I can still use the Jenkins plugin in Jira to connect to Hudson? I'm not clear on that.

And assuming I can use it, what functionality will I lose by not having the corresponding plugin at the other end?

Thank you.

(and yes, I know the real solution is to port the Hudson server to Jenkins, and that probably will happen further down the line, but I need to get things up and running sooner than that)

[Mark Rekveld - Marvelution · Accepted solution]

Hi,

You are correct, the old Hudson plugin is deprecated and no longer supported. It simply didn't perform in large instances causing all kinds of issues.

The new setup aims to fix this. And you are no longer required to have the Jenkins/Hudson plugin installed, but it is recommended.

I use the Jenkins CI server for testing this and am able to sync jobs and builds from that server without having the plugin installed. See https://marvelution.atlassian.net/wiki/display/JJI/Application+LinksThis shown the configuration in JIRA 6 to link to a Jenkins/Hudson server without the plugin installed.

I've added https://marvelution.atlassian.net/browse/JJI-141to start including the Hudson CI server during testing, and also finally fixed https://marvelution.atlassian.net/browse/JJI-102.

Currectly you will only loose the Entity Links, JIRA Build Notifier and JIRA Changelog Annotator in Hudson.

Hopefully this anwsers your question. If not let me know.

Cheers, Mark

[Simon Champion]

Hi Mark,

Just to confirm that things seem to be working okay.

I'm not too worried about some features being missing as we're going to be treating this Hudson box as a legacy system so we're fine about not having all the bells and whistles, but good to get the key bits working.

Thanks again for your help.

Simon C.

[Mark Rekveld - Marvelution]

Hi Simon,

Good to hear that its working. And your welcome.

If you have any other questions, comments or feature requests then let me know.

Cheers, Mark

[Simon Champion]

Hi Mark,

Thank you for the quick response and for fixing the JJI-102 ticket. Very much appreciated.

I'll try to get things set up with the new plugin version and see how it goes.

Many thanks,

Simon C.