Hey folks, an announcement for package authors and users who care about 
testing:

We've had support for Julia package testing on Travis CI 
<http://travis-ci.org> for almost 9 months now, 
ref https://groups.google.com/forum/#!msg/julia-users/BtCxh4k9hZA/ngUvxdxOxQ8J 
if you missed the original announcement. Up to this point we supported the 
following settings for which Julia version to test against:

    language: julia
    julia:
        - release
        - nightly

Release has meant the latest release version in the 0.3.x series, and 
nightly has meant the latest nightly build of 0.4-dev master. Once Julia 
0.4.0 gets released, the meaning of these settings will change, where 
release will be the latest version in the 0.4.x series, and nightly will be 
the latest nightly build of 0.5-dev master. Considering the wide install 
base and number of packages that may want to continue supporting 0.3 even 
after 0.4.0 gets released, we've just added support for additional version 
options in your .travis.yml file. You can now do

    julia: 
        - release
        - nightly
        - 0.3

Or, if you want to test with specific point releases, you can do that too 
(there should not usually be much need for this, but it could be useful 
once in a while to compare different point releases):

    julia: 
        - release
        - nightly
        - 0.3
        - 0.3.10

The oldest point release for which we have generic Linux binaries available 
is 0.3.1. If you enable multi-os support for your repository 
(see http://docs.travis-ci.com/user/multi-os/), then you can go back as far 
as 0.2.0 on OS X. Note that you'd need to replace the default test script 
with the old-fashioned `julia test/runtests.jl` since `Pkg.test` and 
`--check-bounds=yes` are not supported on Julia version 0.2.x. The 
downloads of those versions would fail on Linux workers so you may need to 
set up a build matrix with excluded jobs 
(see http://docs.travis-ci.com/user/customizing-the-build/#Build-Matrix).

Let us know if you have any questions or issues.

Happy testing,
Tony (with thanks to @ninjin and @staticfloat for PR review)

Reply via email to