[jira] [Resolved] (COMPRESS-413) Travis build redundantly repeats compilation and tests redundantly

["Gary Gregory (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/COMPRESS-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Gregory resolved COMPRESS-413.
-----------------------------------
    Resolution: Fixed

Thank you for the PR. Patch applied except for the removal of Oracle 7 and 8 from the Travis build.

Please verify and close or continue.

I only see 1 error and one failure now instead of a bunch:

{noformat}
Failed tests:
  X5455_ExtendedTimestampTest.testSampleFile:185 expected:<[2105-01-01/00:00:02] +0000> but was:<[1968-11-24/17:31:45] +0000>
Tests in error:
  ZCompressorInputStreamTest.testFailsToCreateZCompressorInputStreamAndThrowsIOException ╗

Tests run: 842, Failures: 1, Errors: 1, Skipped: 4
{noformat}

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