commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Spero (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COMPRESS-413) Travis build redundantly repeats compilation and tests redundantly
Date Sun, 25 Jun 2017 00:37:00 GMT

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

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

I'll strip out the AsiExtraField foo.  I just have the strategic reserve of coverage increasers
for coverall-shutting-up. 

My main issue with Java 7 compatibility is that the primary use case  now is some older android
releases (which can't do Java 8 default/static methods), but android compatibility testing
at its most basic requires using a different animal-sniffer scent (anything else is difficult
without gradle). 

> 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)

Mime
View raw message