Hey everyone, I’ve created a GitHub Action that sets up a Julia environment as a base for CI and other automation tasks. The action lets you setup 32- and 64-bit Julia environments on all supported OSes (Windows Server 2016 & 2019, Ubuntu 16.04 & 18.04 and macOS X Mojave 10.14). It still lacks so…

If you’ve tried them out or are interested in actions, I’d like to hear some input on the following issue that came up about what package CI workflows should look like: https://github.com/julia-actions/julia-runtest/issues/1

I have completely moved StringBuilders.jl over to use these new GitHub Actions for its CI testing. So far so good. It seems really fast, plus we get Windows, Mac and Linux all in one service (and all running in parallel). The current configuration looks like this . Just be warned: we are still tink…

The current configuration looks like this . got 404 :sob:

Unfortunately, there seems to be an issue with the julia-actions/julia-uploadcodecov, see, for instance, GitHub - JuliaGeometry/CoordinateTransformations.jl: A fresh approach to coordinate transformations... . Coverage reports don’t get uploaded. Is there any solution to this? Should I file an issue…

I’ve actually moved away from the julia-uploadcodecov action and am using the native codecov action instead. Main benefit is that it should work without a token in many cases. You can take a look at what I’m using right now here .

This thread makes it look easy to switch from travis … to github actions. I’m thinking about doing this and am still confused. I almost understand things well enough (I got Greetings Octocat to work) to do the experiment, but don’t want to break what I already have. Do the normal things (CI + codec…

Novice question: You have docdeploy as a separate .yml file. Is that the optimal way to do this? Are you using Documenter.jl? I don’t see the references to version numbers that I would in a .travis.yml file. Is all this encoded in julia-actions/julia-docdeploy@releases/v1? The example from https:/…

[image] ctkelley: Do the normal things (CI + codecov + documenter) “just work” if one makes the obvious changes and follows the templates from @davidanthoff and @SaschaMann ? For most packages, they should “just work”. The examples in this thread may be a bit outdated, I personally would use P…

I got the template from Documenter.jl to work with minimal tweaking. I’m amazed at how much faster my docs are processed now. Very happy so far. Having doc.yml as a stand-alone file makes this stuff easier to keep track of as well.

Using Julia in GitHub Actions

Tooling

SaschaMann December 16, 2019, 3:04pm 5

PkgTemplates.jl has up-to-date example workflows: Testing & Coverage, Testing & Docs deployment

Travis CI changes pricing plans

Topic		Replies	Views
Easy workflow file for setting up GitHub Actions CI for your Julia package Tooling ci , github-actions	77	10481	September 18, 2021
Julia CI (github actions with codecov) setup for package development Package Management question , package	1	1423	February 13, 2022
Best way to Continuous Integration and Automated Tests Package Management git , travis , codecov , github , github-actions	6	2012	September 20, 2021
GitHub actions CI using CodeCov code coverage General Usage question , codecov , ci , github-actions	2	2360	November 20, 2020
Github-action-benchmark with Julia support General Usage ci , github-actions	0	738	December 4, 2021

Using Julia in GitHub Actions

Related topics