hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giridharan Kesavan <gkesa...@hortonworks.com>
Subject Re: Cannot access Jenkins generated test results, findbug warnings and javac warnings
Date Fri, 19 Sep 2014 17:18:06 GMT
patchprocess has always lived inside the workspace, now that we have moved
to git and the test-patch script does a git reset and git clean it removes
the patchprocess directory.

so I put a fix to create the patchprocess dir outside the workspace and
move it back into workspace soon after the build completes and the post
build steps can archive the patchprocess contents.

@steve
I have re-named the archive to patchprocess as the test-patch writes the
logs to
"        --patch-dir=${WORKSPACE}/../patchprocess \
​"​



-giri

On Fri, Sep 19, 2014 at 10:06 AM, Colin McCabe <cmccabe@alumni.cmu.edu>
wrote:

> Thanks, Steve.
>
> Should we just put everything in patchprocess/ like before?  It seems
> like renaming this directory to PreCommit-HADOOP-Build-patchprocess/
> or PreCommit-YARN-Build-patchprocess/ in various builds has created
> problems, and not made things any more clear.  What do you guys think?
>
> Colin
>
> On Fri, Sep 19, 2014 at 5:42 AM, Steve Loughran <stevel@hortonworks.com>
> wrote:
> > well, I have those permissions, but not sure where things are going right
> > now
> >
> > 1. jenkins is set to archive patchprocess/*.*
> > 1 & publish tests from trunk/**/target/surefire-reports/*.xml
> >
> >
> > I've set it to use the path
> > PreCommit-HADOOP-Build-patchprocess/*.*
> >
> > & will do some manual triggering to see if it takes
> >
> > On 19 September 2014 10:54, Wangda Tan <wheeleast@gmail.com> wrote:
> >
> >> Hi Steve,
> >> I guess this problem should be also caused by wrong URL, if anybody have
> >> admin access to Jenkins, correct URL should be easily found.
> >>
> >> Thanks,
> >> Wangda
> >>
> >> On Fri, Sep 19, 2014 at 4:32 PM, Steve Loughran <stevel@hortonworks.com
> >
> >> wrote:
> >>
> >> > Looks like HADOOP-11084 isn't complete —the patch to the build to get
> it
> >> > working post-git
> >> >
> >> > before that patch the builds weren't working at all ... now its just
> >> > getting the URLs wrong.
> >> >
> >> > If you can work out the right URLs we can fix this easily enough
> >> >
> >> > On 19 September 2014 09:24, Wangda Tan <wheeleast@gmail.com> wrote:
> >> >
> >> > > Hi Hadoop developers,
> >> > > I found recently, I cannot access Jenkins generated results, like:
> >> > >
> >> > >
> >> > >
> >> > > *Test
> >> > > results:
> >> > >
> https://builds.apache.org/job/PreCommit-YARN-Build/5039//testReport/
> >> > > <
> https://builds.apache.org/job/PreCommit-YARN-Build/5039//testReport/
> >> > > >Findbugs
> >> > > warnings:
> >> > >
> >> >
> >>
> https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/newPatchFindbugsWarningshadoop-yarn-client.html
> >> > > <
> >> > >
> >> >
> >>
> https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/newPatchFindbugsWarningshadoop-yarn-client.html
> >> > > >Javac
> >> > > warnings:
> >> > >
> >> >
> >>
> https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/diffJavacWarnings.txt
> >> > > <
> >> > >
> >> >
> >>
> https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/diffJavacWarnings.txt
> >> > > >*
> >> > >
> >> > > It will report 404 when trying to access findbugs/javac warnings
> and it
> >> > > will redirect to info page of build when trying to access test
> report.
> >> > >
> >> > > I'm not sure if there's any recent changes on Jenkins configuration.
> >> Did
> >> > > you hit the problem like this?
> >> > >
> >> > > Thanks,
> >> > > Wangda
> >> > >
> >> >
> >> > --
> >> > 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.
>

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

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message