Re: Groovy plugin in Hudson - custom tool locations

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Groovy plugin in Hudson - custom tool locations

David Vrzalik-2
On Monday 06 July 2009 02:04:34 pm you wrote:

> Hi!
>
> I’d like to use the groovy plugin You developed for Hudson in my project
> and I was wondering, whether there was a possibility for changing the
> groovy location for slave computers, as there is for the JDK and various
> other build tools. I’m trying to set up a distributed cluster of Hudson
> instances to do testing of our software on multiple platforms, and as
> always, when I set up the windows box, I have to change all the tool paths.
>
> If there’s no such possibility at the moment, maybe you can give me some
> pointer as to how I could improve your plugin, by adding this option, I
> guess, I might be able to implement it.
>
> Many thanks in advance for Your response.
>

Hi,
the plugin (and Hudson generally) is capable of expanding environment
variables in tool path.
For example, our global configuration contains using this path:
${COMMON_TOOLS}${SEPARATOR}groovy-1.5.4

You just have to make sure that your environment has the right values
corresponding to the system the slave is running on.

I hope this helps...



--
David Vrzalik

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

Reply | Threaded
Open this post in threaded view
|

Re: Groovy plugin in Hudson - custom tool locations

Tom Huybrechts
Can you update the groovy plugin to use ToolInstallation (like Java,
Ant and Maven) ?


On Tue, Jul 7, 2009 at 11:03 AM, David Vrzalik<[hidden email]> wrote:

> On Monday 06 July 2009 02:04:34 pm you wrote:
>> Hi!
>>
>> I’d like to use the groovy plugin You developed for Hudson in my project
>> and I was wondering, whether there was a possibility for changing the
>> groovy location for slave computers, as there is for the JDK and various
>> other build tools. I’m trying to set up a distributed cluster of Hudson
>> instances to do testing of our software on multiple platforms, and as
>> always, when I set up the windows box, I have to change all the tool paths.
>>
>> If there’s no such possibility at the moment, maybe you can give me some
>> pointer as to how I could improve your plugin, by adding this option, I
>> guess, I might be able to implement it.
>>
>> Many thanks in advance for Your response.
>>
>
> Hi,
> the plugin (and Hudson generally) is capable of expanding environment
> variables in tool path.
> For example, our global configuration contains using this path:
> ${COMMON_TOOLS}${SEPARATOR}groovy-1.5.4
>
> You just have to make sure that your environment has the right values
> corresponding to the system the slave is running on.
>
> I hope this helps...
>
>
>
> --
> David Vrzalik
>
> ---------------------------------------------------------------------
> 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]

Reply | Threaded
Open this post in threaded view
|

Re: Groovy plugin in Hudson - custom tool locations

David Vrzalik-2
Yes, I guess I could do that ...

> Can you update the groovy plugin to use ToolInstallation (like Java,
> Ant and Maven) ?
>
> On Tue, Jul 7, 2009 at 11:03 AM, David Vrzalik<[hidden email]> wrote:
> > On Monday 06 July 2009 02:04:34 pm you wrote:
> >> Hi!
> >>
> >> I’d like to use the groovy plugin You developed for Hudson in my project
> >> and I was wondering, whether there was a possibility for changing the
> >> groovy location for slave computers, as there is for the JDK and various
> >> other build tools. I’m trying to set up a distributed cluster of Hudson
> >> instances to do testing of our software on multiple platforms, and as
> >> always, when I set up the windows box, I have to change all the tool
> >> paths.
> >>
> >> If there’s no such possibility at the moment, maybe you can give me some
> >> pointer as to how I could improve your plugin, by adding this option, I
> >> guess, I might be able to implement it.
> >>
> >> Many thanks in advance for Your response.
> >
> > Hi,
> > the plugin (and Hudson generally) is capable of expanding environment
> > variables in tool path.
> > For example, our global configuration contains using this path:
> > ${COMMON_TOOLS}${SEPARATOR}groovy-1.5.4
> >
> > You just have to make sure that your environment has the right values
> > corresponding to the system the slave is running on.
> >
> > I hope this helps...
> >
> >
> >
> > --
> > David Vrzalik
> >
> > ---------------------------------------------------------------------
> > 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]

--
David Vrzalik

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