RE: CI Grid, Windows and Paths

[Jamie Whitehouse <ba...@genesyslab.com>]

On Tue, 2008-12-23 at 21:16 -0500, Brian E. Fox wrote:

> It is slightly unnatural but unfortunately Hudson only launches the
> slaves as a process, they don't run as persistent servers.

Coming to this thread a bit late, but as of Hudson 1.255 you can install
slaves as a windows service, see Kohsuke's blog post:
http://weblogs.java.net/blog/kohsuke/archive/2008/09/installing_huds_1.html

Before that you could wrap it in Java Service Wrapper.


>  However I
> don't think it's completely useless because the testing and building
> once maven runs is the same. We just have to fool with the env a bit
> more.
> 
> The maven version used must have been updated by someone with access,
> it's not updated automatically.
> 
> -----Original Message-----
> From: Brett Porter [mailto:brett@apache.org] 
> Sent: Tuesday, December 23, 2008 7:08 PM
> To: Maven Developers List
> Subject: Re: CI Grid, Windows and Paths
> 
> 
> On 24/12/2008, at 10:58 AM, Benjamin Bentmann wrote:
> 
> > Now my question, how do we want to handle that smoothly on the grid?  
> > I see three options:
> >
> > a) Simply avoid using Maven 2.0.x for affected builds
> > b) Update the path translation in Maven 2.0.x to match 2.1.x
> > c) Update the *.bat files to ensure M2_HOME is absolute
> > d) Update MavenCli or similar to fix maven.home
> >
> > Option c) seems to be as easy as
> >
> >  for %%i in ("%M2_HOME%") do set "M2_HOME=%%~fi"
> >
> > but I haven't fully tried the patch yet.
> 
> +1 for fixing c), especially if it is that simple.
> 
> >
> >
> > Option c) or d) are my favorites as I personally dislike the grid  
> > env for Windows: it's just unnatural, how many Windows users run  
> > Maven with a unix-style home dir? I see ourselves testing an exotic  
> > environment and chasing issues a regular Windows user would never  
> > face. Hence I believe it's worth to get rid of Hudson anomalies at  
> > the front door.
> >
> > WDYT?
> 
> Agreed here too - can the Windows job be reconfigured to a more  
> natural location?
> 
> Trying to understand correctly - how did the version of Maven switch  
> from 2.1.0-M1 to 2.0.9 to 2.1.0-M1 again? Was this something you  
> altered the configuration for, or is it happening based on what was  
> last built?
> 
> - Brett
> 
> --
> Brett Porter
> brett@apache.org
> http://blogs.exist.com/bporter/
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 

					
-------------------------------------------------------------------------------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential and proprietary information of Alcatel-Lucent and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or its affiliated entities.