beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kennknowles <>
Subject [GitHub] incubator-beam pull request #791: Cache .m2 directory on Travis-CI
Date Thu, 04 Aug 2016 22:23:35 GMT
GitHub user kennknowles opened a pull request:

    Cache .m2 directory on Travis-CI

    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](
    Travis is approaching a 100% failure rate, between the 4 items in the test matrix. This
is one attempt to speed it up.
    The downside of this one is that if we are worried about cache corruption, we can only
clear it via infra ticket or pushing temp commits that deliberately cache an empty m2. We
can disable the cache any time.
    I'll push a rebase to this in a while to kick the build and see what the savings look
    R: @dhalperi 

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

    $ git pull travis-cache

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 #791
commit d3edf26d17ca481b8db1d5e1aa79afbad1474096
Author: Kenneth Knowles <>
Date:   2016-08-04T22:12:03Z

    Cache .m2 directory on Travis-CI


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