[
https://issues.apache.org/jira/browse/HBASE-12944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14298098#comment-14298098
]
Hudson commented on HBASE-12944:
--------------------------------
FAILURE: Integrated in HBase-TRUNK #6070 (See
[https://builds.apache.org/job/HBase-TRUNK/6070/])
HBASE-12944 Support patches to branches in precommit jenkins build (ADDENDUM
moves sourcing of .properties file to start of the script) (enis: rev
a5613efa7b22a31811cd326e9ad231911afdbde2)
* dev-support/test-patch.sh
> 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)
