You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@apache.org by Tim Ellison <t....@gmail.com> on 2010/01/06 11:56:00 UTC
Standard tool locations
We currently have a number of tools (e.g. JDKs, Ant, Maven, etc) defined
globally, in the 'Manage Hudson' configuration page.
Some are already a bit dubious, being declared as "on Ubuntu only", so
not really global at all. Now we have a Windows client the paths are
totally wrong there, so specifying a build to use 'latest' is not going
to work.
I think the only option is to push the tool location definitions down to
individual nodes. That will require some duplication across the Ubuntu
nodes, but will allow us to specify the actual tools available on a
node, and the correct paths for Windows.
WDYT? Any better option?
Regards,
Tim
Re: Standard tool locations
Posted by Niklas Gustavsson <ni...@protocol7.com>.
On Wed, Jan 6, 2010 at 12:27 PM, Tim Ellison <t....@gmail.com> wrote:
> On 06/Jan/2010 11:15, Aristedes Maniatis wrote:
>> On 6/01/10 9:56 PM, Tim Ellison wrote:
>>> We currently have a number of tools (e.g. JDKs, Ant, Maven, etc) defined
>>> globally, in the 'Manage Hudson' configuration page.
>>>
>>> Some are already a bit dubious, being declared as "on Ubuntu only", so
>>> not really global at all. Now we have a Windows client the paths are
>>> totally wrong there, so specifying a build to use 'latest' is not going
>>> to work.
>
> I should correct this, since we can override the 'latest' locations. So
> we would just 'push down' the platform specific tools to the specific nodes.
:-) That's what we already do for the installed tools on hudson-win.
However, I haven't figured out how to specify
MAVEN_HOME/JAVA_HOME/ANT_HOME. These are set on the global level, but
in the node configuration they are not available. Not sure what
consequences this will have. The Maven builds I've tested works as
expected.
/niklas
Re: Standard tool locations
Posted by Tim Ellison <t....@gmail.com>.
On 06/Jan/2010 11:15, Aristedes Maniatis wrote:
> On 6/01/10 9:56 PM, Tim Ellison wrote:
>> We currently have a number of tools (e.g. JDKs, Ant, Maven, etc) defined
>> globally, in the 'Manage Hudson' configuration page.
>>
>> Some are already a bit dubious, being declared as "on Ubuntu only", so
>> not really global at all. Now we have a Windows client the paths are
>> totally wrong there, so specifying a build to use 'latest' is not going
>> to work.
I should correct this, since we can override the 'latest' locations. So
we would just 'push down' the platform specific tools to the specific nodes.
>> I think the only option is to push the tool location definitions down to
>> individual nodes. That will require some duplication across the Ubuntu
>> nodes, but will allow us to specify the actual tools available on a
>> node, and the correct paths for Windows.
>>
>> WDYT? Any better option?
>
> Will that work on parameterised builds? [1]
Don't know -- I'm guessing that the parameter choices will be limited to
those that are declared in the global configurations. We can try with a
single JDK version and see if you can use it in a parameterized build.
Regards,
Tim
> And as I think I emailed before, 'maven (latest)' is already quite old,
> so any improvements here will certainly help.
>
>
>
> [1] eg. http://hudson.zones.apache.org/hudson/job/Cayenne-trunk/
>
>
Re: Standard tool locations
Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 6/01/10 9:56 PM, Tim Ellison wrote:
> We currently have a number of tools (e.g. JDKs, Ant, Maven, etc) defined
> globally, in the 'Manage Hudson' configuration page.
>
> Some are already a bit dubious, being declared as "on Ubuntu only", so
> not really global at all. Now we have a Windows client the paths are
> totally wrong there, so specifying a build to use 'latest' is not going
> to work.
>
> I think the only option is to push the tool location definitions down to
> individual nodes. That will require some duplication across the Ubuntu
> nodes, but will allow us to specify the actual tools available on a
> node, and the correct paths for Windows.
>
> WDYT? Any better option?
Will that work on parameterised builds? [1]
And as I think I emailed before, 'maven (latest)' is already quite old, so any improvements here will certainly help.
[1] eg. http://hudson.zones.apache.org/hudson/job/Cayenne-trunk/
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A