[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-485) Move CI to Travis

[Radoslav Husar (JIRA)]

     [ https://issues.jboss.org/browse/MODCLUSTER-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radoslav Husar updated MODCLUSTER-485:
--------------------------------------
              Status: Pull Request Sent  (was: Pull Request Sent)
    Git Pull Request: https://github.com/modcluster/mod_cluster/pull/200, https://github.com/modcluster/mod_cluster/pull/214  (was: https://github.com/modcluster/mod_cluster/pull/200)


> Move CI to Travis
> -----------------
>
>                 Key: MODCLUSTER-485
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-485
>             Project: mod_cluster
>          Issue Type: Task
>          Components: Core & Container Integration (Java)
>            Reporter: Radoslav Husar
>            Assignee: Radoslav Husar
>              Labels: CI
>             Fix For: 2.0.0.Alpha1, 1.3.4.Final
>
>
> -I ran into this while adding support for Tomcat 9.-
> -What the CI should be testing, give the number of JDKs and different container versions that we support, we should build with respective jdks and versions:-
> -jdk6 + mvn verify -PTC6-
> -jdk7 + mvn verify -PTC7-
> -jdk7 + mvn verify -PAS7-
> -jdk8 + mvn verify -PTC8-
> -jdk7/8 + mvn verify-
> The situation has changed since original proposal fixing CI with proper dependencies for tomcat versions. Taking into account support for legacy containers has been dropped  in master, so now we have desired combinations:
> * jdk7 + jdk8 and default profile (excludes Tomcat 9) -> 3 combos on travis 
> * jdk 8 + Tomcat 9 profile -> 1 combo on travis
> See http://tomcat.apache.org/whichversion.html



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)