GitHub user aaltay opened a pull request:

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

    Move Jenkins Python post commit script to the repository.

    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](https://www.apache.org/licenses/icla.txt).
    
    ---
    
    This is a copy of the script Jenkins post commit Python verify job is
    running (with some cosmetic changes, license and instructions.) Moving
    it to the repo so that we can track changes to it.
    
    Jenkins will be updated to call this script instead of keeping a copy
    of it as part of its configuration.

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

    $ git pull https://github.com/aaltay/incubator-beam jenkins

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

    https://github.com/apache/incubator-beam/pull/571.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 #571
    
----
commit da80522e76b4e4e3af9090108c7a5465279b79e4
Author: Ahmet Altay <[email protected]>
Date:   2016-07-01T00:02:59Z

    Move Jenkins Python post commit script to the repository.
    
    This is a copy of the script Jenkins post commit Python verify job is
    running (with some cosmetic changes, license and instructions.) Moving
    it to the repo so that we can track changes to it.
    
    Jenkins will be updated to call this script instead of keeping a copy
    of it as part of its configuration.

----


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

Reply via email to