[
https://issues.apache.org/jira/browse/BEAM-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15881640#comment-15881640
]
Davor Bonaci commented on BEAM-1544:
------------------------------------
I think it would be beneficial for the project as a whole to have one CI
system, not two. Jenkins capabilities vastly exceeds those of Travis for our
use cases, so I'd love if we could deprecate Travis as soon as possible.
Jenkins has "matrix" configurations, which allows running a single job against
a matrix of configurations. This is exactly what we need here, I think.
On the other hand, thinking a bit more about the structure of the jobs would be
beneficial *before* adding the matrix. For example, breaking up the tests
across Java vs. Python first would be good (e.g., running Python tests against
multiple JDKs is not particularly beneficial ;-) ).
> Move Java cross-JDK tests from Travis to Jenkins
> ------------------------------------------------
>
> Key: BEAM-1544
> URL: https://issues.apache.org/jira/browse/BEAM-1544
> Project: Beam
> Issue Type: Task
> Components: build-system, testing
> Reporter: Mark Liu
> Assignee: Mark Liu
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
