[
https://issues.apache.org/jira/browse/HBASE-12944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297907#comment-14297907
]
Enis Soztutar commented on HBASE-12944:
---------------------------------------
The job failed because the following is not in branch-1. The jenkins env is
still not fixed regarding the bash issue, so I'll just backport that commit
into all applicable branches (let me do branch-1 first though).
{code}
commit aa71a8b9b9a0290c3e2bdcb4d2975ac778e28101
Author: Enis Soztutar <[email protected]>
Date: Thu Jul 17 17:35:14 2014 -0700
Commented out smart -p0 handling in dev-support/smart-apply-patch.sh until
we fix our jenkins env
{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-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)
