sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Attila Szabo (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-3289) Add .travis.yml
Date Fri, 23 Feb 2018 22:39:01 GMT

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

Attila Szabo commented on SQOOP-3289:

Hey [~dvoros],

I would love the idea to have to finally have a working and  (apache toolchain) independent
CI/CD system.

Though if don't mind I'd like to aim for something more ambitious.

What do you think::

Would it be possible to setup travis in a way to execute automatically unit and integration
and 3rd test for trunk after every commit?

The reason why I'm asking is the following:

I do understand that for developers who prefer the Github fork way it would be much easier
to execute the unit tests with Travis compared to local one, although this solution would
barely differ from the currently existing [https://builds.apache.org/job/Sqoop-hadoop200/] solution,
and IMHO we definitely NEED a CI system where ALL of the tests are evaluated after every commit.
I've been trying to get in contact with the responsible ppl to make changes in [https://builds.apache.org/job/Sqoop-hadoop200/] though
I did not make too big achievements sadly.


Thats why I'm asking:

What about to aim for running every tests in travis?




> 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

View raw message