[ https://issues.apache.org/jira/browse/HBASE-20388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438603#comment-16438603 ]
Hudson commented on HBASE-20388: -------------------------------- Results for branch HBASE-20388 [build #7 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-20388/7/]: (x) *{color:red}-1 overall{color}* ---- details (if available): (x) {color:red}-1 general checks{color} -- Something went wrong running this stage, please [check relevant console output|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-20388/7//console]. (x) {color:red}-1 jdk8 hadoop2 checks{color} -- Something went wrong running this stage, please [check relevant console output|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-20388/7//console]. (/) {color:green}+1 source release artifact{color} -- See build output for details. > nightly tests running on a feature branch should only comment on that feature > branch's jira > ------------------------------------------------------------------------------------------- > > Key: HBASE-20388 > URL: https://issues.apache.org/jira/browse/HBASE-20388 > Project: HBase > Issue Type: Improvement > Components: community, test > Reporter: Sean Busbey > Assignee: Sean Busbey > Priority: Major > Attachments: HBASE-20388.0.patch, HBASE-20388.1.patch, > HBASE-20388.2.patch > > > It would help improve our signal-to-noise ratio from nightly tests if feature > branch runs stopped commenting on all the jiras that got covered by a rebase > / merge. > should be straight forward to have the commenting bit check the current > branch against our feature branch naming convention. -- This message was sent by Atlassian JIRA (v7.6.3#76005)