[
https://issues.apache.org/jira/browse/HBASE-19098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16221651#comment-16221651
]
Hudson commented on HBASE-19098:
--------------------------------
SUCCESS: Integrated in Jenkins build HBase-2.0 #751 (See
[https://builds.apache.org/job/HBase-2.0/751/])
HBASE-19098 compatibility checker should handle remotes named something
(busbey: rev e1152afdd45dc300da691dcb38a89f059b7d06de)
* (edit) dev-support/checkcompatibility.py
> Python based compatiblity checker fails if git repo does not have a remote
> named 'origin'
> -----------------------------------------------------------------------------------------
>
> Key: HBASE-19098
> URL: https://issues.apache.org/jira/browse/HBASE-19098
> Project: HBase
> Issue Type: Bug
> Components: tooling
> Reporter: Andrew Purtell
> Assignee: Sean Busbey
> Priority: Critical
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 2.0.0-alpha-4
>
> Attachments: HBASE-19098.0.patch
>
>
> The new Python based compatibility checker will fail if the local git repo
> does not have a remote named "origin". I develop with multiple upstream repos
> and rename them according to a custom convention. If the requirement that an
> upstream named "origin" must be present could be removed, that would be good,
> or otherwise this should be documented next to the example usage in the
> python source.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
