You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2019/03/22 16:21:00 UTC

[jira] [Updated] (HBASE-22088) Jenkins post-build step times out after HBASE-20522

     [ https://issues.apache.org/jira/browse/HBASE-22088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-22088:
--------------------------
    Description: 
The post Jenkins step timesout (takes 9 hours) after HBASE-22052 (the parent) was committed. Its hard to see why since don't have access to jenkins build box logs. I asked for access. Until it arrives going to mess around here.

 * What about HBASE-20522 made it so post step takes forever?
 * The post step is archiving and publishing an html report. At first I blamed the publishHMTL plugin but I think instead it the archiving step just before. HBASE-20522 made the build output way bigger? Let me get some signal....

  was:The post Jenkins step timesout (takes 9 hours) after HBASE-22052 (the parent) was committed. Its hard to see why since don't have access to jenkins build box logs. I asked for access. Until it arrives going to mess around here.


> Jenkins post-build step times out after HBASE-20522
> ---------------------------------------------------
>
>                 Key: HBASE-22088
>                 URL: https://issues.apache.org/jira/browse/HBASE-22088
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: stack
>            Priority: Major
>
> The post Jenkins step timesout (takes 9 hours) after HBASE-22052 (the parent) was committed. Its hard to see why since don't have access to jenkins build box logs. I asked for access. Until it arrives going to mess around here.
>  * What about HBASE-20522 made it so post step takes forever?
>  * The post step is archiving and publishing an html report. At first I blamed the publishHMTL plugin but I think instead it the archiving step just before. HBASE-20522 made the build output way bigger? Let me get some signal....



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