Re: Hudson restart requested to install new plugins (was Re: [cross-proj

[Mickael Istria <mickael.istria@xxxxxxxxxxx>]

Hi all,

I'm quite glad to see that Hudson is available for all projects! I've 
spent a little time trying to get it working for the Java Workflow 
Tooling project, and I have a few questions.

I'm wondering how to handle signing and permissions issues with Hudson 
builds. Indeed, builds started from Hudson are processed by a 
"hudsonbuild" user on build.eclipse.org.
However, this user is not allowed to sign jars, and has very basic 
permissions. This makes Hudson build unable to process the full chain 
(pde build + testing + signing + update site + p2). The signing tasks is 
the one that is currently blocking, once permissions have been set to 
"rwx" for everybody.

I understand that it would not be safe to give to "hudsonbuild" the 
right to sign jars. Thus, does any of you have an idea of a workaround I 
could use? I think a solution would be to get build started by another 
user than hudsonbuild, but I don't think that it can be done 
respectfully of security concerns...

Any suggestion is welcome!

Thanks in advance
Mickael Istria, for JWT project

Kim Moir a écrit :
> Just a FYI, the bugzilla plugin requires XMLRPC to be configured on 
> the bugzilla server.  
>
> http://www.bugzilla.org/releases/3.0/new-features.html#v30_feat_xml
>
> I don't think this is currently enabled  on bugs.eclipse.org
> see
> https://bugs.eclipse.org/bugs/xmlrpc.cgi
>
> Kim
>
>
>
>
> *Nick Boldt <nickboldt@xxxxxxxxx>*
> Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
>
> 02/12/2009 12:16 AM
> Please respond to
> Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
>
>
> 	
> To
> 	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
> cc
> 	
> Subject
> 	Hudson restart requested to install new plugins (was Re:       
>  [cross-project-issues-dev]        [galileo] FYI - Updated build with 
> STP bits)
>
>
>
> 	
>
>
>
>
>
> Woo! Thanks for posting that this is possible. Last I heard the Hudson
> setup was only for Galileo, but not I see that's not the case.
>
> I've managed to get GEF to build there using the Athena CBI builder.
>
> I've also installed a bunch of plugins and upped the number of available
> executors from 2 to 4 (it's a 4-CPU server, right?).
>
> Some useful plugins include:
>
> * Audit Trail, Disk Usage (to track who's doing what)
> * Bugzilla (hopefully to integrate CVS changes w/ related bug numbers)
> * Build-timeout (to kill long-running / stuck builds)
> * CVS Tagging (for use with Modeling builds
> * Description Setter, Text-finder (to label build status)
> * SCP, Promoted Builds, Release (to control how builds are published)
> * XVnc (for running headless UI tests)
> * Jabber, IRC, Twitter (notifications)
> * Emma (code coverage)
> * SSH Slaves (to control slaves via SSH, eg., to perhaps use vservers as
>  slaves as usage grows)
>
> So...
>
> when is a good time to restart Hudson so that we can start using these
> wonderful new plugins?
>
> > As you will see when you get to the Hudson page, I've
> > been doing some experiments to hook in automated
> > STP builds there - it's turning out to be very civilized
> > to deal with so far (and saves all that ssh'ing about).
>
> --
> Nick Boldt :: http://wiki.eclipse.org/User:Nickb
> Release Engineer :: Eclipse Modeling & Dash CBI
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>