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

Hudson commented on HBASE-18467:
--------------------------------

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

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




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/253//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/253//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


> nightly job needs to run all stages and then comment on jira
> ------------------------------------------------------------
>
>                 Key: HBASE-18467
>                 URL: https://issues.apache.org/jira/browse/HBASE-18467
>             Project: HBase
>          Issue Type: Improvement
>          Components: community, test
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Critical
>             Fix For: 2.0.0, 3.0.0, 2.1.0, 1.5.0, 1.3.3, 1.2.8, 1.4.3
>
>         Attachments: HBASE-18467.0.WIP.patch, HBASE-18467.0.patch, 
> HBASE-18467.1.patch, HBASE-18467.1.patch, HBASE-18467.2.patch, 
> HBASE-18467.3.patch, HBASE-18467.4.patch, HBASE-18467.5.patch, 
> HBASE-18467.6.patch, HBASE-18467.7.addendum.patch
>
>
> follow on from HBASE-18147, need a post action that pings all newly-committed 
> jiras with result of the branch build



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to