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

Radoslav Husar (JIRA) issues at jboss.org
Fri Jun 17 12:24:00 EDT 2016


    [ https://issues.jboss.org/browse/MODCLUSTER-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254233#comment-13254233 ] 

Radoslav Husar commented on MODCLUSTER-485:
-------------------------------------------

Note for JDK7 we need to use this workaround:

{noformat}
# Workaround openjdk6/7 crashes in container-based environments failing with:
# *** buffer overflow detected ***: /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java terminated
# /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64/libnet.so(Java_java_net_Inet4AddressImpl_getLocalHostName+0x190)[0x7fde947f34a0]
sudo: required
addons:
  hostname: localhost
{noformat}

> Move CI to Travis
> -----------------
>
>                 Key: MODCLUSTER-485
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-485
>             Project: mod_cluster
>          Issue Type: Task
>            Reporter: Radoslav Husar
>            Assignee: Radoslav Husar
>
> -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, taking master into account support for legacy containers has been dropped so now we have:
> * jdk7 + 8 and everything in default (excludes Tomcat 9) -> 3 combos on travis 
> * jdk 8 + Tomcat 9 -> 1 combo on travis
> See http://tomcat.apache.org/whichversion.html



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


More information about the mod_cluster-issues mailing list