Sunday, 30 May 2010

Hudson deploy-websphere plugin ready to ship

Ready to ship!
Eventually I have decided to go for a new plugin having a dependency with the existing deploy plugin. This, in my opinion, is the best solution because, being WebSphere a proprietary product and being some jar not redistributable there is a needing of a little extra configuration (just copying a couple of proprietary jar on the classpath) at the end of the plugin installation. Anyway more details will be on the wikis (either my personal one and the one of hudson if I can publish my plugin) once I got the right to check-in on the hudson java.net repository.
So hung on for a little while....

Antonio

Saturday, 29 May 2010

Hudson and WebSphere

It has been a while I have been playing with Hudson. It is way better than any other integration server I have seen and is crazily simple to extend. I'd love to use it at work but for the moment we are still stucked with Cruise Control. Said that, I think the integration with the "WebSphere world" can be kind of improved.
I mean Hudson war file can be installed on WAS; moreover there are already few WebSphere/IBM plugins as the WAS Builder and the RAD Builder. But either these than the out of the box deploy plugin don't support any WebSphere server. The WAS Builder plugin allow you to deploy on WebSphere but for what I undestood you need to write your own script.
I know WebSphere is a proprietary product and is a kind of closed world, and WAS itself has been defined from Hudson users "exhotic" but, being working with WebSphere for a while, and predicting I'll be working with it for yet another while, I'd like to have an out of the box mechanism to deploy the artifacts to WAS and even WebSphere Portal. Being this not existing at the moment I did decide to write it myself. :)
The solution will be havily JMX based and I am taking freely hints from the java file here.
At the moment, until I undestand if I can extend the already existing plugin, I am going toward this direction as you can see from the picture below:


otherwise I will start my own plugin.
My plan is to build up the complete solution in 3 steps:

  1. release the WebSphere deploy plugin for WebSphere Application Server 6.1/7 (with security disabled)
  2. release the WebSphere deploy plugin for WebSphere Application Server 6.1/7 (with security enabled)
  3. release the WebSphere deploy plugin for WebSphere Portal Server 6.1
The steps 2 and 3 might have some extra complication due to some extra proprietary IBM jar files needed and moreover, for be able the plugin to work, an IBM JRE is needed.
I did decided to push these extra complication back and focus on the point 1 for the moment that seems "easier".
I should say I am not really far away to have a "golden candidate", I just need to undestand the gotcha relative to extending the existing plugin. So what to say, if you are a WebSphere and Hudson user waiting for a mechanism to deploy your build artifacts with an out of the box solution to WAS 6.1/7 and WPS 6.1 stay tuned!!

Antonio