[ 
https://issues.apache.org/jira/browse/COMPRESS-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059790#comment-16059790
 ] 

Simon Spero commented on COMPRESS-413:
--------------------------------------

Compare: 
[Master| https://travis-ci.org/apache/commons-compress/builds/244058294]
- Ran for 6 min 13 sec
- Total time 14 min 15 sec

[PR| https://travis-ci.org/apache/commons-compress/builds/245887614 ]
- Ran for 4 min 31 sec
- Total time 8 min 22 sec

Further,  Oracle JDK 7 hit EOL *over 2 years* ago! 
OpenJDK 7 has seen only sporadic patching, and is no longer part of any ubuntu 
LTS release. 

It is probably worth only testing under at most one of these environments 
(also, current tests run against  really, really old versions of jdk8)




> Travis build redundantly repeats compilation and tests redundantly
> ------------------------------------------------------------------
>
>                 Key: COMPRESS-413
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-413
>             Project: Commons Compress
>          Issue Type: Improvement
>          Components: Build
>    Affects Versions: 1.14
>         Environment: Travis
>            Reporter: Simon Spero
>            Priority: Minor
>              Labels: CI
>             Fix For: 1.15
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> The Travis build setup is suboptimal.
> At the moment, code is compiled and installed by the default install phase.  
> Then the default build phase is executed, which compiles and runs the tests.
> If the tests succeed, then the build is cleaned, recompiled, and retested; 
> this time with 
> coverage enabled. 
> The .travis.yml file could be changed to skip the install phase, and to run 
> tests with coverage during the build phase. 
> The coveralls plugin can be configured in the pom  to not fail the build if 
> the service is unreachable, so forks that don't have jacoco enabled won't 
> always have their builds fail. 
> Also, the jdk switching in the trusty container seems to be not working 
> properly at the moment, so installing a jdk7 doesn't work properly.
> These changes evolved as I was poking jenkins last night.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to