Discussion:
Git repo ready to use
(too old to reply)
Karthik Kambatla
2014-08-27 08:33:57 UTC
Permalink
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, branch-2 and tags.
3. Even if you are experienced with git, take a look at
https://wiki.apache.org/hadoop/HowToCommitWithGit . Particularly, let us
avoid merge commits.

Follow-up items:

1. Update rest of the wiki documentation
2. Update precommit Jenkins jobs and get HADOOP-11001 committed (reviews
appreciated). Until this is done, the precommit jobs will run against our
old svn repo.
3. git mirrors etc. to use the new repo instead of the old svn repo.

Thanks again for your cooperation through the migration process. Please
reach out to me (or the list) if you find anything missing or have
suggestions.

Cheers!
Karthik
Karthik Kambatla
2014-08-27 08:40:02 UTC
Permalink
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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
wrote:

> 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, branch-2 and tags.
> 3. Even if you are experienced with git, take a look at
> https://wiki.apache.org/hadoop/HowToCommitWithGit . Particularly, let
> us avoid merge commits.
>
> Follow-up items:
>
> 1. Update rest of the wiki documentation
> 2. Update precommit Jenkins jobs and get HADOOP-11001 committed
> (reviews appreciated). Until this is done, the precommit jobs will run
> against our old svn repo.
> 3. git mirrors etc. to use the new repo instead of the old svn repo.
>
> Thanks again for your cooperation through the migration process. Please
> reach out to me (or the list) if you find anything missing or have
> suggestions.
>
> Cheers!
> Karthik
>
>
Zhijie Shen
2014-08-27 09:15:50 UTC
Permalink
Committed YARN-2035 successfully via git. Email notification seems to work
already.


On Wed, Aug 27, 2014 at 1:40 AM, Karthik Kambatla <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
wrote:

> 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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> wrote:
>
> > 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, branch-2 and tags.
> > 3. Even if you are experienced with git, take a look at
> > https://wiki.apache.org/hadoop/HowToCommitWithGit . Particularly, let
> > us avoid merge commits.
> >
> > Follow-up items:
> >
> > 1. Update rest of the wiki documentation
> > 2. Update precommit Jenkins jobs and get HADOOP-11001 committed
> > (reviews appreciated). Until this is done, the precommit jobs will run
> > against our old svn repo.
> > 3. git mirrors etc. to use the new repo instead of the old svn repo.
> >
> > Thanks again for your cooperation through the migration process. Please
> > reach out to me (or the list) if you find anything missing or have
> > suggestions.
> >
> > Cheers!
> > Karthik
> >
> >
>



--
Zhijie Shen
Hortonworks Inc.
http://hortonworks.com/

--
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.
Vinayakumar B
2014-08-27 09:19:54 UTC
Permalink
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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
wrote:

> 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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> wrote:
>
> > 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, branch-2 and tags.
> > 3. Even if you are experienced with git, take a look at
> > https://wiki.apache.org/hadoop/HowToCommitWithGit . Particularly, let
> > us avoid merge commits.
> >
> > Follow-up items:
> >
> > 1. Update rest of the wiki documentation
> > 2. Update precommit Jenkins jobs and get HADOOP-11001 committed
> > (reviews appreciated). Until this is done, the precommit jobs will run
> > against our old svn repo.
> > 3. git mirrors etc. to use the new repo instead of the old svn repo.
> >
> > Thanks again for your cooperation through the migration process. Please
> > reach out to me (or the list) if you find anything missing or have
> > suggestions.
> >
> > Cheers!
> > Karthik
> >
> >
>
Karthik Kambatla
2014-08-27 09:22:19 UTC
Permalink
On Wed, Aug 27, 2014 at 2:19 AM, Vinayakumar B <vinayakumarb-1oDqGaOF3Lkdnm+***@public.gmane.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?

branch-2.5 looks good to me.


>
> Regards,
> Vinay
>
>
> On Wed, Aug 27, 2014 at 2:10 PM, Karthik Kambatla <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> wrote:
>
> > 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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> > wrote:
> >
> > > 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, branch-2 and tags.
> > > 3. Even if you are experienced with git, take a look at
> > > https://wiki.apache.org/hadoop/HowToCommitWithGit . Particularly,
> let
> > > us avoid merge commits.
> > >
> > > Follow-up items:
> > >
> > > 1. Update rest of the wiki documentation
> > > 2. Update precommit Jenkins jobs and get HADOOP-11001 committed
> > > (reviews appreciated). Until this is done, the precommit jobs will
> run
> > > against our old svn repo.
> > > 3. git mirrors etc. to use the new repo instead of the old svn repo.
> > >
> > > Thanks again for your cooperation through the migration process. Please
> > > reach out to me (or the list) if you find anything missing or have
> > > suggestions.
> > >
> > > Cheers!
> > > Karthik
> > >
> > >
> >
>
Vinayakumar B
2014-08-27 09:43:13 UTC
Permalink
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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
wrote:

> On Wed, Aug 27, 2014 at 2:19 AM, Vinayakumar B <vinayakumarb-1oDqGaOF3Lkdnm+***@public.gmane.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?
>
> branch-2.5 looks good to me.
>
>
> >
> > Regards,
> > Vinay
> >
> >
> > On Wed, Aug 27, 2014 at 2:10 PM, Karthik Kambatla <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> > wrote:
> >
> > > 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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> > > wrote:
> > >
> > > > 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, branch-2 and tags.
> > > > 3. Even if you are experienced with git, take a look at
> > > > https://wiki.apache.org/hadoop/HowToCommitWithGit . Particularly,
> > let
> > > > us avoid merge commits.
> > > >
> > > > Follow-up items:
> > > >
> > > > 1. Update rest of the wiki documentation
> > > > 2. Update precommit Jenkins jobs and get HADOOP-11001 committed
> > > > (reviews appreciated). Until this is done, the precommit jobs will
> > run
> > > > against our old svn repo.
> > > > 3. git mirrors etc. to use the new repo instead of the old svn
> repo.
> > > >
> > > > Thanks again for your cooperation through the migration process.
> Please
> > > > reach out to me (or the list) if you find anything missing or have
> > > > suggestions.
> > > >
> > > > Cheers!
> > > > Karthik
> > > >
> > > >
> > >
> >
>
Ted Yu
2014-08-27 14:00:20 UTC
Permalink
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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
wrote:

> 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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> wrote:
>
> > 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, branch-2 and tags.
> > 3. Even if you are experienced with git, take a look at
> > https://wiki.apache.org/hadoop/HowToCommitWithGit . Particularly, let
> > us avoid merge commits.
> >
> > Follow-up items:
> >
> > 1. Update rest of the wiki documentation
> > 2. Update precommit Jenkins jobs and get HADOOP-11001 committed
> > (reviews appreciated). Until this is done, the precommit jobs will run
> > against our old svn repo.
> > 3. git mirrors etc. to use the new repo instead of the old svn repo.
> >
> > Thanks again for your cooperation through the migration process. Please
> > reach out to me (or the list) if you find anything missing or have
> > suggestions.
> >
> > Cheers!
> > Karthik
> >
> >
>
Ted Yu
2014-08-27 22:45:02 UTC
Permalink
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 <yuzhihong-***@public.gmane.org> wrote:

> 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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> wrote:
>
>> 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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
>> wrote:
>>
>> > 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, branch-2 and tags.
>> > 3. Even if you are experienced with git, take a look at
>> > https://wiki.apache.org/hadoop/HowToCommitWithGit . Particularly,
>> let
>> > us avoid merge commits.
>> >
>> > Follow-up items:
>> >
>> > 1. Update rest of the wiki documentation
>> > 2. Update precommit Jenkins jobs and get HADOOP-11001 committed
>> > (reviews appreciated). Until this is done, the precommit jobs will
>> run
>> > against our old svn repo.
>> > 3. git mirrors etc. to use the new repo instead of the old svn repo.
>> >
>> > Thanks again for your cooperation through the migration process. Please
>> > reach out to me (or the list) if you find anything missing or have
>> > suggestions.
>> >
>> > Cheers!
>> > Karthik
>> >
>> >
>>
>
>
Karthik Kambatla
2014-08-27 23:35:26 UTC
Permalink
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 PM, Ted Yu <yuzhihong-***@public.gmane.org> wrote:

> 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 <yuzhihong-***@public.gmane.org> wrote:
>
> > 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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> > wrote:
> >
> >> 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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> >> wrote:
> >>
> >> > 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, branch-2 and tags.
> >> > 3. Even if you are experienced with git, take a look at
> >> > https://wiki.apache.org/hadoop/HowToCommitWithGit . Particularly,
> >> let
> >> > us avoid merge commits.
> >> >
> >> > Follow-up items:
> >> >
> >> > 1. Update rest of the wiki documentation
> >> > 2. Update precommit Jenkins jobs and get HADOOP-11001 committed
> >> > (reviews appreciated). Until this is done, the precommit jobs will
> >> run
> >> > against our old svn repo.
> >> > 3. git mirrors etc. to use the new repo instead of the old svn
> repo.
> >> >
> >> > Thanks again for your cooperation through the migration process.
> Please
> >> > reach out to me (or the list) if you find anything missing or have
> >> > suggestions.
> >> >
> >> > Cheers!
> >> > Karthik
> >> >
> >> >
> >>
> >
> >
>
Ted Yu
2014-08-27 23:38:23 UTC
Permalink
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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
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 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 PM, Ted Yu <yuzhihong-***@public.gmane.org> wrote:
>
> > 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 <yuzhihong-***@public.gmane.org> wrote:
> >
> > > 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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> > > wrote:
> > >
> > >> 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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org
> >
> > >> wrote:
> > >>
> > >> > 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, branch-2 and tags.
> > >> > 3. Even if you are experienced with git, take a look at
> > >> > https://wiki.apache.org/hadoop/HowToCommitWithGit .
> Particularly,
> > >> let
> > >> > us avoid merge commits.
> > >> >
> > >> > Follow-up items:
> > >> >
> > >> > 1. Update rest of the wiki documentation
> > >> > 2. Update precommit Jenkins jobs and get HADOOP-11001 committed
> > >> > (reviews appreciated). Until this is done, the precommit jobs
> will
> > >> run
> > >> > against our old svn repo.
> > >> > 3. git mirrors etc. to use the new repo instead of the old svn
> > repo.
> > >> >
> > >> > Thanks again for your cooperation through the migration process.
> > Please
> > >> > reach out to me (or the list) if you find anything missing or have
> > >> > suggestions.
> > >> >
> > >> > Cheers!
> > >> > Karthik
> > >> >
> > >> >
> > >>
> > >
> > >
> >
>
Karthik Kambatla
2014-08-28 06:25:41 UTC
Permalink
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 <yuzhihong-***@public.gmane.org> wrote:

> 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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> 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 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 PM, Ted Yu <yuzhihong-***@public.gmane.org> wrote:
> >
> > > 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 <yuzhihong-***@public.gmane.org> wrote:
> > >
> > > > 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 <
> kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> > > > wrote:
> > > >
> > > >> 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 <
> kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org
> > >
> > > >> wrote:
> > > >>
> > > >> > 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, branch-2 and tags.
> > > >> > 3. Even if you are experienced with git, take a look at
> > > >> > https://wiki.apache.org/hadoop/HowToCommitWithGit .
> > Particularly,
> > > >> let
> > > >> > us avoid merge commits.
> > > >> >
> > > >> > Follow-up items:
> > > >> >
> > > >> > 1. Update rest of the wiki documentation
> > > >> > 2. Update precommit Jenkins jobs and get HADOOP-11001 committed
> > > >> > (reviews appreciated). Until this is done, the precommit jobs
> > will
> > > >> run
> > > >> > against our old svn repo.
> > > >> > 3. git mirrors etc. to use the new repo instead of the old svn
> > > repo.
> > > >> >
> > > >> > Thanks again for your cooperation through the migration process.
> > > Please
> > > >> > reach out to me (or the list) if you find anything missing or have
> > > >> > suggestions.
> > > >> >
> > > >> > Cheers!
> > > >> > Karthik
> > > >> >
> > > >> >
> > > >>
> > > >
> > > >
> > >
> >
>
Liu, Yi A
2014-08-28 06:42:08 UTC
Permalink
Thanks Karthik for making Git repo ready.

Regards,
Yi Liu


-----Original Message-----
From: Karthik Kambatla [mailto:***@cloudera.com]
Sent: Thursday, August 28, 2014 2:26 PM
To: common-***@hadoop.apache.org
Subject: Re: Git repo ready to use

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 <***@gmail.com> wrote:

> 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 <***@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 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 PM, Ted Yu <***@gmail.com> wrote:
> >
> > > 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 <***@gmail.com> wrote:
> > >
> > > > 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 <
> ***@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 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 <
> ***@cloudera.com
> > >
> > > >> wrote:
> > > >>
> > > >> > 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, branch-2 and tags.
> > > >> > 3. Even if you are experienced with git, take a look at
> > > >> > https://wiki.apache.org/hadoop/HowToCommitWithGit .
> > Particularly,
> > > >> let
> > > >> > us avoid merge commits.
> > > >> >
> > > >> > Follow-up items:
> > > >> >
> > > >> > 1. Update rest of the wiki documentation
> > > >> > 2. Update precommit Jenkins jobs and get HADOOP-11001 committed
> > > >> > (reviews appreciated). Until this is done, the precommit
> > > >> > jobs
> > will
> > > >> run
> > > >> > against our old svn repo.
> > > >> > 3. git mirrors etc. to use the new repo instead of the old
> > > >> > svn
> > > repo.
> > > >> >
> > > >> > Thanks again for your cooperation through the migration process.
> > > Please
> > > >> > reach out to me (or the list) if you find anything missing or
> > > >> > have suggestions.
> > > >> >
> > > >> > Cheers!
> > > >> > Karthik
> > > >> >
> > > >
Ted Yu
2014-08-28 08:52:09 UTC
Permalink
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 jobs e.g.:

https://builds.apache.org/job/Hadoop-Yarn-trunk/

Cheers


On Wed, Aug 27, 2014 at 11:25 PM, Karthik Kambatla <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
wrote:

> 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 <yuzhihong-***@public.gmane.org> wrote:
>
> > 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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> > 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 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 PM, Ted Yu <yuzhihong-***@public.gmane.org> wrote:
> > >
> > > > 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 <yuzhihong-***@public.gmane.org> wrote:
> > > >
> > > > > 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 <
> > kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> > > > > wrote:
> > > > >
> > > > >> 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 <
> > kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org
> > > >
> > > > >> wrote:
> > > > >>
> > > > >> > 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, branch-2 and tags.
> > > > >> > 3. Even if you are experienced with git, take a look at
> > > > >> > https://wiki.apache.org/hadoop/HowToCommitWithGit .
> > > Particularly,
> > > > >> let
> > > > >> > us avoid merge commits.
> > > > >> >
> > > > >> > Follow-up items:
> > > > >> >
> > > > >> > 1. Update rest of the wiki documentation
> > > > >> > 2. Update precommit Jenkins jobs and get HADOOP-11001
> committed
> > > > >> > (reviews appreciated). Until this is done, the precommit jobs
> > > will
> > > > >> run
> > > > >> > against our old svn repo.
> > > > >> > 3. git mirrors etc. to use the new repo instead of the old
> svn
> > > > repo.
> > > > >> >
> > > > >> > Thanks again for your cooperation through the migration process.
> > > > Please
> > > > >> > reach out to me (or the list) if you find anything missing or
> have
> > > > >> > suggestions.
> > > > >> >
> > > > >> > Cheers!
> > > > >> > Karthik
> > > > >> >
> > > > >> >
> > > > >>
> > > > >
> > > > >
> > > >
> > >
> >
>
Ted Yu
2014-08-28 09:04:12 UTC
Permalink
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 <yuzhihong-***@public.gmane.org> wrote:

> 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 jobs e.g.:
>
> https://builds.apache.org/job/Hadoop-Yarn-trunk/
>
> Cheers
>
>
> On Wed, Aug 27, 2014 at 11:25 PM, Karthik Kambatla <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> wrote:
>
>> 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 <yuzhihong-***@public.gmane.org> wrote:
>>
>> > 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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
>> > 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 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 PM, Ted Yu <yuzhihong-***@public.gmane.org> wrote:
>> > >
>> > > > 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 <yuzhihong-***@public.gmane.org>
>> wrote:
>> > > >
>> > > > > 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 <
>> > kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
>> > > > > wrote:
>> > > > >
>> > > > >> 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 <
>> > kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org
>> > > >
>> > > > >> wrote:
>> > > > >>
>> > > > >> > 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, branch-2 and tags.
>> > > > >> > 3. Even if you are experienced with git, take a look at
>> > > > >> > https://wiki.apache.org/hadoop/HowToCommitWithGit .
>> > > Particularly,
>> > > > >> let
>> > > > >> > us avoid merge commits.
>> > > > >> >
>> > > > >> > Follow-up items:
>> > > > >> >
>> > > > >> > 1. Update rest of the wiki documentation
>> > > > >> > 2. Update precommit Jenkins jobs and get HADOOP-11001
>> committed
>> > > > >> > (reviews appreciated). Until this is done, the precommit
>> jobs
>> > > will
>> > > > >> run
>> > > > >> > against our old svn repo.
>> > > > >> > 3. git mirrors etc. to use the new repo instead of the old
>> svn
>> > > > repo.
>> > > > >> >
>> > > > >> > Thanks again for your cooperation through the migration
>> process.
>> > > > Please
>> > > > >> > reach out to me (or the list) if you find anything missing or
>> have
>> > > > >> > suggestions.
>> > > > >> >
>> > > > >> > Cheers!
>> > > > >> > Karthik
>> > > > >> >
>> > > > >> >
>> > > > >>
>> > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>
>
Ted Yu
2014-08-28 10:18:20 UTC
Permalink
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 morning.


Cheers



On Thu, Aug 28, 2014 at 2:04 AM, Ted Yu <yuzhihong-***@public.gmane.org> wrote:

> 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 <yuzhihong-***@public.gmane.org> wrote:
>
>> 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 jobs e.g.:
>>
>> https://builds.apache.org/job/Hadoop-Yarn-trunk/
>>
>> Cheers
>>
>>
>> On Wed, Aug 27, 2014 at 11:25 PM, Karthik Kambatla <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
>> wrote:
>>
>>> 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 <yuzhihong-***@public.gmane.org> wrote:
>>>
>>> > 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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
>>> > 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 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 PM, Ted Yu <yuzhihong-***@public.gmane.org> wrote:
>>> > >
>>> > > > 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 <yuzhihong-***@public.gmane.org>
>>> wrote:
>>> > > >
>>> > > > > 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 <
>>> > kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
>>> > > > > wrote:
>>> > > > >
>>> > > > >> 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 <
>>> > kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org
>>> > > >
>>> > > > >> wrote:
>>> > > > >>
>>> > > > >> > 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, branch-2 and tags.
>>> > > > >> > 3. Even if you are experienced with git, take a look at
>>> > > > >> > https://wiki.apache.org/hadoop/HowToCommitWithGit .
>>> > > Particularly,
>>> > > > >> let
>>> > > > >> > us avoid merge commits.
>>> > > > >> >
>>> > > > >> > Follow-up items:
>>> > > > >> >
>>> > > > >> > 1. Update rest of the wiki documentation
>>> > > > >> > 2. Update precommit Jenkins jobs and get HADOOP-11001
>>> committed
>>> > > > >> > (reviews appreciated). Until this is done, the precommit
>>> jobs
>>> > > will
>>> > > > >> run
>>> > > > >> > against our old svn repo.
>>> > > > >> > 3. git mirrors etc. to use the new repo instead of the old
>>> svn
>>> > > > repo.
>>> > > > >> >
>>> > > > >> > Thanks again for your cooperation through the migration
>>> process.
>>> > > > Please
>>> > > > >> > reach out to me (or the list) if you find anything missing or
>>> have
>>> > > > >> > suggestions.
>>> > > > >> >
>>> > > > >> > Cheers!
>>> > > > >> > Karthik
>>> > > > >> >
>>> > > > >> >
>>> > > > >>
>>> > > > >
>>> > > > >
>>> > > >
>>> > >
>>> >
>>>
>>
>>
>
Steve Loughran
2014-08-28 11:16:56 UTC
Permalink
thx for trying, ted

for any committer who wants to work with jenkins, the instructions are

http://wiki.apache.org/general/Jenkins#How_do_I_get_an_account


On 28 August 2014 11:18, Ted Yu <yuzhihong-***@public.gmane.org> 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:
>
>
> /home/jenkins/jenkins-slave/workspace/PreCommit-HDFS-Build/patchprocess/jira:
> No such file or directory
>
>
> I will work with Giri in the morning.
>
>
> Cheers
>
>
>
> On Thu, Aug 28, 2014 at 2:04 AM, Ted Yu <yuzhihong-***@public.gmane.org> wrote:
>
> > 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 <yuzhihong-***@public.gmane.org> wrote:
> >
> >> 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 jobs e.g.:
> >>
> >> https://builds.apache.org/job/Hadoop-Yarn-trunk/
> >>
> >> Cheers
> >>
> >>
> >> On Wed, Aug 27, 2014 at 11:25 PM, Karthik Kambatla <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> >> wrote:
> >>
> >>> 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 <yuzhihong-***@public.gmane.org> wrote:
> >>>
> >>> > 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 <
> kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> >>> > 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 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 PM, Ted Yu <yuzhihong-***@public.gmane.org>
> wrote:
> >>> > >
> >>> > > > 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 <yuzhihong-***@public.gmane.org>
> >>> wrote:
> >>> > > >
> >>> > > > > 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 <
> >>> > kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> >>> > > > > wrote:
> >>> > > > >
> >>> > > > >> 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 <
> >>> > kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org
> >>> > > >
> >>> > > > >> wrote:
> >>> > > > >>
> >>> > > > >> > 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, branch-2 and tags.
> >>> > > > >> > 3. Even if you are experienced with git, take a look at
> >>> > > > >> > https://wiki.apache.org/hadoop/HowToCommitWithGit .
> >>> > > Particularly,
> >>> > > > >> let
> >>> > > > >> > us avoid merge commits.
> >>> > > > >> >
> >>> > > > >> > Follow-up items:
> >>> > > > >> >
> >>> > > > >> > 1. Update rest of the wiki documentation
> >>> > > > >> > 2. Update precommit Jenkins jobs and get HADOOP-11001
> >>> committed
> >>> > > > >> > (reviews appreciated). Until this is done, the precommit
> >>> jobs
> >>> > > will
> >>> > > > >> run
> >>> > > > >> > against our old svn repo.
> >>> > > > >> > 3. git mirrors etc. to use the new repo instead of the
> old
> >>> svn
> >>> > > > repo.
> >>> > > > >> >
> >>> > > > >> > Thanks again for your cooperation through the migration
> >>> process.
> >>> > > > Please
> >>> > > > >> > reach out to me (or the list) if you find anything missing
> or
> >>> have
> >>> > > > >> > suggestions.
> >>> > > > >> >
> >>> > > > >> > Cheers!
> >>> > > > >> > Karthik
> >>> > > > >> >
> >>> > > > >> >
> >>> > > > >>
> >>> > > > >
> >>> > > > >
> >>> > > >
> >>> > >
> >>> >
> >>>
> >>
> >>
> >
>

--
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.
Giridharan Kesavan
2014-08-28 15:48:06 UTC
Permalink
I'm looking into it.

-giri


On Thu, Aug 28, 2014 at 3:18 AM, Ted Yu <yuzhihong-***@public.gmane.org> 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:
>
>
> /home/jenkins/jenkins-slave/workspace/PreCommit-HDFS-Build/patchprocess/jira:
> No such file or directory
>
>
> I will work with Giri in the morning.
>
>
> Cheers
>
>
>
> On Thu, Aug 28, 2014 at 2:04 AM, Ted Yu <yuzhihong-***@public.gmane.org> wrote:
>
> > 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 <yuzhihong-***@public.gmane.org> wrote:
> >
> >> 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 jobs e.g.:
> >>
> >> https://builds.apache.org/job/Hadoop-Yarn-trunk/
> >>
> >> Cheers
> >>
> >>
> >> On Wed, Aug 27, 2014 at 11:25 PM, Karthik Kambatla <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> >> wrote:
> >>
> >>> 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 <yuzhihong-***@public.gmane.org> wrote:
> >>>
> >>> > 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 <
> kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> >>> > 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 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 PM, Ted Yu <yuzhihong-***@public.gmane.org>
> wrote:
> >>> > >
> >>> > > > 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 <yuzhihong-***@public.gmane.org>
> >>> wrote:
> >>> > > >
> >>> > > > > 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 <
> >>> > kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> >>> > > > > wrote:
> >>> > > > >
> >>> > > > >> 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 <
> >>> > kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org
> >>> > > >
> >>> > > > >> wrote:
> >>> > > > >>
> >>> > > > >> > 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, branch-2 and tags.
> >>> > > > >> > 3. Even if you are experienced with git, take a look at
> >>> > > > >> > https://wiki.apache.org/hadoop/HowToCommitWithGit .
> >>> > > Particularly,
> >>> > > > >> let
> >>> > > > >> > us avoid merge commits.
> >>> > > > >> >
> >>> > > > >> > Follow-up items:
> >>> > > > >> >
> >>> > > > >> > 1. Update rest of the wiki documentation
> >>> > > > >> > 2. Update precommit Jenkins jobs and get HADOOP-11001
> >>> committed
> >>> > > > >> > (reviews appreciated). Until this is done, the precommit
> >>> jobs
> >>> > > will
> >>> > > > >> run
> >>> > > > >> > against our old svn repo.
> >>> > > > >> > 3. git mirrors etc. to use the new repo instead of the
> old
> >>> svn
> >>> > > > repo.
> >>> > > > >> >
> >>> > > > >> > Thanks again for your cooperation through the migration
> >>> process.
> >>> > > > Please
> >>> > > > >> > reach out to me (or the list) if you find anything missing
> or
> >>> have
> >>> > > > >> > suggestions.
> >>> > > > >> >
> >>> > > > >> > Cheers!
> >>> > > > >> > Karthik
> >>> > > > >> >
> >>> > > > >> >
> >>> > > > >>
> >>> > > > >
> >>> > > > >
> >>> > > >
> >>> > >
> >>> >
> >>>
> >>
> >>
> >
>

--
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.
Giridharan Kesavan
2014-08-28 16:07:33 UTC
Permalink
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 <
gkesavan-RYNwJFaOa9CEK/***@public.gmane.org> wrote:

> I'm looking into it.
>
> -giri
>
>
> On Thu, Aug 28, 2014 at 3:18 AM, Ted Yu <yuzhihong-***@public.gmane.org> 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:
>>
>>
>> /home/jenkins/jenkins-slave/workspace/PreCommit-HDFS-Build/patchprocess/jira:
>> No such file or directory
>>
>>
>> I will work with Giri in the morning.
>>
>>
>> Cheers
>>
>>
>>
>> On Thu, Aug 28, 2014 at 2:04 AM, Ted Yu <yuzhihong-***@public.gmane.org> wrote:
>>
>> > 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 <yuzhihong-***@public.gmane.org> wrote:
>> >
>> >> 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 jobs e.g.:
>> >>
>> >> https://builds.apache.org/job/Hadoop-Yarn-trunk/
>> >>
>> >> Cheers
>> >>
>> >>
>> >> On Wed, Aug 27, 2014 at 11:25 PM, Karthik Kambatla <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org
>> >
>> >> wrote:
>> >>
>> >>> 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 <yuzhihong-***@public.gmane.org> wrote:
>> >>>
>> >>> > 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 <
>> kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
>> >>> > 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 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 PM, Ted Yu <yuzhihong-***@public.gmane.org>
>> wrote:
>> >>> > >
>> >>> > > > 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 <yuzhihong-***@public.gmane.org>
>> >>> wrote:
>> >>> > > >
>> >>> > > > > 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 <
>> >>> > kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
>> >>> > > > > wrote:
>> >>> > > > >
>> >>> > > > >> 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 <
>> >>> > kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org
>> >>> > > >
>> >>> > > > >> wrote:
>> >>> > > > >>
>> >>> > > > >> > 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, branch-2 and tags.
>> >>> > > > >> > 3. Even if you are experienced with git, take a look at
>> >>> > > > >> > https://wiki.apache.org/hadoop/HowToCommitWithGit .
>> >>> > > Particularly,
>> >>> > > > >> let
>> >>> > > > >> > us avoid merge commits.
>> >>> > > > >> >
>> >>> > > > >> > Follow-up items:
>> >>> > > > >> >
>> >>> > > > >> > 1. Update rest of the wiki documentation
>> >>> > > > >> > 2. Update precommit Jenkins jobs and get HADOOP-11001
>> >>> committed
>> >>> > > > >> > (reviews appreciated). Until this is done, the precommit
>> >>> jobs
>> >>> > > will
>> >>> > > > >> run
>> >>> > > > >> > against our old svn repo.
>> >>> > > > >> > 3. git mirrors etc. to use the new repo instead of the
>> old
>> >>> svn
>> >>> > > > repo.
>> >>> > > > >> >
>> >>> > > > >> > Thanks again for your cooperation through the migration
>> >>> process.
>> >>> > > > Please
>> >>> > > > >> > reach out to me (or the list) if you find anything missing
>> or
>> >>> have
>> >>> > > > >> > suggestions.
>> >>> > > > >> >
>> >>> > > > >> > Cheers!
>> >>> > > > >> > Karthik
>> >>> > > > >> >
>> >>> > > > >> >
>> >>> > > > >>
>> >>> > > > >
>> >>> > > > >
>> >>> > > >
>> >>> > >
>> >>> >
>> >>>
>> >>
>> >>
>> >
>>
>
>

--
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.
Ted Yu
2014-08-28 16:30:23 UTC
Permalink
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 <
gkesavan-RYNwJFaOa9CEK/***@public.gmane.org> 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.
>
>
>
> -giri
>
>
> On Thu, Aug 28, 2014 at 8:48 AM, Giridharan Kesavan <
> gkesavan-RYNwJFaOa9CEK/***@public.gmane.org> wrote:
>
> > I'm looking into it.
> >
> > -giri
> >
> >
> > On Thu, Aug 28, 2014 at 3:18 AM, Ted Yu <yuzhihong-***@public.gmane.org> 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:
> >>
> >>
> >>
> /home/jenkins/jenkins-slave/workspace/PreCommit-HDFS-Build/patchprocess/jira:
> >> No such file or directory
> >>
> >>
> >> I will work with Giri in the morning.
> >>
> >>
> >> Cheers
> >>
> >>
> >>
> >> On Thu, Aug 28, 2014 at 2:04 AM, Ted Yu <yuzhihong-***@public.gmane.org> wrote:
> >>
> >> > 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 <yuzhihong-***@public.gmane.org> wrote:
> >> >
> >> >> 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 jobs e.g.:
> >> >>
> >> >> https://builds.apache.org/job/Hadoop-Yarn-trunk/
> >> >>
> >> >> Cheers
> >> >>
> >> >>
> >> >> On Wed, Aug 27, 2014 at 11:25 PM, Karthik Kambatla <
> kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org
> >> >
> >> >> wrote:
> >> >>
> >> >>> 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 <yuzhihong-***@public.gmane.org>
> wrote:
> >> >>>
> >> >>> > 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 <
> >> kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> >> >>> > 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 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 PM, Ted Yu <yuzhihong-***@public.gmane.org>
> >> wrote:
> >> >>> > >
> >> >>> > > > 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 <yuzhihong-***@public.gmane.org>
> >> >>> wrote:
> >> >>> > > >
> >> >>> > > > > 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 <
> >> >>> > kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> >> >>> > > > > wrote:
> >> >>> > > > >
> >> >>> > > > >> 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 <
> >> >>> > kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org
> >> >>> > > >
> >> >>> > > > >> wrote:
> >> >>> > > > >>
> >> >>> > > > >> > 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, branch-2 and tags.
> >> >>> > > > >> > 3. Even if you are experienced with git, take a look
> at
> >> >>> > > > >> > https://wiki.apache.org/hadoop/HowToCommitWithGit .
> >> >>> > > Particularly,
> >> >>> > > > >> let
> >> >>> > > > >> > us avoid merge commits.
> >> >>> > > > >> >
> >> >>> > > > >> > Follow-up items:
> >> >>> > > > >> >
> >> >>> > > > >> > 1. Update rest of the wiki documentation
> >> >>> > > > >> > 2. Update precommit Jenkins jobs and get HADOOP-11001
> >> >>> committed
> >> >>> > > > >> > (reviews appreciated). Until this is done, the
> precommit
> >> >>> jobs
> >> >>> > > will
> >> >>> > > > >> run
> >> >>> > > > >> > against our old svn repo.
> >> >>> > > > >> > 3. git mirrors etc. to use the new repo instead of the
> >> old
> >> >>> svn
> >> >>> > > > repo.
> >> >>> > > > >> >
> >> >>> > > > >> > Thanks again for your cooperation through the migration
> >> >>> process.
> >> >>> > > > Please
> >> >>> > > > >> > reach out to me (or the list) if you find anything
> missing
> >> or
> >> >>> have
> >> >>> > > > >> > suggestions.
> >> >>> > > > >> >
> >> >>> > > > >> > Cheers!
> >> >>> > > > >> > Karthik
> >> >>> > > > >> >
> >> >>> > > > >> >
> >> >>> > > > >>
> >> >>> > > > >
> >> >>> > > > >
> >> >>> > > >
> >> >>> > >
> >> >>> >
> >> >>>
> >> >>
> >> >>
> >> >
> >>
> >
> >
>
> --
> 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.
>
Charles Lamb
2014-08-28 16:41:30 UTC
Permalink
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
Ted Yu
2014-08-28 16:49:13 UTC
Permalink
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 <clamb-psgPW5cihnJWk0Htik3J/***@public.gmane.org> 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
>
>
Karthik Kambatla
2014-08-28 23:21:21 UTC
Permalink
Thanks Giri and Ted for fixing the builds.


On Thu, Aug 28, 2014 at 9:49 AM, Ted Yu <yuzhihong-***@public.gmane.org> 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 <clamb-psgPW5cihnJWk0Htik3J/***@public.gmane.org> 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
> >
> >
>
Andrew Wang
2014-08-29 03:00:21 UTC
Permalink
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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
wrote:

> Thanks Giri and Ted for fixing the builds.
>
>
> On Thu, Aug 28, 2014 at 9:49 AM, Ted Yu <yuzhihong-***@public.gmane.org> 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 <clamb-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> 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 Abdelnur
2014-08-29 04:16:45 UTC
Permalink
i'm also seeing broken links for javadocs warnings.

Alejandro
(phone typing)

> On Aug 28, 2014, at 20:00, Andrew Wang <andrew.wang-psgPW5cihnJWk0Htik3J/***@public.gmane.org> 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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> wrote:
>
>> Thanks Giri and Ted for fixing the builds.
>>
>>
>>> On Thu, Aug 28, 2014 at 9:49 AM, Ted Yu <yuzhihong-***@public.gmane.org> 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 <clamb-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
>>> 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
>>
Ted Yu
2014-08-29 04:26:23 UTC
Permalink
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 <tucu-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
wrote:

> i'm also seeing broken links for javadocs warnings.
>
> Alejandro
> (phone typing)
>
> > On Aug 28, 2014, at 20:00, Andrew Wang <andrew.wang-psgPW5cihnJWk0Htik3J/***@public.gmane.org> 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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> > wrote:
> >
> >> Thanks Giri and Ted for fixing the builds.
> >>
> >>
> >>> On Thu, Aug 28, 2014 at 9:49 AM, Ted Yu <yuzhihong-***@public.gmane.org> 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 <clamb-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> >>> 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 Abdelnur
2014-08-29 15:48:36 UTC
Permalink
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 <yuzhihong-***@public.gmane.org> 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 <tucu-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> wrote:
>
> > i'm also seeing broken links for javadocs warnings.
> >
> > Alejandro
> > (phone typing)
> >
> > > On Aug 28, 2014, at 20:00, Andrew Wang <andrew.wang-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> 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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> > > wrote:
> > >
> > >> Thanks Giri and Ted for fixing the builds.
> > >>
> > >>
> > >>> On Thu, Aug 28, 2014 at 9:49 AM, Ted Yu <yuzhihong-***@public.gmane.org> 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 <clamb-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> > >>> 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
Ted Yu
2014-08-29 18:51:30 UTC
Permalink
>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 <tucu-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
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 <yuzhihong-***@public.gmane.org> 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 <tucu-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> > wrote:
> >
> > > i'm also seeing broken links for javadocs warnings.
> > >
> > > Alejandro
> > > (phone typing)
> > >
> > > > On Aug 28, 2014, at 20:00, Andrew Wang <andrew.wang-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> > 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 <
> kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> > > > wrote:
> > > >
> > > >> Thanks Giri and Ted for fixing the builds.
> > > >>
> > > >>
> > > >>> On Thu, Aug 28, 2014 at 9:49 AM, Ted Yu <yuzhihong-***@public.gmane.org>
> 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 <clamb-psgPW5cihnLQFizaE/***@public.gmane.orgm
> >
> > > >>> 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
>
Sangjin Lee
2014-09-04 06:07:00 UTC
Permalink
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 <yuzhihong-***@public.gmane.org> 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 <tucu-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> 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 <yuzhihong-***@public.gmane.org> 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 <tucu-psgPW5cihnJWk0Htik3J/***@public.gmane.org
> >
> > > wrote:
> > >
> > > > i'm also seeing broken links for javadocs warnings.
> > > >
> > > > Alejandro
> > > > (phone typing)
> > > >
> > > > > On Aug 28, 2014, at 20:00, Andrew Wang <andrew.wang-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> > > 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 <
> > kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> > > > > wrote:
> > > > >
> > > > >> Thanks Giri and Ted for fixing the builds.
> > > > >>
> > > > >>
> > > > >>> On Thu, Aug 28, 2014 at 9:49 AM, Ted Yu <yuzhihong-***@public.gmane.org>
> > 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 <
> clamb-psgPW5cihnJWk0Htik3J/***@public.gmane.org
> > >
> > > > >>> 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
> >
>
Vinayakumar B
2014-09-04 06:15:44 UTC
Permalink
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" <sjlee0-***@public.gmane.org> 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 <yuzhihong-***@public.gmane.org> 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 <tucu-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> > 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 <yuzhihong-***@public.gmane.org> 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 <
> tucu-psgPW5cihnJWk0Htik3J/***@public.gmane.org
> > >
> > > > wrote:
> > > >
> > > > > i'm also seeing broken links for javadocs warnings.
> > > > >
> > > > > Alejandro
> > > > > (phone typing)
> > > > >
> > > > > > On Aug 28, 2014, at 20:00, Andrew Wang <andrew.wang-psgPW5cihnJWk0Htik3J/***@public.gmane.org
> >
> > > > 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 <
> > > kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> > > > > > wrote:
> > > > > >
> > > > > >> Thanks Giri and Ted for fixing the builds.
> > > > > >>
> > > > > >>
> > > > > >>> On Thu, Aug 28, 2014 at 9:49 AM, Ted Yu <yuzhihong-***@public.gmane.org>
> > > 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 <
> > clamb-psgPW5cihnJWk0Htik3J/***@public.gmane.org
> > > >
> > > > > >>> 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
> > >
> >
>
Sangjin Lee
2014-09-04 15:54:17 UTC
Permalink
That's good to know. Thanks.


On Wed, Sep 3, 2014 at 11:15 PM, Vinayakumar B <vinayakumarb-1oDqGaOF3Lkdnm+***@public.gmane.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" <sjlee0-***@public.gmane.org> 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 <yuzhihong-***@public.gmane.org> 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 <tucu-psgPW5cihnJWk0Htik3J/***@public.gmane.org
> >
> > > 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 <yuzhihong-***@public.gmane.org> 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 <
> > tucu-psgPW5cihnJWk0Htik3J/***@public.gmane.org
> > > >
> > > > > wrote:
> > > > >
> > > > > > i'm also seeing broken links for javadocs warnings.
> > > > > >
> > > > > > Alejandro
> > > > > > (phone typing)
> > > > > >
> > > > > > > On Aug 28, 2014, at 20:00, Andrew Wang <
> andrew.wang-psgPW5cihnJWk0Htik3J/***@public.gmane.org
> > >
> > > > > 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 <
> > > > kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> > > > > > > wrote:
> > > > > > >
> > > > > > >> Thanks Giri and Ted for fixing the builds.
> > > > > > >>
> > > > > > >>
> > > > > > >>> On Thu, Aug 28, 2014 at 9:49 AM, Ted Yu <yuzhihong-***@public.gmane.org
> >
> > > > 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 <
> > > clamb-psgPW5cihnJWk0Htik3J/***@public.gmane.org
> > > > >
> > > > > > >>> 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
> > > >
> > >
> >
>
Andrew Wang
2014-09-08 22:38:36 UTC
Permalink
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 <sjlee0-***@public.gmane.org> wrote:

> That's good to know. Thanks.
>
>
> On Wed, Sep 3, 2014 at 11:15 PM, Vinayakumar B <vinayakumarb-1oDqGaOF3Lkdnm+***@public.gmane.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" <sjlee0-***@public.gmane.org> 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 <yuzhihong-***@public.gmane.org> 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 <
> tucu-psgPW5cihnJWk0Htik3J/***@public.gmane.org
> > >
> > > > 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 <yuzhihong-***@public.gmane.org>
> 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 <
> > > tucu-psgPW5cihnJWk0Htik3J/***@public.gmane.org
> > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > i'm also seeing broken links for javadocs warnings.
> > > > > > >
> > > > > > > Alejandro
> > > > > > > (phone typing)
> > > > > > >
> > > > > > > > On Aug 28, 2014, at 20:00, Andrew Wang <
> > andrew.wang-psgPW5cihnJWk0Htik3J/***@public.gmane.org
> > > >
> > > > > > 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 <
> > > > > kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > >> Thanks Giri and Ted for fixing the builds.
> > > > > > > >>
> > > > > > > >>
> > > > > > > >>> On Thu, Aug 28, 2014 at 9:49 AM, Ted Yu <
> yuzhihong-***@public.gmane.org
> > >
> > > > > 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 <
> > > > clamb-psgPW5cihnJWk0Htik3J/***@public.gmane.org
> > > > > >
> > > > > > > >>> 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
> > > > >
> > > >
> > >
> >
>
Colin McCabe
2014-09-12 18:31:57 UTC
Permalink
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.wang-psgPW5cihnJWk0Htik3J/***@public.gmane.org> 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 <sjlee0-***@public.gmane.org> wrote:
>
>> That's good to know. Thanks.
>>
>>
>> On Wed, Sep 3, 2014 at 11:15 PM, Vinayakumar B <vinayakumarb-1oDqGaOF3Lkdnm+***@public.gmane.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" <sjlee0-***@public.gmane.org> 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 <yuzhihong-***@public.gmane.org> 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 <
>> tucu-psgPW5cihnJWk0Htik3J/***@public.gmane.org
>> > >
>> > > > 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 <yuzhihong-***@public.gmane.org>
>> 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 <
>> > > tucu-psgPW5cihnJWk0Htik3J/***@public.gmane.org
>> > > > >
>> > > > > > wrote:
>> > > > > >
>> > > > > > > i'm also seeing broken links for javadocs warnings.
>> > > > > > >
>> > > > > > > Alejandro
>> > > > > > > (phone typing)
>> > > > > > >
>> > > > > > > > On Aug 28, 2014, at 20:00, Andrew Wang <
>> > andrew.wang-psgPW5cihnJWk0Htik3J/***@public.gmane.org
>> > > >
>> > > > > > 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 <
>> > > > > kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
>> > > > > > > > wrote:
>> > > > > > > >
>> > > > > > > >> Thanks Giri and Ted for fixing the builds.
>> > > > > > > >>
>> > > > > > > >>
>> > > > > > > >>> On Thu, Aug 28, 2014 at 9:49 AM, Ted Yu <
>> yuzhihong-***@public.gmane.org
>> > >
>> > > > > 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 <
>> > > > clamb-psgPW5cihnJWk0Htik3J/***@public.gmane.org
>> > > > > >
>> > > > > > > >>> 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
2014-09-15 18:14:28 UTC
Permalink
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 <cmccabe-***@public.gmane.org>
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.wang-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> 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 <sjlee0-***@public.gmane.org> wrote:
> >
> >> That's good to know. Thanks.
> >>
> >>
> >> On Wed, Sep 3, 2014 at 11:15 PM, Vinayakumar B <vinayakumarb-1oDqGaOF3Lkdnm+***@public.gmane.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" <sjlee0-***@public.gmane.org> 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 <yuzhihong-***@public.gmane.org>
> 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 <
> >> tucu-psgPW5cihnJWk0Htik3J/***@public.gmane.org
> >> > >
> >> > > > 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 <yuzhihong-***@public.gmane.org>
> >> 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 <
> >> > > tucu-psgPW5cihnJWk0Htik3J/***@public.gmane.org
> >> > > > >
> >> > > > > > wrote:
> >> > > > > >
> >> > > > > > > i'm also seeing broken links for javadocs warnings.
> >> > > > > > >
> >> > > > > > > Alejandro
> >> > > > > > > (phone typing)
> >> > > > > > >
> >> > > > > > > > On Aug 28, 2014, at 20:00, Andrew Wang <
> >> > andrew.wang-psgPW5cihnJWk0Htik3J/***@public.gmane.org
> >> > > >
> >> > > > > > 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 <
> >> > > > > kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> >> > > > > > > > wrote:
> >> > > > > > > >
> >> > > > > > > >> Thanks Giri and Ted for fixing the builds.
> >> > > > > > > >>
> >> > > > > > > >>
> >> > > > > > > >>> On Thu, Aug 28, 2014 at 9:49 AM, Ted Yu <
> >> yuzhihong-***@public.gmane.org
> >> > >
> >> > > > > 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 <
> >> > > > clamb-psgPW5cihnJWk0Htik3J/***@public.gmane.org
> >> > > > > >
> >> > > > > > > >>> 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
Karthik Kambatla
2014-08-27 17:18:42 UTC
Permalink
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 at 1:40 AM, Karthik Kambatla <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
wrote:

> 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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> wrote:
>
>> 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, branch-2 and tags.
>> 3. Even if you are experienced with git, take a look at
>> https://wiki.apache.org/hadoop/HowToCommitWithGit . Particularly, let
>> us avoid merge commits.
>>
>> Follow-up items:
>>
>> 1. Update rest of the wiki documentation
>> 2. Update precommit Jenkins jobs and get HADOOP-11001 committed
>> (reviews appreciated). Until this is done, the precommit jobs will run
>> against our old svn repo.
>> 3. git mirrors etc. to use the new repo instead of the old svn repo.
>>
>> Thanks again for your cooperation through the migration process. Please
>> reach out to me (or the list) if you find anything missing or have
>> suggestions.
>>
>> Cheers!
>> Karthik
>>
>>
>
Karthik Kambatla
2014-08-27 17:48:23 UTC
Permalink
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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
wrote:

> 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 at 1:40 AM, Karthik Kambatla <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> wrote:
>
>> 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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
>> wrote:
>>
>>> 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, branch-2 and tags.
>>> 3. Even if you are experienced with git, take a look at
>>> https://wiki.apache.org/hadoop/HowToCommitWithGit . Particularly,
>>> let us avoid merge commits.
>>>
>>> Follow-up items:
>>>
>>> 1. Update rest of the wiki documentation
>>> 2. Update precommit Jenkins jobs and get HADOOP-11001 committed
>>> (reviews appreciated). Until this is done, the precommit jobs will run
>>> against our old svn repo.
>>> 3. git mirrors etc. to use the new repo instead of the old svn repo.
>>>
>>> Thanks again for your cooperation through the migration process. Please
>>> reach out to me (or the list) if you find anything missing or have
>>> suggestions.
>>>
>>> Cheers!
>>> Karthik
>>>
>>>
>>
>
Karthik Kambatla
2014-08-27 17:51:24 UTC
Permalink
svngit2jira would write a message like this -
https://issues.apache.org/jira/browse/CLOUDSTACK-1638?focusedCommentId=13714929&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13714929
with a link to the commit like this -
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7260e8d

This is more concise and easier to look at than the Hudson list.


On Wed, Aug 27, 2014 at 10:48 AM, Karthik Kambatla <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
wrote:

> 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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
> wrote:
>
>> 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 at 1:40 AM, Karthik Kambatla <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
>> wrote:
>>
>>> 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 <kasha-psgPW5cihnJWk0Htik3J/***@public.gmane.org>
>>> wrote:
>>>
>>>> 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, branch-2 and tags.
>>>> 3. Even if you are experienced with git, take a look at
>>>> https://wiki.apache.org/hadoop/HowToCommitWithGit . Particularly,
>>>> let us avoid merge commits.
>>>>
>>>> Follow-up items:
>>>>
>>>> 1. Update rest of the wiki documentation
>>>> 2. Update precommit Jenkins jobs and get HADOOP-11001 committed
>>>> (reviews appreciated). Until this is done, the precommit jobs will run
>>>> against our old svn repo.
>>>> 3. git mirrors etc. to use the new repo instead of the old svn
>>>> repo.
>>>>
>>>> Thanks again for your cooperation through the migration process. Please
>>>> reach out to me (or the list) if you find anything missing or have
>>>> suggestions.
>>>>
>>>> Cheers!
>>>> Karthik
>>>>
>>>>
>>>
>>
>
Continue reading on narkive:
Loading...