beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ssisk <>
Subject [GitHub] beam pull request #2466: [BEAM-1644] Move travis & jenkins into shared test-...
Date Fri, 07 Apr 2017 23:15:14 GMT
GitHub user ssisk opened a pull request:

    [BEAM-1644] Move travis & jenkins into shared test-infra dir, and move k8s scripts

    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](
    Reasoning is discussed in the bug, but generally, we want to have a language neutral place
for these kubernetes scripts to live, and also don't want a million top level directories
for test-infra
    cc @jasonkuster 

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

    $ git pull create-k8s-home

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 #2466
commit 617297662e2649f5e38f5c4ae9047f7e9bcecbe8
Author: Stephen Sisk <>
Date:   2017-04-07T22:57:33Z

    Move travis/jenkins folders in a test-infra folder

commit 4cd666c5026ef91121a5cf7c6786c21c8d39d904
Author: Stephen Sisk <>
Date:   2017-04-07T23:06:15Z

    Move jdbc's postgres k8s scripts into shared k8s dir

commit 3468cec566bd24164922c0c063067d90e1c43849
Author: Stephen Sisk <>
Date:   2017-04-07T23:11:19Z

    Move HIFIO k8s scripts into shared dir


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