You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@apache.org by Tammo van Lessen <tv...@gmail.com> on 2010/09/01 14:14:38 UTC

Buildr/JRuby on hudson machines

Hi,

first off, thanks for the efforts for stabilizing hudson and
integrating it with LDAP etc. I think and hope that it makes the
builds much more stable.

Unfortunately the change has broken our ODE builds, simply because
we're using buildr as build system, which requires JRuby and some
buildr gems to be installed on the slaves. In the old setup, I had
access to the hudson machine, installed jruby with buildr in my home
directory and let hudson call these tools from there. Since the
change, I lost shell access, thus this approach doesn't work anymore.

So now I'm looking for solutions and have hence a couple of questions:
  - Is JRuby and/or Buildr already installed on these machines? If so,
where are they installed so that I can point hudson to that location?
  - What is the planned procedure for such custom-style builds? My
understanding of the new hudson system is that access to the build
master and slaves should be restricted. Is the approach to request
installation of JRuby/Buildr etc. via INFRA-JIRAs or would it better
to ask for shell access?

Thanks,
  Tammo

-- 
Tammo van Lessen - tvanlessen@gmail.com - http://www.taval.de

Re: Buildr/JRuby on hudson machines

Posted by Niklas Gustavsson <ni...@protocol7.com>.
On Thu, Sep 2, 2010 at 11:13 AM, Tammo van Lessen <tv...@gmail.com> wrote:
> Perhaps another question. Everytime I look at hudson, I see the hadoop
> nodes bumming around. Are they sponsored and reserved for hadoop only?

Yes, they are sponsored for the Hadoop projects (there is also a
Lucene slave). Other projects could do the same if they wish.

/niklas

Re: Buildr/JRuby on hudson machines

Posted by Tammo van Lessen <tv...@gmail.com>.

On 01.09.2010 14:31, Niklas Gustavsson wrote:
> If you installed it on the old master, they would now be available on
> "solaris2".

Awesome, that did the trick!

Perhaps another question. Everytime I look at hudson, I see the hadoop
nodes bumming around. Are they sponsored and reserved for hadoop only?

Thanks,
  Tammo

-- 
Tammo van Lessen - http://www.taval.de

Re: Buildr/JRuby on hudson machines

Posted by Antoine Toulme <an...@lunar-ocean.com>.
Just as a sidenote, Buildr will try to come up with a hudson plugin at some
point.

On Wed, Sep 1, 2010 at 05:31, Niklas Gustavsson <ni...@protocol7.com>wrote:

> On Wed, Sep 1, 2010 at 2:14 PM, Tammo van Lessen <tv...@gmail.com>
> wrote:
> > Unfortunately the change has broken our ODE builds, simply because
> > we're using buildr as build system, which requires JRuby and some
> > buildr gems to be installed on the slaves. In the old setup, I had
> > access to the hudson machine, installed jruby with buildr in my home
> > directory and let hudson call these tools from there. Since the
> > change, I lost shell access, thus this approach doesn't work anymore.
>
> Yes, there was a notification that builds bound to "master" would
> likely be broken sent to this list some time ago
> (
> http://mail-archives.apache.org/mod_mbox/www-builds/201008.mbox/%3CAANLkTimBMtKWdbi=aJR_cFBoPSmvR6nWDd-2WvRJo_Yx@mail.gmail.com%3E
> ).
>
> There was no change to shell access in the process of moving the
> master. However, if your builds ran on hudson.zones.apache.org, that
> DNS name no longer works for ssh. Instead, you need to ssh to
> 140.211.11.106. In Hudson, that machine is now called "solaris2".
> Otherwise, your previous shell accounts should be working just like
> before.
>
> > So now I'm looking for solutions and have hence a couple of questions:
> >  - Is JRuby and/or Buildr already installed on these machines? If so,
> > where are they installed so that I can point hudson to that location?
>
> If you installed it on the old master, they would now be available on
> "solaris2".
>
> >  - What is the planned procedure for such custom-style builds? My
> > understanding of the new hudson system is that access to the build
> > master and slaves should be restricted. Is the approach to request
> > installation of JRuby/Buildr etc. via INFRA-JIRAs or would it better
> > to ask for shell access?
>
> No builds will be running on the new master, and thus tools are not
> installed on that machine. For other machines, please refer to the
> instructions in the wiki:
>
> http://wiki.apache.org/general/Hudson#What_should_I_do_with_the_build_and_test_tools_that_my_project_needs.3F
>
> /niklas
>

Re: Buildr/JRuby on hudson machines

Posted by Niklas Gustavsson <ni...@protocol7.com>.
On Wed, Sep 1, 2010 at 2:14 PM, Tammo van Lessen <tv...@gmail.com> wrote:
> Unfortunately the change has broken our ODE builds, simply because
> we're using buildr as build system, which requires JRuby and some
> buildr gems to be installed on the slaves. In the old setup, I had
> access to the hudson machine, installed jruby with buildr in my home
> directory and let hudson call these tools from there. Since the
> change, I lost shell access, thus this approach doesn't work anymore.

Yes, there was a notification that builds bound to "master" would
likely be broken sent to this list some time ago
(http://mail-archives.apache.org/mod_mbox/www-builds/201008.mbox/%3CAANLkTimBMtKWdbi=aJR_cFBoPSmvR6nWDd-2WvRJo_Yx@mail.gmail.com%3E).

There was no change to shell access in the process of moving the
master. However, if your builds ran on hudson.zones.apache.org, that
DNS name no longer works for ssh. Instead, you need to ssh to
140.211.11.106. In Hudson, that machine is now called "solaris2".
Otherwise, your previous shell accounts should be working just like
before.

> So now I'm looking for solutions and have hence a couple of questions:
>  - Is JRuby and/or Buildr already installed on these machines? If so,
> where are they installed so that I can point hudson to that location?

If you installed it on the old master, they would now be available on
"solaris2".

>  - What is the planned procedure for such custom-style builds? My
> understanding of the new hudson system is that access to the build
> master and slaves should be restricted. Is the approach to request
> installation of JRuby/Buildr etc. via INFRA-JIRAs or would it better
> to ask for shell access?

No builds will be running on the new master, and thus tools are not
installed on that machine. For other machines, please refer to the
instructions in the wiki:
http://wiki.apache.org/general/Hudson#What_should_I_do_with_the_build_and_test_tools_that_my_project_needs.3F

/niklas