Re: Ambari build failure on H4 due to RAT failure
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 yus...@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 hit...@apache.org wrote:
@Yusaku, if you can modify the build job itself, running “git clean -f
-d” at the start might be a useful step.
— Hitesh
On Sep 8, 2014, at 11:26 AM, Yusaku Sako yus...@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@gmail.com
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 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
--
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.
--
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
Re: Ambari build failure on H4 due to RAT failure
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@gmail.com wrote:
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 yus...@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 hit...@apache.org wrote:
@Yusaku, if you can modify the build job itself, running “git clean -f
-d” at the start might be a useful step.
— Hitesh
On Sep 8, 2014, at 11:26 AM, Yusaku Sako yus...@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@gmail.com
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 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
--
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.
--
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
--
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.
Re: Ambari build failure on H4 due to RAT failure
I think #187 failed because the new git clean now is deleting the
local nodejs installation (didn't really pay attention to the nodejs
local install hack until the failure occurred).
Yusaku
On Tue, Sep 9, 2014 at 1:44 PM, Yusaku Sako yus...@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@gmail.com wrote:
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 yus...@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 hit...@apache.org wrote:
@Yusaku, if you can modify the build job itself, running “git clean -f
-d” at the start might be a useful step.
— Hitesh
On Sep 8, 2014, at 11:26 AM, Yusaku Sako yus...@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@gmail.com
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 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
--
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.
--
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
--
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.
Re: Ambari build failure on H4 due to RAT failure
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 yus...@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@gmail.com wrote:
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 yus...@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 hit...@apache.org wrote:
@Yusaku, if you can modify the build job itself, running “git clean -f
-d” at the start might be a useful step.
— Hitesh
On Sep 8, 2014, at 11:26 AM, Yusaku Sako yus...@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@gmail.com
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
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
--
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.
--
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
--
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
Re: Ambari build failure on H4 due to RAT failure
Thanks for the tip, Jun!
I made more changes so that git clean -xdf runs before the local
nodejs installation.
Will let you know once we get a successful run H4.
Yusaku
On Tue, Sep 9, 2014 at 2:18 PM, jun aoki jun.aoki@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 yus...@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@gmail.com wrote:
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 yus...@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 hit...@apache.org wrote:
@Yusaku, if you can modify the build job itself, running “git clean -f
-d” at the start might be a useful step.
— Hitesh
On Sep 8, 2014, at 11:26 AM, Yusaku Sako yus...@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@gmail.com
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
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
--
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.
--
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
--
CONFIDENTIALITY NOTICE
NOTICE: This message is
Re: Ambari build failure on H4 due to RAT failure
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.0...@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@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 yus...@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@gmail.com wrote:
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 yus...@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 hit...@apache.org
wrote:
@Yusaku, if you can modify the build job itself, running “git clean
-f
-d” at the start might be a useful step.
— Hitesh
On Sep 8, 2014, at 11:26 AM, Yusaku Sako yus...@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@gmail.com
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
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
--
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.
--
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
Re: Ambari build failure on H4 due to RAT failure
Yusaku,
I confirmed that the build started working on H4
https://builds.apache.org/job/Ambari-trunk-Commit/189/consoleFull
Thank you so much for taking up the errands and cleaned up the environment!
I'm working on creating a test-patch job for Ambari
https://issues.apache.org/jira/browse/AMBARI-7209 and will keep you and the
community updated.
Thank you,
jun
On Tue, Sep 9, 2014 at 3:01 PM, Yusaku Sako yus...@hortonworks.com wrote:
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.0...@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@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 yus...@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@gmail.com
wrote:
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 yus...@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 hit...@apache.org
wrote:
@Yusaku, if you can modify the build job itself, running “git
clean
-f
-d” at the start might be a useful step.
— Hitesh
On Sep 8, 2014, at 11:26 AM, Yusaku Sako yus...@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@gmail.com
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
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
--
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
Re: Ambari build failure on H4 due to RAT failure
You are welcome, and thank _you_ for doing the heavy lifting :)
It would be awesome if we can port over the test patch job from Hadoop!
Yusaku
On Tue, Sep 9, 2014 at 4:25 PM, jun aoki jun.aoki@gmail.com wrote:
Yusaku,
I confirmed that the build started working on H4
https://builds.apache.org/job/Ambari-trunk-Commit/189/consoleFull
Thank you so much for taking up the errands and cleaned up the environment!
I'm working on creating a test-patch job for Ambari
https://issues.apache.org/jira/browse/AMBARI-7209 and will keep you and the
community updated.
Thank you,
jun
On Tue, Sep 9, 2014 at 3:01 PM, Yusaku Sako yus...@hortonworks.com wrote:
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.0...@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@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 yus...@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@gmail.com
wrote:
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 yus...@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 hit...@apache.org
wrote:
@Yusaku, if you can modify the build job itself, running “git
clean
-f
-d” at the start might be a useful step.
— Hitesh
On Sep 8, 2014, at 11:26 AM, Yusaku Sako yus...@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@gmail.com
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
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
--
Re: Ambari build failure on H4 due to RAT failure
On Tue, Sep 9, 2014 at 2:21 PM, Jun Aoki jun.aoki.0...@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. Speaking of which -- I think we can make Ambari build even more flexible if we make that part of the Maven routine. For now, though, the build on ASF Jenkins is doing fine -- I'll file extra JIRAs soon though. Thanks, Roman.
Re: Ambari build failure on H4 due to RAT failure
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.
Re: Ambari build failure on H4 due to RAT failure
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
Re: Ambari build failure on H4 due to RAT failure
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@gmail.com 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 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
--
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.
Re: Ambari build failure on H4 due to RAT failure
@Yusaku, if you can modify the build job itself, running “git clean -f -d” at
the start might be a useful step.
— Hitesh
On Sep 8, 2014, at 11:26 AM, Yusaku Sako yus...@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@gmail.com 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 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
--
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.
Re: Ambari build failure on H4 due to RAT failure
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 hit...@apache.org wrote:
@Yusaku, if you can modify the build job itself, running “git clean -f -d” at
the start might be a useful step.
— Hitesh
On Sep 8, 2014, at 11:26 AM, Yusaku Sako yus...@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@gmail.com 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 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
--
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.
--
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.
