[
https://issues.apache.org/jira/browse/SQOOP-3289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16377212#comment-16377212
]
Attila Szabo commented on SQOOP-3289:
-------------------------------------
Hi Daniel,
Though in general the ASF community is great, IMHO it does not make too much
sense to compare one project to the other. Especially a very busy active like
Spark with something quite mature as Sqoop.
Though I think my message was clear enough, it's up to you if you willing to
wait until the current builds.apache.org build pipeline will do the real job.
Just one comment on my side :
If we won't be able to make the life of the contributors ( and the committers)
easier, any efforts on this front could be in vain.
My 2 cents,
Attila
> 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)
