Re: Travis CI build improvements

On 2017-04-17 at 17:02:46 +0000, Fields, Christopher J wrote:
> More than happy to have you help out.  Can you do this through a pull request (I know these are tested via travis)?  Or would you need direct commit access?

Yes, I can do it all through a pull request. I can also set it up on a
fork and demonstrate the steps needed to enable the services.

As for the tests that require the network or optional dependencies, it
is possible to enable different builds conditionally. I believe the best
approach for the ones that require networking would be to create a
special branch that enables those tests. This branch can just be rebased
off the current master branch whenever a new release is uploaded.

Regards,
- Zakariyya Mughal

> 
> chris
> 
> On 4/17/17, 11:15 AM, "Bioperl-l on behalf of Zakariyya Mughal" <[email protected] on behalf of [email protected]> wrote:
> 
>     Hello,
>     
>     I noticed the Travis CI configuration could use some work. I suggest
>     taking a look at <https://github.com/travis-perl/helpers> since it can
>     automatically install all the dependencies and send the coverage to
>     Coveralls.
>     
>     We could additionally look at automatically building on Windows (using
>     Appveyor) and macOS (using Travis CI) as well.
>     
>     I helped the PDL project improve their builds and coverage in the past
>     using the same tools.
>     
>     Regards,
>     - Zakariyya Mughal
>     _______________________________________________
>     Bioperl-l mailing list
>     [email protected]
>     http://mailman.open-bio.org/mailman/listinfo/bioperl-l
>     
>