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 < gkesa...@hortonworks.com> 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 < > gkesa...@hortonworks.com> wrote: > > > I'm looking into it. > > > > -giri > > > > > > On Thu, Aug 28, 2014 at 3:18 AM, Ted Yu <yuzhih...@gmail.com> wrote: > > > >> I spent some time on PreCommit-hdfs-Build. > >> Looks like the following command was not effective: > >> > >> mkdir -p ${WORKSPACE}/patchprocess > >> > >> In build output, I saw: > >> > >> > >> > /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 <yuzhih...@gmail.com> 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 <yuzhih...@gmail.com> 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 < > ka...@cloudera.com > >> > > >> >> 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 <yuzhih...@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 < > >> ka...@cloudera.com> > >> >>> > wrote: > >> >>> > > >> >>> > > Thanks for reporting it, Ted. We are aware of it - second > >> follow-up > >> >>> item > >> >>> > in > >> >>> > > my earlier email. > >> >>> > > > >> >>> > > Unfortunately, I don't have access to the 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 <yuzhih...@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 <yuzhih...@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 < > >> >>> > ka...@cloudera.com> > >> >>> > > > > wrote: > >> >>> > > > > > >> >>> > > > >> Oh.. a couple more things. > >> >>> > > > >> > >> >>> > > > >> The git commit hashes have changed and are different from > >> what > >> >>> we > >> >>> > had > >> >>> > > on > >> >>> > > > >> our github. This might 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 < > >> >>> > ka...@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 > >> >>> > > > >> > > >> >>> > > > >> > > >> >>> > > > >> > >> >>> > > > > > >> >>> > > > > > >> >>> > > > > >> >>> > > > >> >>> > > >> >>> > >> >> > >> >> > >> > > >> > > > > > > -- > 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. >
