beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kennknowles <>
Subject [GitHub] incubator-beam pull request #1180: Use our Travis settings everywhere
Date Tue, 25 Oct 2016 02:39:54 GMT
GitHub user kennknowles opened a pull request:

    Use our Travis settings everywhere

    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](
    I believe this is a better fix for #1137

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

    $ git pull travis-settings

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 #1180
commit 0df8bbcb28fefd1e4cc658b4db7696346ed283cd
Author: Kenneth Knowles <>
Date:   2016-10-25T02:31:26Z

    Revert "Fix invalid snapshot repo in Travis CI's maven settings.xml"
    This reverts commit fbc23ed9234088c9d88bf88b19a3a4d6d5e52446.

commit 7ed8355522f34b97f5ec7ea9785df996fc0b8e1d
Author: Kenneth Knowles <>
Date:   2016-10-25T02:34:04Z

    Set up Maven settings globally for Travis CI builds


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