Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Received-SPF: pass (athena.apache.org: domain of yusaku@hortonworks.com
 designates 209.85.217.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAMCZmydwR_4=k2cbZ50R=R1s4NFDdNTXTLJc0O=KDrALmfLpoA@mail.gmail.com>
References: 
 <CA+deypHGPEY8Jd3p9-kFtg8ZC+=Dnz+A9v6guUKAhRBFXOZurA@mail.gmail.com>
	<CAGjSOKVCpaAX7-dYge+noiAS_v_nOuAFUCnmF9YO=t9E2hZXqA@mail.gmail.com>
	<CA+deypEMeui05LU51Uo3XTMu5Q1WWPSY0D3EONvc48CG41WgVg@mail.gmail.com>
	<CAGjSOKUX8TQ1FVShNFs+ujY9eEYcN=eiMG2JTn3j=ZvOK8z7Fw@mail.gmail.com>
	<0D804ED3-65F5-42D3-B793-CC1E4A470B0E@apache.org>
	<CAGjSOKXY8tCDZiU3S9TsWg-8v8vuA33w07kxmZoV0Mp7HY1uAw@mail.gmail.com>
	<CA+deypHFbub8U_F+9=bNi7nCJtXcjTgA-dPhmKUtR=_+peAikA@mail.gmail.com>
	<CAGjSOKX=yhS18PQWECeSb3f5aYZ2WfX=CRss1_oPH7nEqXR_pQ@mail.gmail.com>
	<CA+deypFDRPsJR3oErqE1UfV7dvtnrev1W0TXrecfFkBKrK_BPw@mail.gmail.com>
	<CAMCZmydwR_4=k2cbZ50R=R1s4NFDdNTXTLJc0O=KDrALmfLpoA@mail.gmail.com>
Date: Tue, 9 Sep 2014 15:01:49 -0700
Message-ID: 
 <CAGjSOKW00RVZM3veUtsN8Qh8wS0dwobRNH_qehjgJ-GkrJz7Pg@mail.gmail.com>
Subject: Re: Ambari build failure on H4 due to RAT failure
From: Yusaku Sako <yusaku@hortonworks.com>
To: "dev@ambari.apache.org" <dev@ambari.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Jun,

#189 succeeded on H4.
I left the git clean up code as is.  It should not hurt and will
prevent problems arising from unwanted artifacts in the future.
Also, I reset the label pattern to original.

Yusaku

On Tue, Sep 9, 2014 at 2:21 PM, Jun Aoki <jun.aoki.0713@gmail.com> wrote:
> For the nodejs error, it should be OK once we clean the garbage file
> described in rat.txt and revert back to the configuration since Roman
> configured it to install nodejs on the fly locally.
>
>
>
> - jun
>
> On Tue, Sep 9, 2014 at 2:18 PM, jun aoki <jun.aoki.dev@gmail.com> wrote:
>
>> Hi Yusaku, thank you for taking a look!
>> If you open the job Configuration, you should see Label Expression. You =
can
>> change it to H4.
>> Please retain the original value. (If I remember, something "ubuntu" ?)
>>
>> Also could you save
>>
>> /home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/=
target/rat.txt
>> for reference ? It will tell why it fails on H4 too.
>>
>>
>> On Tue, Sep 9, 2014 at 1:44 PM, Yusaku Sako <yusaku@hortonworks.com>
>> wrote:
>>
>> > Hi Jun,
>> >
>> > I've added the command "git clean -xdf" to be run before the mvn
>> > command to trigger build & UTs.
>> > It's currently running on H11 with this new command added:
>> > https://builds.apache.org/job/Ambari-trunk-Commit/187/
>> > I'm not sure how to verify by running it specifically on H4.
>> >
>> > Yusaku
>> >
>> > On Tue, Sep 9, 2014 at 8:25 AM, jun aoki <jun.aoki.dev@gmail.com> wrot=
e:
>> > > Yusaku/Hitesh, that's a cleaner approach. Could you please try it on=
 H4
>> > and
>> > > see if that solves?
>> > > Also could you share what errors the rat.txt contains? I don't even
>> have
>> > > access to look into its Workspace.
>> > >
>> > >
>> > > On Mon, Sep 8, 2014 at 3:37 PM, Yusaku Sako <yusaku@hortonworks.com>
>> > wrote:
>> > >
>> > >> Hitesh, yes, that's a good idea.  Maybe also add the -x option as
>> well.
>> > >>
>> > >> Yusaku
>> > >>
>> > >> On Mon, Sep 8, 2014 at 3:26 PM, Hitesh Shah <hitesh@apache.org>
>> wrote:
>> > >> > @Yusaku, if you can modify the build job itself, running =E2=80=
=9Cgit clean
>> -f
>> > >> -d=E2=80=9D at the start might be a useful step.
>> > >> >
>> > >> > =E2=80=94 Hitesh
>> > >> >
>> > >> > On Sep 8, 2014, at 11:26 AM, Yusaku Sako <yusaku@hortonworks.com>
>> > wrote:
>> > >> >
>> > >> >> Jun,
>> > >> >>
>> > >> >> Thanks.  I have yet tried to access Jenkins, so I guess your
>> > >> >> instructions will be clear to me once I do.
>> > >> >> I found this: http://wiki.apache.org/general/Jenkins
>> > >> >> So I will try it out and see.
>> > >> >>
>> > >> >> Yusaku
>> > >> >>
>> > >> >> On Mon, Sep 8, 2014 at 11:18 AM, jun aoki <jun.aoki.dev@gmail.co=
m>
>> > >> wrote:
>> > >> >>> Hi Yusaku, thank you for responding.
>> > >> >>>
>> > >> >>> It is a bit tricky but if you have access to the job
>> configuration,
>> > >> you can
>> > >> >>> set 'rm' command in Execute Shell step. Something like
>> > >> >>>
>> > >> >>> {code}
>> > >> >>> rm ${WORKSPACE}/*
>> > >> >>> {code}
>> > >> >>>
>> > >> >>> Then run the job once (make sure it runs on H4) , remove the rm
>> line
>> > >> from
>> > >> >>> the Configuration, then it should run good.
>> > >> >>>
>> > >> >>>
>> > >> >>> On Mon, Sep 8, 2014 at 11:09 AM, Yusaku Sako <
>> > yusaku@hortonworks.com>
>> > >> wrote:
>> > >> >>>
>> > >> >>>> Roman,
>> > >> >>>>
>> > >> >>>> Who gets to access these Jenkins servers?
>> > >> >>>> And for those who have the access privilege, how do we access
>> them?
>> > >> >>>>
>> > >> >>>> Yusaku
>> > >> >>>>
>> > >> >>>> On Mon, Sep 8, 2014 at 11:06 AM, jun aoki <
>> jun.aoki.dev@gmail.com>
>> > >> wrote:
>> > >> >>>>> Hi Ambari Commiters
>> > >> >>>>>
>> > >> >>>>> I submitted a ticket
>> > >> >>>>> https://issues.apache.org/jira/browse/AMBARI-7205
>> > >> >>>>>
>> > >> >>>>> It seems like there are some garbage on H4's workspace.
>> > >> >>>>> Could you please remove the garbage (or possibly the entire g=
it
>> > >> clone) to
>> > >> >>>>> clean up the RAT failure?
>> > >> >>>>> I don't have access to the Jenkins slaves.
>> > >> >>>>>
>> > >> >>>>> Thank you!
>> > >> >>>>> --
>> > >> >>>>> -jun
>> > >> >>>>
>> > >> >>>> --
>> > >> >>>> CONFIDENTIALITY NOTICE
>> > >> >>>> NOTICE: This message is intended for the use of the individual=
 or
>> > >> entity to
>> > >> >>>> which it is addressed and may contain information that is
>> > >> confidential,
>> > >> >>>> privileged and exempt from disclosure under applicable law. If
>> the
>> > >> reader
>> > >> >>>> of this message is not the intended recipient, you are hereby
>> > >> notified that
>> > >> >>>> any printing, copying, dissemination, distribution, disclosure=
 or
>> > >> >>>> forwarding of this communication is strictly prohibited. If yo=
u
>> > have
>> > >> >>>> received this communication in error, please contact the sende=
r
>> > >> immediately
>> > >> >>>> and delete it from your system. Thank You.
>> > >> >>>>
>> > >> >>>
>> > >> >>>
>> > >> >>>
>> > >> >>> --
>> > >> >>> -jun
>> > >> >>
>> > >> >> --
>> > >> >> CONFIDENTIALITY NOTICE
>> > >> >> NOTICE: This message is intended for the use of the individual o=
r
>> > >> entity to
>> > >> >> which it is addressed and may contain information that is
>> > confidential,
>> > >> >> privileged and exempt from disclosure under applicable law. If t=
he
>> > >> reader
>> > >> >> of this message is not the intended recipient, you are hereby
>> > notified
>> > >> that
>> > >> >> any printing, copying, dissemination, distribution, disclosure o=
r
>> > >> >> forwarding of this communication is strictly prohibited. If you
>> have
>> > >> >> received this communication in error, please contact the sender
>> > >> immediately
>> > >> >> and delete it from your system. Thank You.
>> > >> >
>> > >>
>> > >> --
>> > >> CONFIDENTIALITY NOTICE
>> > >> NOTICE: This message is intended for the use of the individual or
>> > entity to
>> > >> which it is addressed and may contain information that is
>> confidential,
>> > >> privileged and exempt from disclosure under applicable law. If the
>> > reader
>> > >> of this message is not the intended recipient, you are hereby notif=
ied
>> > that
>> > >> any printing, copying, dissemination, distribution, disclosure or
>> > >> forwarding of this communication is strictly prohibited. If you hav=
e
>> > >> received this communication in error, please contact the sender
>> > immediately
>> > >> and delete it from your system. Thank You.
>> > >>
>> > >
>> > >
>> > >
>> > > --
>> > > -jun
>> >
>> > --
>> > CONFIDENTIALITY NOTICE
>> > NOTICE: This message is intended for the use of the individual or enti=
ty
>> to
>> > which it is addressed and may contain information that is confidential=
,
>> > privileged and exempt from disclosure under applicable law. If the rea=
der
>> > of this message is not the intended recipient, you are hereby notified
>> that
>> > any printing, copying, dissemination, distribution, disclosure or
>> > forwarding of this communication is strictly prohibited. If you have
>> > received this communication in error, please contact the sender
>> immediately
>> > and delete it from your system. Thank You.
>> >
>>
>>
>>
>> --
>> -jun
>>

--=20
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to=
=20
which it is addressed and may contain information that is confidential,=20
privileged and exempt from disclosure under applicable law. If the reader=
=20
of this message is not the intended recipient, you are hereby notified that=
=20
any printing, copying, dissemination, distribution, disclosure or=20
forwarding of this communication is strictly prohibited. If you have=20
received this communication in error, please contact the sender immediately=
=20
and delete it from your system. Thank You.