Set up GitHub actions #323

2020-11-15T14:28:46+01:00

tfausak commented

2020-11-15 14:28:46 +01:00

(Migrated from github.com)

There is no content yet.

tfausak commented

2020-11-15 15:37:06 +01:00

(Migrated from github.com)

I know that Travis CI is already set up, but GitHub Actions has a couple benefits:

It's possible to test against Ubuntu, macOS, and Windows. This is also possible on Travis CI, but I feel like the GitHub Actions build runners are quicker and more reliable.
Build artifacts, like executables and package tarballs, are first class.
Subjectively, it seems like Travis CI is losing mind share and GitHub Actions is gaining it.

For the time being I'm going to leave Travis CI in place, but it does feel wasteful to have two CI pipelines.

I know that Travis CI is already set up, but GitHub Actions has a couple benefits: - It's possible to test against Ubuntu, macOS, and Windows. This is also possible on Travis CI, but I feel like the GitHub Actions build runners are quicker and more reliable. - Build artifacts, like executables and package tarballs, are first class. - Subjectively, it seems like Travis CI is losing mind share and GitHub Actions is gaining it. For the time being I'm going to leave Travis CI in place, but it does feel wasteful to have two CI pipelines.

Sign in to join this conversation.

No reviewers

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: hexagoxel/brittany#323