beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jasonkuster <>
Subject [GitHub] beam pull request #2709: Dummy change to trigger jenkins
Date Fri, 28 Apr 2017 05:46:50 GMT
GitHub user jasonkuster reopened a pull request:

    Dummy change to trigger jenkins

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

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

    $ git pull dummy

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 #2709
commit 7a636618f4b66380024953fea81db077f01ad5a8
Author: Jason Kuster <>
Date:   2017-04-26T00:42:10Z

    Dummy change to trigger jenkins
    Signed-off-by: Jason Kuster <>

commit 620d9be978f2759554581e4e2b66174741fd384a
Author: Jason Kuster <>
Date:   2017-04-26T01:14:42Z

    another dummy change
    Signed-off-by: Jason Kuster <>


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 or file a JIRA ticket
with INFRA.

View raw message