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

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/01/12 03:50:07 UTC

[jira] [Updated] (BEAM-1143) Timestamps on Jenkins log lines

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

Kenneth Knowles updated BEAM-1143:
----------------------------------

This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.

> Timestamps on Jenkins log lines
> -------------------------------
>
>                 Key: BEAM-1143
>                 URL: https://issues.apache.org/jira/browse/BEAM-1143
>             Project: Beam
>          Issue Type: Improvement
>          Components: testing
>            Reporter: Kenneth Knowles
>            Priority: P3
>
> I suspect this might be doable more universally in the groovy DSL scripts, but we would gain some value by a port of https://github.com/apache/incubator-beam/commit/7f82a573d00a5a30331b7bbb8757e55f4a2d93ae to the most appropriate analog for Jenkins. (in the worst case, just exactly porting the env var)
> We are currently regularly bottlenecked on build duration/backlog and the time seems to exist outside of the durations accounted for by Maven's usual output.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)