sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Voros (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-3289) Add .travis.yml
Date Fri, 09 Mar 2018 17:18:00 GMT

    [ https://issues.apache.org/jira/browse/SQOOP-3289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16393199#comment-16393199
] 

Daniel Voros commented on SQOOP-3289:
-------------------------------------

Hi [~BoglarkaEgyed],

Thanks for you review! In the meantime I've started fooling around with thirdparty tests in
Travis. Thought I'll share the current status so you can comment on that early on. For the
latest results, please check this build: https://travis-ci.org/dvoros/sqoop/builds/351353673

cc [~vasas] [~maugli]



> 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
(v7.6.3#76005)

Mime
View raw message