Daniel Voros commented on SQOOP-3289:

Thank you both for your comments! I'm convinced, let's give Travis a shot with 
the CI as well!

[~vasas] I'll start experimenting with thirdparty tests. First thing that came 
to my mind was to run the DB containers on a third-party server and use that 
from Travis. Not sure if that's better or worse from the legal perspective tho. 

> Add .travis.yml
> ---------------
>                 Key: SQOOP-3289
>                 URL: https://issues.apache.org/jira/browse/SQOOP-3289
>             Project: Sqoop
>          Issue Type: Task
>          Components: build
>    Affects Versions: 1.4.7
>            Reporter: Daniel Voros
>            Assignee: Daniel Voros
>            Priority: Minor
>             Fix For: 1.5.0
> Adding a .travis.yml would enable running builds/tests on travis-ci.org. 
> Currently if you wish to use Travis for testing your changes, you have to 
> manually add a .travis.yml to your branch. Having it committed to trunk would 
> save us this extra step.
> I currently have an example 
> [{{.travis.yml}}|https://github.com/dvoros/sqoop/blob/93a4c06c1a3da1fd5305c99e379484507797b3eb/.travis.yml]
>  on my travis branch running unit tests for every commit and every pull 
> request: https://travis-ci.org/dvoros/sqoop/builds
> Later we could add the build status to the project readme as well, see: 
> https://github.com/dvoros/sqoop/tree/travis
> Also, an example of a pull request: https://github.com/dvoros/sqoop/pull/1

This message was sent by Atlassian JIRA

Reply via email to