Dima Spivak created HBASE-16158:
-----------------------------------
Summary: 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
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
(v6.3.4#6332)
