You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@apache.org by Giridharan Kesavan <gk...@yahoo-inc.com> on 2010/03/24 05:09:03 UTC

Moving builds off hudson Master

All the hadoop patch admin jobs which requires 1 min time of the hudson master is stuck for hours b'coz of
http://hudson.zones.apache.org/hudson/job/Wink-Trunk-JDK1.6/262

Can we work on moving the build off hudson master. (Build that doesn't require to run on master but Solaris)
I can spend sometime

Thanks,
giri

Re: Moving builds off hudson Master

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Wed, Mar 24, 2010 at 11:20 AM, Jukka Zitting <ju...@gmail.com> wrote:
> On Wed, Mar 24, 2010 at 5:09 AM, Giridharan  Kesavan
> <gk...@yahoo-inc.com> wrote:
>> Can we work on moving the build off hudson master.
>
> I think we should do that, ideally reserving the master to tied jobs
> only.

I have changed Hudson configuration so that only tied jobs are now run
on the master. Untied jobs get distributed over minerva, vesta and
hudson-solaris.

BR,

Jukka Zitting

AW: Moving builds off hudson Master

Posted by Ja...@rzf.fin-nrw.de.
Thanks Nicolas,
I hadnt enough time to follow that deeply on builds@

Jan 

>-----Ursprüngliche Nachricht-----
>Von: Nicolas Lalevée [mailto:nicolas.lalevee@hibnet.org] 
>Gesendet: Montag, 29. März 2010 20:46
>An: builds@apache.org
>Cc: Ant Developers List
>Betreff: Re: Moving builds off hudson Master
>
>
>Le 24 mars 2010 à 10:20, Jukka Zitting a écrit :
>
>> Hi,
>> 
>> On Wed, Mar 24, 2010 at 5:09 AM, Giridharan  Kesavan
>> <gk...@yahoo-inc.com> wrote:
>>> All the hadoop patch admin jobs which requires 1 min time 
>of the hudson master is stuck for hours b'coz of
>>> http://hudson.zones.apache.org/hudson/job/Wink-Trunk-JDK1.6/262
>> 
>> I just restored the second executor on Hudson master to avoid such
>> bottlenecks for now.
>> 
>>> Can we work on moving the build off hudson master.
>> 
>> I think we should do that, ideally reserving the master to tied jobs
>> only. The current list of tied jobs on master is:
>> 
>>    Ant_JDK_1.4
>>    Ant_JDK_1.4_Test
>
>These two jobs were tied to the master to get a JDK 1.4.
>Now there is another Solaris machine, I tied them to the Solaris group.
>
>cheers,
>Nicolas
>
>
>>    Hadoop-Patch-Admin
>>    Hdfs-Patch-Admin
>>    hupa-trunk
>>    imap-trunk-m2
>>    Jakarta BSF 3
>>    jsieve-trunk
>>    mailet-api-trunk
>>    mailet-base-trunk
>>    mailet-standard-trunk
>>    Mapreduce-Patch-Admin
>>    ODE-1.x
>>    ODE-trunk
>>    ODE-trunk-jdk6
>>    Pig-Patch-Admin
>>    SpamAssassin-trunk
>>    struts-annotations
>>    struts-master
>>    struts2
>>    xwork2
>>    Zookeeper-Patch-Admin
>> 
>> Which ones of these really must be run on the master?
>> 
>> BR,
>> 
>> Jukka Zitting
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>For additional commands, e-mail: dev-help@ant.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Re: Moving builds off hudson Master

Posted by Nicolas Lalevée <ni...@hibnet.org>.
Le 24 mars 2010 à 10:20, Jukka Zitting a écrit :

> Hi,
> 
> On Wed, Mar 24, 2010 at 5:09 AM, Giridharan  Kesavan
> <gk...@yahoo-inc.com> wrote:
>> All the hadoop patch admin jobs which requires 1 min time of the hudson master is stuck for hours b'coz of
>> http://hudson.zones.apache.org/hudson/job/Wink-Trunk-JDK1.6/262
> 
> I just restored the second executor on Hudson master to avoid such
> bottlenecks for now.
> 
>> Can we work on moving the build off hudson master.
> 
> I think we should do that, ideally reserving the master to tied jobs
> only. The current list of tied jobs on master is:
> 
>    Ant_JDK_1.4
>    Ant_JDK_1.4_Test

These two jobs were tied to the master to get a JDK 1.4.
Now there is another Solaris machine, I tied them to the Solaris group.

cheers,
Nicolas


>    Hadoop-Patch-Admin
>    Hdfs-Patch-Admin
>    hupa-trunk
>    imap-trunk-m2
>    Jakarta BSF 3
>    jsieve-trunk
>    mailet-api-trunk
>    mailet-base-trunk
>    mailet-standard-trunk
>    Mapreduce-Patch-Admin
>    ODE-1.x
>    ODE-trunk
>    ODE-trunk-jdk6
>    Pig-Patch-Admin
>    SpamAssassin-trunk
>    struts-annotations
>    struts-master
>    struts2
>    xwork2
>    Zookeeper-Patch-Admin
> 
> Which ones of these really must be run on the master?
> 
> BR,
> 
> Jukka Zitting


Re: Moving builds off hudson Master

Posted by Nicolas Lalevée <ni...@hibnet.org>.
Le 24 mars 2010 à 10:20, Jukka Zitting a écrit :

> Hi,
> 
> On Wed, Mar 24, 2010 at 5:09 AM, Giridharan  Kesavan
> <gk...@yahoo-inc.com> wrote:
>> All the hadoop patch admin jobs which requires 1 min time of the hudson master is stuck for hours b'coz of
>> http://hudson.zones.apache.org/hudson/job/Wink-Trunk-JDK1.6/262
> 
> I just restored the second executor on Hudson master to avoid such
> bottlenecks for now.
> 
>> Can we work on moving the build off hudson master.
> 
> I think we should do that, ideally reserving the master to tied jobs
> only. The current list of tied jobs on master is:
> 
>    Ant_JDK_1.4
>    Ant_JDK_1.4_Test

These two jobs were tied to the master to get a JDK 1.4.
Now there is another Solaris machine, I tied them to the Solaris group.

cheers,
Nicolas


>    Hadoop-Patch-Admin
>    Hdfs-Patch-Admin
>    hupa-trunk
>    imap-trunk-m2
>    Jakarta BSF 3
>    jsieve-trunk
>    mailet-api-trunk
>    mailet-base-trunk
>    mailet-standard-trunk
>    Mapreduce-Patch-Admin
>    ODE-1.x
>    ODE-trunk
>    ODE-trunk-jdk6
>    Pig-Patch-Admin
>    SpamAssassin-trunk
>    struts-annotations
>    struts-master
>    struts2
>    xwork2
>    Zookeeper-Patch-Admin
> 
> Which ones of these really must be run on the master?
> 
> BR,
> 
> Jukka Zitting


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Re: Moving builds off hudson Master

Posted by sebb <se...@gmail.com>.
On 24/03/2010, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
>
>  On Wed, Mar 24, 2010 at 4:31 PM, sebb <se...@gmail.com> wrote:
>  > I now get:
>  >
>  > [exec] Error: JAVA_HOME is not defined correctly.
>  > [exec]   We cannot execute /home/hudson/tools/java/latest/bin/java/bin/java
>  >
>  > I suspect it should be
>  >
>  > JAVA_HOME=/home/hudson/tools/java/latest
>
>
> Oh, obviously. Sorry for the confusion.
>
>
>  > Feel free to trigger the Jakarta BSF build if you want to test any
>  > changes (it's not currently built automatically).
>
>
> OK. I fixed the JAVA_HOME path and rebuilt the project. It now finds
>  Maven, but fails due to spaces in the workspace path (${basedir}
>  expands to "/home/hudson/hudson-slave/workspace/Jakarta BSF
>  3/bsf3.x").
>
>  BR,

OK, thanks, I've renamed the project (it could be tricky to quote the
spaces portably).

>
>  Jukka Zitting
>

Re: Moving builds off hudson Master

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Wed, Mar 24, 2010 at 4:31 PM, sebb <se...@gmail.com> wrote:
> I now get:
>
> [exec] Error: JAVA_HOME is not defined correctly.
> [exec]   We cannot execute /home/hudson/tools/java/latest/bin/java/bin/java
>
> I suspect it should be
>
> JAVA_HOME=/home/hudson/tools/java/latest

Oh, obviously. Sorry for the confusion.

> Feel free to trigger the Jakarta BSF build if you want to test any
> changes (it's not currently built automatically).

OK. I fixed the JAVA_HOME path and rebuilt the project. It now finds
Maven, but fails due to spaces in the workspace path (${basedir}
expands to "/home/hudson/hudson-slave/workspace/Jakarta BSF
3/bsf3.x").

BR,

Jukka Zitting

Re: Moving builds off hudson Master

Posted by sebb <se...@gmail.com>.
On 24/03/2010, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
>
>  On Wed, Mar 24, 2010 at 12:48 PM, sebb <se...@gmail.com> wrote:
>  > Just updated Jakarta BSF3, and triggered it.
>  >
>  > The build failed on vesta, because it uses an Ant file that assumes
>  > "mvn" will be available in "mvn.path", currently set to
>  > $HOME/tools/maven/latest2/bin/.
>
>
> That's probably because JAVA_HOME is not set and there is no java on
>  the default PATH.
>
>  I just added JAVA_HOME=/home/hudson/tools/java/latest/bin/java to the
>  default environment of the slave process.

I now get:

[exec] Error: JAVA_HOME is not defined correctly.
[exec]   We cannot execute /home/hudson/tools/java/latest/bin/java/bin/java

I suspect it should be

JAVA_HOME=/home/hudson/tools/java/latest

Feel free to trigger the Jakarta BSF build if you want to test any
changes (it's not currently built automatically).

>  BR,
>
>
>  Jukka Zitting
>

Re: Moving builds off hudson Master

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Wed, Mar 24, 2010 at 12:48 PM, sebb <se...@gmail.com> wrote:
> Just updated Jakarta BSF3, and triggered it.
>
> The build failed on vesta, because it uses an Ant file that assumes
> "mvn" will be available in "mvn.path", currently set to
> $HOME/tools/maven/latest2/bin/.

That's probably because JAVA_HOME is not set and there is no java on
the default PATH.

I just added JAVA_HOME=/home/hudson/tools/java/latest/bin/java to the
default environment of the slave process.

BR,

Jukka Zitting

Re: Moving builds off hudson Master

Posted by sebb <se...@gmail.com>.
On 24/03/2010, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
>
>  On Wed, Mar 24, 2010 at 11:23 AM, Justin Mason <jm...@jmason.org> wrote:
>  > do we need to do any dependency installation for the java projects?
>
>
> Probably not. I've copied all the build tools in ~hudson/tools from
>  the Hudson master, so I think all the Java builds should be covered
>  unless they depend on some custom tools installed in personal home
>  directories.

Just updated Jakarta BSF3, and triggered it.

The build failed on vesta, because it uses an Ant file that assumes
"mvn" will be available in "mvn.path", currently set to
$HOME/tools/maven/latest2/bin/.

Is there a portable way of accessing mvn from an Ant build?

>  BR,
>
>
>  Jukka Zitting
>

Re: Moving builds off hudson Master

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Wed, Mar 24, 2010 at 11:23 AM, Justin Mason <jm...@jmason.org> wrote:
> do we need to do any dependency installation for the java projects?

Probably not. I've copied all the build tools in ~hudson/tools from
the Hudson master, so I think all the Java builds should be covered
unless they depend on some custom tools installed in personal home
directories.

BR,

Jukka Zitting

Re: Moving builds off hudson Master

Posted by Justin Mason <jm...@jmason.org>.
SpamAssassin-trunk will be moving as soon as some pkgadd dependencies
are installed on the hudson-solaris zone.

do we need to do any dependency installation for the java projects?

--j.

On Wed, Mar 24, 2010 at 09:20, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
> On Wed, Mar 24, 2010 at 5:09 AM, Giridharan  Kesavan
> <gk...@yahoo-inc.com> wrote:
>> All the hadoop patch admin jobs which requires 1 min time of the hudson master is stuck for hours b'coz of
>> http://hudson.zones.apache.org/hudson/job/Wink-Trunk-JDK1.6/262
>
> I just restored the second executor on Hudson master to avoid such
> bottlenecks for now.
>
>> Can we work on moving the build off hudson master.
>
> I think we should do that, ideally reserving the master to tied jobs
> only. The current list of tied jobs on master is:
>
>    Ant_JDK_1.4
>    Ant_JDK_1.4_Test
>    Hadoop-Patch-Admin
>    Hdfs-Patch-Admin
>    hupa-trunk
>    imap-trunk-m2
>    Jakarta BSF 3
>    jsieve-trunk
>    mailet-api-trunk
>    mailet-base-trunk
>    mailet-standard-trunk
>    Mapreduce-Patch-Admin
>    ODE-1.x
>    ODE-trunk
>    ODE-trunk-jdk6
>    Pig-Patch-Admin
>    SpamAssassin-trunk
>    struts-annotations
>    struts-master
>    struts2
>    xwork2
>    Zookeeper-Patch-Admin
>
> Which ones of these really must be run on the master?
>
> BR,
>
> Jukka Zitting
>
>



-- 
--j.

Re: Moving builds off hudson Master

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Wed, Mar 24, 2010 at 5:09 AM, Giridharan  Kesavan
<gk...@yahoo-inc.com> wrote:
> All the hadoop patch admin jobs which requires 1 min time of the hudson master is stuck for hours b'coz of
> http://hudson.zones.apache.org/hudson/job/Wink-Trunk-JDK1.6/262

I just restored the second executor on Hudson master to avoid such
bottlenecks for now.

> Can we work on moving the build off hudson master.

I think we should do that, ideally reserving the master to tied jobs
only. The current list of tied jobs on master is:

    Ant_JDK_1.4
    Ant_JDK_1.4_Test
    Hadoop-Patch-Admin
    Hdfs-Patch-Admin
    hupa-trunk
    imap-trunk-m2
    Jakarta BSF 3
    jsieve-trunk
    mailet-api-trunk
    mailet-base-trunk
    mailet-standard-trunk
    Mapreduce-Patch-Admin
    ODE-1.x
    ODE-trunk
    ODE-trunk-jdk6
    Pig-Patch-Admin
    SpamAssassin-trunk
    struts-annotations
    struts-master
    struts2
    xwork2
    Zookeeper-Patch-Admin

Which ones of these really must be run on the master?

BR,

Jukka Zitting