JuliaLang
Update the CI
The example showcases how to set up the CI using Travis CI (GitHub app), Codecov, and Documenter.
Codecov Report
:exclamation: No coverage uploaded for pull request base (
master@f968c69). Click here to learn what that means. The diff coverage isn/a.
@@ Coverage Diff @@
## master #47 +/- ##
=======================================
Coverage ? 100%
=======================================
Files ? 1
Lines ? 2
Branches ? 0
=======================================
Hits ? 2
Misses ? 0
Partials ? 0
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact),ø = not affected,? = missing dataPowered by Codecov. Last update f968c69...b32b018. Read the comment docs.
Codecov Report
:exclamation: No coverage uploaded for pull request base (
master@f968c69). Click here to learn what that means. The diff coverage isn/a.
@@ Coverage Diff @@
## master #47 +/- ##
=======================================
Coverage ? 100%
=======================================
Files ? 1
Lines ? 2
Branches ? 0
=======================================
Hits ? 2
Misses ? 0
Partials ? 0
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact),ø = not affected,? = missing dataPowered by Codecov. Last update f968c69...b32b018. Read the comment docs.
It is using Travis to run Windows x64/x86 jobs. Those jobs are a bit slower at the moment, but that way it just needs one CI service that runs all the test matrix (linux, osx, win / 64-bit and 32-bit infrastructures).
I agree. In my experience setting up AppVeyor is tricky, I can never remember how to do it. Also organizations cannot have accounts, which is a problem when there are several maintainers or when the original maintainer steps back.
In my experience setting up AppVeyor is tricky, I can never remember how to do it.
It really isn't anymore, it is IMO much easier than Travis if you use AppVeyor.jl.
Also organizations cannot have accounts, which is a problem when there are several maintainers or when the original maintainer steps back.
This is not true anymore. I set it up for JuliaSparse some 5 months ago for Metis.jl: https://github.com/JuliaSparse/Metis.jl
OK, nice to hear. Still setting up two CI services is more work than setting up a single one, and Travis CI is the only one to support Windows, Linux and Mac currently.
Anyway we could keep the script, and just note that people don't need to enable both.
Technically Azure also allows for all three OS / architectures, but currently it is pretty involved. Keeping the AppVeyor script seems like it would be more confusing than the potential benefit. How about putting a comment on how other CI are available and we can link to the documentation for setting up AppVeyor and Azure?