Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hadoop >> mail # dev >> Hadoop build slaves software


Copy link to this message
-
Re: Hadoop build slaves software
Turns out I had to both kill -9 it and chmod 000
/home/jenkins/jenkins-slave in order to keep it from auto-respawning.
Just a note so that once the toolchain is fixed, someone knows to
re-chmod back to 755.

-Todd

On Fri, Jan 4, 2013 at 2:11 PM, Todd Lipcon <[EMAIL PROTECTED]> wrote:
> I'm going to kill -9 the jenkins slave on hadoop8 for now cuz it's
> causing havoc on the precommit builds. I can't see another way to
> administratively disable it from the Jenkins interface.
>
> Rajiv, Giri -- mind if I build/install protoc into /usr/local to match
> the other slaves? We can continue the conversation about provisioning
> after, but would like to unblock the builds in the meantime.
>
> As for CentOS vs Ubuntu, I've got no preference. RHEL6 is probably
> preferable since it's a more common install platform, anyway. But,
> we'll still need to have a custom toolchain for things like protoc 2.4
> which don't have new enough versions in the package repos.
>
> -Todd
>
> On Fri, Jan 4, 2013 at 2:03 PM, Colin McCabe <[EMAIL PROTECTED]> wrote:
>> In addition to protoc, can someone please also install a 32-bit C++ compiler?
>>
>> The builds are all failing on this machine because of that.
>>
>> regards,
>> Colin
>>
>>
>> On Fri, Jan 4, 2013 at 11:37 AM, Giridharan Kesavan
>> <[EMAIL PROTECTED]> wrote:
>>> When I configured the other machines I used the source to compile and
>>> install the protoc, as the 2.4.1 wasn't available in the ubuntu repo.
>>>
>>> BTW installed 2.4.1 on asf008.
>>> gkesavan@asf008:~$ protoc --version
>>> libprotoc 2.4.1
>>>
>>>
>>> -Giri
>>>
>>>
>>> On Thu, Jan 3, 2013 at 11:24 PM, Todd Lipcon <[EMAIL PROTECTED]> wrote:
>>>
>>>> Hey folks,
>>>>
>>>> It looks like hadoop8 has recently come back online as a build slave,
>>>> but is failing all the builds because it has an ancient version of
>>>> protobuf (2.2.0):
>>>> todd@asf008:~$ protoc  --version
>>>> libprotoc 2.2.0
>>>>
>>>> In contrast, other slaves have 2.4.1:
>>>> todd@asf001:~$ protoc --version
>>>> libprotoc 2.4.1
>>>>
>>>> asf001 has the newer protoc in /usr/local/bin but asf008 does not.
>>>> Does anyone know how software is meant to be deployed on these build
>>>> slaves? I'm happy to download and install protobuf 2.4.1 into
>>>> /usr/local on asf008 if manual installation is the name of the game,
>>>> but it seems like we should be doing something a little more
>>>> reproducible than one-off builds by rando developers to manage our
>>>> toolchain on the Jenkins slaves.
>>>>
>>>> -Todd
>>>> --
>>>> Todd Lipcon
>>>> Software Engineer, Cloudera
>>>>
>
>
>
> --
> Todd Lipcon
> Software Engineer, Cloudera

--
Todd Lipcon
Software Engineer, Cloudera