hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16158) Automate runs of check_compatibility.sh on upstream infra
Date Fri, 01 Jul 2016 00:20:10 GMT

    [ https://issues.apache.org/jira/browse/HBASE-16158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15358094#comment-15358094

Andrew Purtell commented on HBASE-16158:

bq. 0.98.0 and branch 0.98

This is not a problem, we've made documented changes along the way release to release. You
can refer to RC votes for detail. The interesting information is from the last release to
current SNAPSHOT

> Automate runs of check_compatibility.sh on upstream infra
> ---------------------------------------------------------
>                 Key: HBASE-16158
>                 URL: https://issues.apache.org/jira/browse/HBASE-16158
>             Project: HBase
>          Issue Type: Task
>          Components: test
>            Reporter: Dima Spivak
> Now that we got {{check_compatiblity.sh}} working again, perhaps we should think about
having it run regularly upstream? One possibility would be to tie it into Yetus runs so that
the tool gets run on every commit between the branch in question and a designated Git reference
(e.g. branch-1.2 could run against the earlier release of the 1.2 line) and simply grepping
the output to make sure that the number of problems and warnings doesn't exceed a designated
number. The other would be to run every branch in its own Jenkins job following the same workflow,
but on a nightly basis. What do you guys and gals think would be best?

This message was sent by Atlassian JIRA

View raw message