beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kennknowles <...@git.apache.org>
Subject [GitHub] incubator-beam pull request #1659: [BEAM-1143] More escaping in Jenkins time...
Date Mon, 19 Dec 2016 19:43:30 GMT
GitHub user kennknowles opened a pull request:

    https://github.com/apache/incubator-beam/pull/1659

    [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](https://www.apache.org/licenses/icla.txt).
    
    ---
    
    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 https://github.com/kennknowles/incubator-beam jenkins-timestamps

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

    https://github.com/apache/incubator-beam/pull/1659.patch

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 <klk@google.com>
Date:   2016-12-19T19:39:29Z

    More escaping in Jenkins timestamp spec

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message