Re: Creating branch-1

I'll help on creating a job, and adding the required properties file to the instance. - Sergio On Mon, Jun 8, 2015 at 1:06 PM, Alan Gates wrote: > For now I'll do the work in the scripts to add branch-1 as an option in > the same way other branches work now. Once we get that in place we can >

Re: Creating branch-1

For now I'll do the work in the scripts to add branch-1 as an option in the same way other branches work now. Once we get that in place we can start working on fancier stuff. I'm guessing someone with access rights to cloudera's instance on ec2 needs to configure the new build. I don't seem

Re: Creating branch-1

R1, right? Then the patch > file would need to be named 'HIVE--mr1.patch' so that it uses the MR1 > environment. > > Right now the code that parses this info is on process_jira function on > 'jenkins-common.sh', and it is called by 'jenkins-submit-build.

Re: Creating branch-1

> Date: Wednesday, June 3, 2015 at 12:17 To: "dev@hive.apache.org<mailto:dev@hive.apache.org>" mailto:dev@hive.apache.org>> Subject: Re: Creating branch-1 Hadoop uses a "Target Version" field. Not sure if this was done for all projects. +Vinod On Jun 3, 2015, at

Re: Creating branch-1

e, and let jenkins-submit-build.sh call the correct job with specific branch details. Any other ideas? - Sergio [cid:part1.08000808.03000103@gmail.com] Alan Gates<mailto:alanfga...@gmail.com> June 1, 2015 at 16:19 Based on our discussion and vote last week I'm working on creating branch-1.

Re: Creating branch-1

;. We can parse different branches there, and let jenkins-submit-build.sh call the correct job with specific branch details. Any other ideas? - Sergio Alan Gates <mailto:alanfga...@gmail.com> June 1, 2015 at 16:19 Based on our discussion and vote last week I'm working on creating

Re: Creating branch-1

now the code that parses this info is on process_jira function on > 'jenkins-common.sh', and it is called by 'jenkins-submit-build.sh'. We can > parse different branches there, and let jenkins-submit-build.sh call the > correct job with specific branch details. > >

Re: Creating branch-1

N, so feedback on that is good too.) Alan. Alan Gates <mailto:alanfga...@gmail.com> June 1, 2015 at 16:19 Based on our discussion and vote last week I'm working on creating branch-1. I plan to make the branch tomorrow. If anyone has a large commit they don't want to have to

Re: Creating branch-1

kins-submit-build.sh'. We can parse different branches there, and let jenkins-submit-build.sh call the correct job with specific branch details. Any other ideas? - Sergio On Mon, Jun 1, 2015 at 6:19 PM, Alan Gates wrote: > Based on our discussion and vote last week I'm working on cr

Re: Creating branch-1

I believe we should start using 2.0.0 as the fix version for patches that go into master, and 1.3.0 for the ones going into branch-1. Is that the belief of others as well ? On Tue, Jun 2, 2015 at 11:44 AM, Alan Gates wrote: > I pushed it to apache, so it should auto-clone to github, correct? >

Re: Creating branch-1

I pushed it to apache, so it should auto-clone to github, correct? Alan. Alexander Pivovarov June 2, 2015 at 11:34 Hi Alan Is branch-1 on github already? https://github.com/apache/hive/tree/branch-1

Re: Creating branch-1

on > clarity are welcomed. (At the same time I updated the page to contain git > instructions instead of SVN, so feedback on that is good too.) > > Alan. > > Alan Gates > June 1, 2015 at 16:19 > Based on our discussion and vote last week I'm working on creating >

Re: Creating branch-1

an. Alan Gates <mailto:alanfga...@gmail.com> June 1, 2015 at 16:19 Based on our discussion and vote last week I'm working on creating branch-1. I plan to make the branch tomorrow. If anyone has a large commit they don't want to have to commit twice and they are close to committi

Creating branch-1

Based on our discussion and vote last week I'm working on creating branch-1. I plan to make the branch tomorrow. If anyone has a large commit they don't want to have to commit twice and they are close to committing it let me know so I can make sure it gets in before I branch. I&