beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-1143) Timestamps on Jenkins log lines
Date Mon, 19 Dec 2016 19:43:58 GMT


ASF GitHub Bot commented on BEAM-1143:

GitHub user kennknowles opened a pull request:

    [BEAM-1143] More escaping in Jenkins timestamp spec

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [x] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [x] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [x] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [x] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](
    The current timestamp spec is insufficiently escaped. The failure mode is that relative
timestamps are shown instead of a readable standard datetime.

You can merge this pull request into a Git repository by running:

    $ git pull jenkins-timestamps

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1659
commit 627ccb522d7d818aebe2256246e81af2d3062d11
Author: Kenneth Knowles <>
Date:   2016-12-19T19:39:29Z

    More escaping in Jenkins timestamp spec


> Timestamps on Jenkins log lines
> -------------------------------
>                 Key: BEAM-1143
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: testing
>            Reporter: Kenneth Knowles
>            Assignee: Jason Kuster
>            Priority: Minor
> I suspect this might be doable more universally in the groovy DSL scripts, but we would
gain some value by a port of
to the most appropriate analog for Jenkins. (in the worst case, just exactly porting the env
> 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

View raw message