www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Niklas Gustavsson <nik...@protocol7.com>
Subject Re: Buildr/JRuby on hudson machines
Date Wed, 01 Sep 2010 12:31:39 GMT
On Wed, Sep 1, 2010 at 2:14 PM, Tammo van Lessen <tvanlessen@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

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 In Hudson, that machine is now called "solaris2".
Otherwise, your previous shell accounts should be working just like

> 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

>  - 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:


View raw message