Specifying Travis CI versions

package
development
travis

#1

How do I select which Julia version to use if it isn’t tagged? For example, if instead of using the nightly I want to use a previous Dev-version by the version number of commit.

Can one specify to checkout certain packages rather than use the default Require \to Pkg.add?


#2

I wonder what the value is of testing against an old 0.7 commit? Do you need a feature of 0.7 but don’t want to spend time to keep your package working against the current master?


#3

Valid point. There were some packages which broke after a certain commit of the master. For example, Conda is currently broken in the nightly. In an ideal situation were all packages (dependencies) can keep up with breaking changes it would be true, but sometimes there it is beneficial to develop using that intermediate stage until the dependencies catch up.

As for packages, currently this solution works in test/runtests.jl

Pkg.rm("C")
Pkg.rm("C")
Pkg.rm("B")
Pkg.rm("B")
Pkg.rm("A")
Pkg.rm("A")
Pkg.clone("A")
Pkg.clone("B")
Pkg.clone("C")

using C
using module

using Test

is there a way to indicate the version or branch rather than having to remove and clone it again?


#4

Pkg.checkout?


#5

Would work if the branch is at the source project. I would prefer having the flexibility of providing my own developing fork for testing though.


#6

You would have to build Julia on your own using the sha to checkout the specific version and the using that version of Julia to test your package.


#7

That kinda beats the purpose of the C.I., but since it would only be temporary I think it would be alright. Thanks, y’all.