Setup for using Hudson to deploy into Hudson

[Max Spring]

Anyone doing Hudson plugin development has probably faced this:
How to best use Hudson itself (and probably the Promoted Builds Plugin)
to deploy a newly built and tested Hudson plugin into already existing
and running Hudson instances.
I'm curious to hear how others have approached this, before I try to
cobble something up myself.
In my case I have to deal with several Hudson instances used by various
teams.
Thanks!
-Max


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Benjamin Shine-2]

I don't have a solution here, but I'll chime in that the process is a  
bit risky.
I'll offer some tips for just-before-deployment:

* Be sure to test the plugin with slave nodes running on remote machines
   before you try to deploy for real. (My first plugin crashed and  
burned
   because it was naive about remoting.)

* Watch the Hudson console (not just the build output) for exceptions.
   Running mvn -e hudson-dev:run (exception stack traces) is especially
   useful. Otherwise, exceptions triggered by jelly can get lost in  
giant
   logs, because sometimes you don't see any errors in the html page.
   Or grep the logs the Big Three of jelly exceptions:
        InvocationTargetException
        NullPointerException
        NoSuchMethodError

* Test a new plugin in a non-production clone of a production server,
   with the actual projects that the plugin will run on in production.
   Often plugin bugs are revealed by real data that weren't revealed by
   test data.


On Oct 19, 2009, at 10:24 AM, Max Spring wrote:

> Anyone doing Hudson plugin development has probably faced this:
> How to best use Hudson itself (and probably the Promoted Builds  
> Plugin)
> to deploy a newly built and tested Hudson plugin into already existing
> and running Hudson instances.
> I'm curious to hear how others have approached this, before I try to
> cobble something up myself.
> In my case I have to deal with several Hudson instances used by  
> various
> teams.
> Thanks!
> -Max
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Max Spring]

I fully agree with the listed best practices.
However, at the moment, I'm looking basically just for the mechanisms
for this use case.
-Max


On 10/19/2009 11:20 AM, Benjamin Shine wrote:

>
> I don't have a solution here, but I'll chime in that the process is a
> bit risky.
> I'll offer some tips for just-before-deployment:
>
> * Be sure to test the plugin with slave nodes running on remote machines
>   before you try to deploy for real. (My first plugin crashed and burned
>   because it was naive about remoting.)
>
> * Watch the Hudson console (not just the build output) for exceptions.
>   Running mvn -e hudson-dev:run (exception stack traces) is especially
>   useful. Otherwise, exceptions triggered by jelly can get lost in giant
>   logs, because sometimes you don't see any errors in the html page.
>   Or grep the logs the Big Three of jelly exceptions:
>     InvocationTargetException
>     NullPointerException
>     NoSuchMethodError
>
> * Test a new plugin in a non-production clone of a production server,
>   with the actual projects that the plugin will run on in production.
>   Often plugin bugs are revealed by real data that weren't revealed by
>   test data.
>
>
> On Oct 19, 2009, at 10:24 AM, Max Spring wrote:
>
>> Anyone doing Hudson plugin development has probably faced this:
>> How to best use Hudson itself (and probably the Promoted Builds Plugin)
>> to deploy a newly built and tested Hudson plugin into already existing
>> and running Hudson instances.
>> I'm curious to hear how others have approached this, before I try to
>> cobble something up myself.
>> In my case I have to deal with several Hudson instances used by various
>> teams.
>> Thanks!
>> -Max
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Flores, Cesar (GE, Corporate, consultant)]

Hi,

I'm new to Hudson and need access to docs to learn how to write a
plug-in. checking the architecture at
http://wiki.hudson-ci.org/display/HUDSON/Architecture

I find some links not working since last weeks:
https://hudson.dev.java.net/source/browse/hudson/hudson/views/hudson/mod
el/
https://stapler.dev.java.net/


Is there any mirror for content in (stapler/hudson).dev.java.net?

Thanks,
Cesar

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Benjamin Shine-2]

That first link is going to the source -- you should definitely  
download the
source yourself. Follow instructions here:
http://wiki.hudson-ci.org/display/HUDSON/Building+Hudson

...which will also build the javadoc, which you'll also need. (There's
an svn mirror available, too, but I don't know where off the top
of my head.)

I don't know if the stapler documentation is mirrored anywhere, though.


On Oct 19, 2009, at 1:44 PM, Flores, Cesar (GE, Corporate, consultant)  
wrote:

> Hi,
>
> I'm new to Hudson and need access to docs to learn how to write a
> plug-in. checking the architecture at
> http://wiki.hudson-ci.org/display/HUDSON/Architecture
>
> I find some links not working since last weeks:
> https://hudson.dev.java.net/source/browse/hudson/hudson/views/hudson/mod
> el/
> https://stapler.dev.java.net/
>
>
> Is there any mirror for content in (stapler/hudson).dev.java.net?
>
> Thanks,
> Cesar
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Kohsuke Kawaguchi]

It's likely that your IP address is blocked by java.net. See
http://wiki.hudson-ci.org/display/HUDSON/Dealing+with+java.net+outages
and contact java.net for getting the IP ban lifted.

In the mean time, see
http://wiki.hudson-ci.org/display/HUDSON/Source+code for other ways of
getting source code access.


Flores, Cesar (GE, Corporate, consultant) wrote:

> Hi,
>
> I'm new to Hudson and need access to docs to learn how to write a
> plug-in. checking the architecture at
> http://wiki.hudson-ci.org/display/HUDSON/Architecture
>
> I find some links not working since last weeks:
> https://hudson.dev.java.net/source/browse/hudson/hudson/views/hudson/mod
> el/
> https://stapler.dev.java.net/
>
>
> Is there any mirror for content in (stapler/hudson).dev.java.net?
>
> Thanks,
> Cesar
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

--
Kohsuke Kawaguchi
Sun Microsystems                   http://weblogs.java.net/blog/kohsuke/

[Kohsuke Kawaguchi]

Max Spring wrote:
> Anyone doing Hudson plugin development has probably faced this:
> How to best use Hudson itself (and probably the Promoted Builds Plugin)
> to deploy a newly built and tested Hudson plugin into already existing
> and running Hudson instances.
> I'm curious to hear how others have approached this, before I try to
> cobble something up myself.
> In my case I have to deal with several Hudson instances used by various
> teams.

I'd do this via Hudson CLI. We have a command to restart Hudson already,
so we just need to add a command to deploy a plugin.

--
Kohsuke Kawaguchi
Sun Microsystems                   http://weblogs.java.net/blog/kohsuke/

[Kohsuke Kawaguchi]

Added in 1.331.

Kohsuke Kawaguchi wrote:

> Max Spring wrote:
>> Anyone doing Hudson plugin development has probably faced this:
>> How to best use Hudson itself (and probably the Promoted Builds Plugin)
>> to deploy a newly built and tested Hudson plugin into already existing
>> and running Hudson instances.
>> I'm curious to hear how others have approached this, before I try to
>> cobble something up myself.
>> In my case I have to deal with several Hudson instances used by various
>> teams.
>
> I'd do this via Hudson CLI. We have a command to restart Hudson already,
> so we just need to add a command to deploy a plugin.
>

--
Kohsuke Kawaguchi
Sun Microsystems                   http://weblogs.java.net/blog/kohsuke/