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,
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
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
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
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
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
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
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,
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
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?
We just got HADOOP-11001 in. If you have access, can you please try
modifying the Jenkins jobs taking the patch on HADOOP-11001 into
consideration.
On Wed, Aug 27, 2014 at 4:38 PM, Ted Yu yuzhih...@gmail.com wrote:
I have access.
I can switch the repository if you think it is time to do so.
Thanks Karthik for making Git repo ready.
Regards,
Yi Liu
-Original Message-
From: Karthik Kambatla [mailto:ka...@cloudera.com]
Sent: Thursday, August 28, 2014 2:26 PM
To: common-dev@hadoop.apache.org
Subject: Re: Git repo ready to use
We just got HADOOP-11001 in. If you have access
I modified config for the following builds:
https://builds.apache.org/job/PreCommit-HDFS-Build/build #7808 would be
checking out trunk using git.
https://builds.apache.org/job/PreCommit-yarn-Build/
https://builds.apache.org/job/PreCommit-mapreduce-Build/
Should I modify the other Jenkins
build #7808 failed due to QA bot trying to apply the following as patch:
http://issues.apache.org/jira/secure/attachment/12552318/dfsio-x86-trunk-vs-3529.png
FYI
On Thu, Aug 28, 2014 at 1:52 AM, Ted Yu yuzhih...@gmail.com wrote:
I modified config for the following builds:
I spent some time on PreCommit-hdfs-Build.
Looks like the following command was not effective:
mkdir -p ${WORKSPACE}/patchprocess
In build output, I saw:
/home/jenkins/jenkins-slave/workspace/PreCommit-HDFS-Build/patchprocess/jira:
No such file or directory
I will work with Giri in the
I'm looking into it.
-giri
On Thu, Aug 28, 2014 at 3:18 AM, Ted Yu yuzhih...@gmail.com wrote:
I spent some time on PreCommit-hdfs-Build.
Looks like the following command was not effective:
mkdir -p ${WORKSPACE}/patchprocess
In build output, I saw:
Fixed all the 3 pre-commit buids. test-patch's git reset --hard is removing
the patchprocess dir, so moved it off the workspace.
-giri
On Thu, Aug 28, 2014 at 8:48 AM, Giridharan Kesavan
gkesa...@hortonworks.com wrote:
I'm looking into it.
-giri
On Thu, Aug 28, 2014 at 3:18 AM, Ted Yu
Thanks, Giri
I have switched the following builds to using git:
https://builds.apache.org/job/Hadoop-Yarn-trunk/
https://builds.apache.org/job/Hadoop-hdfs-trunk/
https://builds.apache.org/job/Hadoop-mapreduce-trunk/
Cheers
On Thu, Aug 28, 2014 at 9:07 AM, Giridharan Kesavan
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
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
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
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
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
Currently patchprocess/ (contents shown below) is one level higher than
${WORKSPACE}
diffJavadocWarnings.txt newPatchFindbugsWarningshadoop-hdfs.html
patchFindBugsOutputhadoop-hdfs.txtpatchReleaseAuditOutput.txt
trunkJavadocWarnings.txt
filteredPatchJavacWarnings.txt
Hi folks,
I am very excited to let you know that the git repo is now writable. I
committed a few changes (CHANGES.txt fixes and branching for 2.5.1) and
everything looks good.
Current status:
1. All branches have the same names, including trunk.
2. Force push is disabled on trunk,
Oh.. a couple more things.
The git commit hashes have changed and are different from what we had on
our github. This might interfere with any build automations that folks
have.
Another follow-up item: email and JIRA integration
On Wed, Aug 27, 2014 at 1:33 AM, Karthik Kambatla
Committed YARN-2035 successfully via git. Email notification seems to work
already.
On Wed, Aug 27, 2014 at 1:40 AM, Karthik Kambatla ka...@cloudera.com
wrote:
Oh.. a couple more things.
The git commit hashes have changed and are different from what we had on
our github. This might
Hi Karthik,
Good to see migration completed.
Currently, *branch-2.5* points to *trunk *itself. I think it should point
to *origin/branch-2.5 *right?
Regards,
Vinay
On Wed, Aug 27, 2014 at 2:10 PM, Karthik Kambatla ka...@cloudera.com
wrote:
Oh.. a couple more things.
The git commit hashes
On Wed, Aug 27, 2014 at 2:19 AM, Vinayakumar B vinayakum...@apache.org
wrote:
Hi Karthik,
Good to see migration completed.
Currently, *branch-2.5* points to *trunk *itself. I think it should point
to *origin/branch-2.5 *right?
Are you referring to your local branch-2.5? What is origin?
Sorry for the noice. :) please ignore. All is well :)
I think, I did a mistake while checking out branch-2.5.
used git checkout *-b *branch-2.5 instead of git checkout branch-2.5
Regards,
Vinay
On Wed, Aug 27, 2014 at 2:52 PM, Karthik Kambatla ka...@cloudera.com
wrote:
On Wed, Aug 27, 2014
Currently Jenkins builds still use subversion as source.
Should Jenkins point to git ?
Cheers
On Wed, Aug 27, 2014 at 1:40 AM, Karthik Kambatla ka...@cloudera.com
wrote:
Oh.. a couple more things.
The git commit hashes have changed and are different from what we had on
our github. This
The emails for commits apparently all go to common-commits@, irrespective
of the project. Apparently, the git filtering is not as good as svn
filtering. Daniel offered to look into alternatives this coming weekend.
I filed INFRA-8250 to restore updates to JIRA on commits.
On Wed, Aug 27, 2014
It appears the comments from Hudson on our JIRAs (post commits) are not
setup by the INFRA team. Do we use any other scripts for this? If yes, do
we want to fix those scripts or use svngit2jira?
On Wed, Aug 27, 2014 at 10:18 AM, Karthik Kambatla ka...@cloudera.com
wrote:
The emails for commits
svngit2jira would write a message like this -
https://issues.apache.org/jira/browse/CLOUDSTACK-1638?focusedCommentId=13714929page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13714929
with a link to the commit like this -
Precommit builds are still using svn :
https://builds.apache.org/job/PreCommit-HDFS-Build/configure
https://builds.apache.org/job/PreCommit-YARN-Build/configure
FYI
On Wed, Aug 27, 2014 at 7:00 AM, Ted Yu yuzhih...@gmail.com wrote:
Currently Jenkins builds still use subversion as source.
Thanks for reporting it, Ted. We are aware of it - second follow-up item in
my earlier email.
Unfortunately, I don't have access to the builds to fix them and don't
quite know the procedure to get access either. I am waiting for someone
with access to help us out.
On Wed, Aug 27, 2014 at 3:45
I have access.
I can switch the repository if you think it is time to do so.
On Wed, Aug 27, 2014 at 4:35 PM, Karthik Kambatla ka...@cloudera.com
wrote:
Thanks for reporting it, Ted. We are aware of it - second follow-up item in
my earlier email.
Unfortunately, I don't have access to the
37 matches
Mail list logo
