Sean Busbey updated HBASE-18467:
    Status: Patch Available  (was: In Progress)

-7 addendum to committed v6
  - have parallel stages do an scm checkout (cause of the current failure on 
all branches with v6)
  - ensure the yetus install job runs on an appropriate label (we hit windows 
once and it did not go well)
  - copy jira comments back to the main workspace (cause of the confusing jira 
comments with -1 overall but no detail reason
  - simplify the jira comment a bit
  - see just before here for example updated jira comment that came from [build 
#15 on a test 

wdyt [~mdrob]?

[~stack] you fine with me updating branch-2 to match everywhere else for 
nightlies after this addendum? branch-2.0?

> 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: 3.0.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

Reply via email to