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 <yus...@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....@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 git 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 you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
--
-jun
