[
https://issues.apache.org/jira/browse/HBASE-22155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16811111#comment-16811111
]
Sean Busbey commented on HBASE-22155:
-------------------------------------
pruning the remote means that now it doesn't try to update for a branch named
"2" but it still kept the local branch named "2" which still causes the branch
checking to fail.
I'm going to temporarily tell it to just start a new git clone. I don't know if
the job will need to run on all the hosts before this fixes all of them; nor a
good way to just use it until that happens.
builds will be slower so long as this option is on. I'll try leaving it on for
today and we can see if things fall over again when we turn it off?
> Move 2.2.0 on to hbase-thirdparty-2.2.0
> ---------------------------------------
>
> Key: HBASE-22155
> URL: https://issues.apache.org/jira/browse/HBASE-22155
> Project: HBase
> Issue Type: Sub-task
> Components: thirdparty
> Reporter: stack
> Assignee: stack
> Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: HBASE-22155-branch-2.2-001.patch,
> HBASE-22155-branch-2.2-001.patch, HBASE-22155-branch-2.2-001.patch,
> HBASE-22155-branch-2.2-001.patch, HBASE-22155-branch-2.2.004.patch,
> HBASE-22155-branch-2.2.v004.patch, HBASE-22155.branch-2.2.001.patch,
> HBASE-22155.branch-2.2.002.patch, HBASE-22155.branch-2.2.003.patch,
> HBASE-22155.branch-2.2.004.patch, HBASE-22155.branch-2.2.005.patch
>
>
> hbase-thirdparty-2.2.0 was just released. The 2.2.0 RM ([~zghaobac]) gave his
> blessing in parent issue that 2.2.0 should use thirdparty 2.2.0.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
