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

Hudson commented on HBASE-20388:
--------------------------------

Results for branch master
        [build #307 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/307/]: (x) 
*{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/307//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/307//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/307//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {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
>             Fix For: 3.0.0
>
>         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)

Reply via email to