[
https://issues.apache.org/jira/browse/HBASE-12944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14298105#comment-14298105
]
Enis Soztutar commented on HBASE-12944:
---------------------------------------
One more commit was needed it seems:
{code}
commit c61c17b6f8ed5009174633171d2299301de571d9
Author: Enis Soztutar <[email protected]>
Date: Thu Jan 29 18:13:05 2015 -0800
HBASE-12944 Support patches to branches in precommit jenkins build
(ADDENDUM to fix branch name parsing)
{code}
> Support patches to branches in precommit jenkins build
> -------------------------------------------------------
>
> Key: HBASE-12944
> URL: https://issues.apache.org/jira/browse/HBASE-12944
> Project: HBase
> Issue Type: New Feature
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Fix For: 2.0.0
>
> Attachments: hbase-12944.patch, hbase-12944.patch,
> test-hadoopqa-0.94.patch, test-hadoopqa-0.98.patch,
> test-hadoopqa-branch-1.patch, test-hadoopqa-branch-1.patch,
> test-hadoopqa-branch-1.patch, test-hadoopqa-branch-1.patch
>
>
> We have a quite a few active branches now, which makes backporting a full
> time job.
> I was thinking about whether we can get hadoopqa to test the patches specific
> to branches with the code from that branch. I think we can grab the branch
> name from the patch file name and check out that branch prior to running the
> tests. I have a patch, but not sure whether it will work. Let me experiment a
> bit. If hadoopqa gets broken, it is probably this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
