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

Do the hadoop jenkins scripts use some regex match on 'target version' to identify the branch to be used ? On Wed, Jun 3, 2015 at 12:17 PM, Vinod Kumar Vavilapalli < vino...@hortonworks.com> wrote: > Hadoop uses a "Target Version" field. Not sure if this was done for all > projects. > > +Vinod

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

Hadoop uses a "Target Version" field. Not sure if this was done for all projects. +Vinod On Jun 3, 2015, at 9:16 AM, Alan Gates mailto:alanfga...@gmail.com>> wrote: I don't think using Affects Version will work because it is used to list which versions of Hive the bug affects, unless you're p

Re: Creating branch-1

I don't think using Affects Version will work because it is used to list which versions of Hive the bug affects, unless you're proposing being able to parse affected version into branch (ie 1.3.0 => branch-1). I like the idea of customizing JIRA, though I don't know how hard it is. We could al

Re: Creating branch-1

Thanks for the insights Sergio! Using 'Affects Version' sounds like a good idea. However, for the case where it needs to be executed against both branch-1 and master, I think it would be more intuitive to use "Affects Version/s: branch-master branch-1" , as the version number in master branch w

Re: Creating branch-1

+1. Alan. Thejas Nair June 2, 2015 at 14:31 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 ? Alan Gates

Re: Creating branch-1

Hi Alan, Currently, the test system executes tests on a specific branch only if there is a Jenkins job assigned to it, like trunk or spark. Any other branch will not work. We will need to create a job for branch-1, modify the jenkins-submit-build.sh to add the new profile, and add a new properties

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

Hi Alan Is branch-1 on github already? https://github.com/apache/hive/tree/branch-1 On Tue, Jun 2, 2015 at 10:37 AM, Alan Gates wrote: > Ok, I've created branch-1. I've also updated HowToContribute with > information on what patches go where now. Proofreaders and feedback on > clarity are we

Re: Creating branch-1

Ok, I've created branch-1. I've also updated HowToContribute with information on what patches go where now. Proofreaders and feedback 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 Gate