Billie found out that Hadoop-Common-2-Commit should be the build that publishes artifacts.
Thanks Billie. On Wed, Sep 24, 2014 at 4:20 PM, Ted Yu <yuzhih...@gmail.com> wrote: > FYI > > I made some changes to: > https://builds.apache.org/view/All/job/Hadoop-branch2 > > because it until this morning was using svn to build. > > Would 2.6.0-SNAPSHOT maven artifacts be updated after the build ? > > Cheers > > > On Mon, Sep 15, 2014 at 11:14 AM, Todd Lipcon <t...@cloudera.com> wrote: > >> Hey all, >> >> For those of you who like to see the entire history of a file going back >> to >> 2006, I found I had to add a new graft to .git/info/grafts: >> >> # Project un-split in new writable git repo >> a196766ea07775f18ded69bd9e8d239f8cfd3ccc >> 928d485e2743115fe37f9d123ce9a635c5afb91a >> cd66945f62635f589ff93468e94c0039684a8b6d >> 77f628ff5925c25ba2ee4ce14590789eb2e7b85b >> >> FWIW, my entire file now contains: >> >> # Project split >> 5128a9a453d64bfe1ed978cf9ffed27985eeef36 >> 6c16dc8cf2b28818c852e95302920a278d07ad0c >> 6a3ac690e493c7da45bbf2ae2054768c427fd0e1 >> 6c16dc8cf2b28818c852e95302920a278d07ad0c >> 546d96754ffee3142bcbbf4563c624c053d0ed0d >> 6c16dc8cf2b28818c852e95302920a278d07ad0c >> 4e569e629a98a4ef5326e5d25a84c7d57b5a8f7a >> c78078dd2283e2890018ff0e87d751c86163f99f >> >> # Project un-split in new writable git repo >> a196766ea07775f18ded69bd9e8d239f8cfd3ccc >> 928d485e2743115fe37f9d123ce9a635c5afb91a >> cd66945f62635f589ff93468e94c0039684a8b6d >> 77f628ff5925c25ba2ee4ce14590789eb2e7b85b >> >> which seems to do a good job for me (not sure if the first few lines are >> necessary anymore in the latest world) >> >> -Todd >> >> >> >> On Fri, Sep 12, 2014 at 11:31 AM, Colin McCabe <cmcc...@alumni.cmu.edu> >> wrote: >> >> > It's an issue with test-patch.sh. See >> > https://issues.apache.org/jira/browse/HADOOP-11084 >> > >> > best, >> > Colin >> > >> > On Mon, Sep 8, 2014 at 3:38 PM, Andrew Wang <andrew.w...@cloudera.com> >> > wrote: >> > > We're still not seeing findbugs results show up on precommit runs. I >> see >> > > that we're archiving "../patchprocess/*", and Ted thinks that since >> it's >> > > not in $WORKSPACE it's not getting picked up. Can we get confirmation >> of >> > > this issue? If so, we could just add "patchprocess" to the toplevel >> > > .gitignore. >> > > >> > > On Thu, Sep 4, 2014 at 8:54 AM, Sangjin Lee <sjl...@gmail.com> wrote: >> > > >> > >> That's good to know. Thanks. >> > >> >> > >> >> > >> On Wed, Sep 3, 2014 at 11:15 PM, Vinayakumar B < >> vinayakum...@apache.org >> > > >> > >> wrote: >> > >> >> > >> > I think its still pointing to old svn repository which is just read >> > only >> > >> > now. >> > >> > >> > >> > You can use latest mirror: >> > >> > https://github.com/apache/hadoop >> > >> > >> > >> > Regards, >> > >> > Vinay >> > >> > On Sep 4, 2014 11:37 AM, "Sangjin Lee" <sjl...@gmail.com> wrote: >> > >> > >> > >> > > It seems like the github mirror at >> > >> > https://github.com/apache/hadoop-common >> > >> > > has stopped getting updates as of 8/22. Could this mirror have >> been >> > >> > broken >> > >> > > by the git transition? >> > >> > > >> > >> > > Thanks, >> > >> > > Sangjin >> > >> > > >> > >> > > >> > >> > > On Fri, Aug 29, 2014 at 11:51 AM, Ted Yu <yuzhih...@gmail.com> >> > wrote: >> > >> > > >> > >> > > > From >> https://builds.apache.org/job/Hadoop-hdfs-trunk/1854/console >> > : >> > >> > > > >> > >> > > > ERROR: No artifacts found that match the file pattern >> > >> > > > "trunk/hadoop-hdfs-project/*/target/*.tar.gz". Configuration >> > >> > > > error?ERROR < >> http://stacktrace.jenkins-ci.org/search?query=ERROR >> > >: >> > >> > > > ?trunk/hadoop-hdfs-project/*/target/*.tar.gz? doesn?t match >> > anything, >> > >> > > > but ?hadoop-hdfs-project/*/target/*.tar.gz? does. Perhaps >> that?s >> > what >> > >> > > > you mean? >> > >> > > > >> > >> > > > >> > >> > > > I corrected the path to hdfs tar ball. >> > >> > > > >> > >> > > > >> > >> > > > FYI >> > >> > > > >> > >> > > > >> > >> > > > >> > >> > > > On Fri, Aug 29, 2014 at 8:48 AM, Alejandro Abdelnur < >> > >> t...@cloudera.com >> > >> > > >> > >> > > > wrote: >> > >> > > > >> > >> > > > > it seems we missed updating the HADOOP precommit job to use >> > Git, it >> > >> > was >> > >> > > > > still using SVN. I've just updated it. >> > >> > > > > >> > >> > > > > thx >> > >> > > > > >> > >> > > > > >> > >> > > > > On Thu, Aug 28, 2014 at 9:26 PM, Ted Yu <yuzhih...@gmail.com >> > >> > >> wrote: >> > >> > > > > >> > >> > > > > > Currently patchprocess/ (contents shown below) is one level >> > >> higher >> > >> > > than >> > >> > > > > > ${WORKSPACE} >> > >> > > > > > >> > >> > > > > > diffJavadocWarnings.txt >> > >> > > > newPatchFindbugsWarningshadoop-hdfs.html >> > >> > > > > > patchFindBugsOutputhadoop-hdfs.txt >> > >> patchReleaseAuditOutput.txt >> > >> > > > > > trunkJavadocWarnings.txt >> > >> > > > > > filteredPatchJavacWarnings.txt >> > >> > > newPatchFindbugsWarningshadoop-hdfs.xml >> > >> > > > > > patchFindbugsWarningshadoop-hdfs.xml >> > >> patchReleaseAuditWarnings.txt >> > >> > > > > > filteredTrunkJavacWarnings.txt patch >> > >> > > > > > patchJavacWarnings.txt >> testrun_hadoop-hdfs.txt >> > >> > > > > > jira patchEclipseOutput.txt >> > >> > > > > > patchJavadocWarnings.txt >> trunkJavacWarnings.txt >> > >> > > > > > >> > >> > > > > > Under Files to archive input box of >> > >> > PreCommit-HDFS-Build/configure, I >> > >> > > > > saw: >> > >> > > > > > >> > >> > > > > > '../patchprocess/*' doesn't match anything, but '*' does. >> > Perhaps >> > >> > > > that's >> > >> > > > > > what you mean? >> > >> > > > > > >> > >> > > > > > I guess once patchprocess is moved back under >> ${WORKSPACE}, a >> > lot >> > >> > of >> > >> > > > > things >> > >> > > > > > would be back to normal. >> > >> > > > > > >> > >> > > > > > Cheers >> > >> > > > > > >> > >> > > > > > On Thu, Aug 28, 2014 at 9:16 PM, Alejandro Abdelnur < >> > >> > > t...@cloudera.com >> > >> > > > > >> > >> > > > > > wrote: >> > >> > > > > > >> > >> > > > > > > i'm also seeing broken links for javadocs warnings. >> > >> > > > > > > >> > >> > > > > > > Alejandro >> > >> > > > > > > (phone typing) >> > >> > > > > > > >> > >> > > > > > > > On Aug 28, 2014, at 20:00, Andrew Wang < >> > >> > andrew.w...@cloudera.com >> > >> > > > >> > >> > > > > > wrote: >> > >> > > > > > > > >> > >> > > > > > > > I noticed that the JUnit test results aren't getting >> > picked >> > >> up >> > >> > > > > > anymore. I >> > >> > > > > > > > suspect we just need to update the path to the surefire >> > >> output, >> > >> > > but >> > >> > > > > > based >> > >> > > > > > > > on a quick examination I'm not sure what that is. >> > >> > > > > > > > >> > >> > > > > > > > Does someone mind taking another look? >> > >> > > > > > > > >> > >> > > > > > > > >> > >> > > > > > > > On Thu, Aug 28, 2014 at 4:21 PM, Karthik Kambatla < >> > >> > > > > ka...@cloudera.com> >> > >> > > > > > > > wrote: >> > >> > > > > > > > >> > >> > > > > > > >> Thanks Giri and Ted for fixing the builds. >> > >> > > > > > > >> >> > >> > > > > > > >> >> > >> > > > > > > >>> On Thu, Aug 28, 2014 at 9:49 AM, Ted Yu < >> > >> yuzhih...@gmail.com >> > >> > > >> > >> > > > > wrote: >> > >> > > > > > > >>> >> > >> > > > > > > >>> Charles: >> > >> > > > > > > >>> QA build is running for your JIRA: >> > >> > > > > > > >>> >> > >> > > > > >> > >> https://builds.apache.org/job/PreCommit-hdfs-Build/7828/parameters/ >> > >> > > > > > > >>> >> > >> > > > > > > >>> Cheers >> > >> > > > > > > >>> >> > >> > > > > > > >>> >> > >> > > > > > > >>>> On Thu, Aug 28, 2014 at 9:41 AM, Charles Lamb < >> > >> > > > cl...@cloudera.com >> > >> > > > > > >> > >> > > > > > > >>> wrote: >> > >> > > > > > > >>> >> > >> > > > > > > >>>>> On 8/28/2014 12:07 PM, Giridharan Kesavan wrote: >> > >> > > > > > > >>>>> >> > >> > > > > > > >>>>> Fixed all the 3 pre-commit buids. test-patch's git >> > reset >> > >> > > --hard >> > >> > > > > is >> > >> > > > > > > >>>>> removing >> > >> > > > > > > >>>>> the patchprocess dir, so moved it off the >> workspace. >> > >> > > > > > > >>>> Thanks Giri. Should I resubmit HDFS-6954's patch? >> I've >> > >> > gotten >> > >> > > 3 >> > >> > > > > or 4 >> > >> > > > > > > >>>> jenkins messages that indicated the problem so >> > something >> > >> is >> > >> > > > > > > >> resubmitting, >> > >> > > > > > > >>>> but now that you've fixed it, should I resubmit it >> > again? >> > >> > > > > > > >>>> >> > >> > > > > > > >>>> Charles >> > >> > > > > > > >> >> > >> > > > > > > >> > >> > > > > > >> > >> > > > > >> > >> > > > > >> > >> > > > > >> > >> > > > > -- >> > >> > > > > Alejandro >> > >> > > > > >> > >> > > > >> > >> > > >> > >> > >> > >> >> > >> >> >> >> -- >> Todd Lipcon >> Software Engineer, Cloudera >> > >
