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

Sean Busbey commented on HBASE-18467:
-------------------------------------

pretty blocks that a) run later stages even when earlier stages fail and b) 
being able to see which blocks specifically falied in the UI. that's something 
we didn't get with my approach in v1-v4 posted here so far.

I have, of course, now discovered an error in the jira comment that is to be 
posted. I'm cleaning that up and then I'll do a run that actually runs the 
tests to make sure they execute. will hopefully have something to post here 
tonight.

Bonus side improvement should be that these run in parallel when there are 
spare executors, which could mean ~2hrs instead of ~7hrs.

> 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
>         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
>
>
> 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