My first brief impressions on Github Actions CI/CD solution launched a while ago.

The runner VMs (Ubuntu et al.) contain plenty of preinstalled software enough to cover most of the needs. There is, e.g. Chrome browser for enabling automated end-to-end testing, if you're into that, and why shouldn't you be.


- All relevant languages are supported. The marketplace already has a ton of actions built by other users so expect this to grow tremendously.

Caching and build matrices work as expected, and after a few pipelines, you get builds rolling pretty fast.

You can share build artefacts between jobs which makes deploying static sites and compiled binaries easy.

YAML syntax is not too hard, and you can quickly write it with realtime linting on Github's UI

Feedback for failed builds is swiftly provided via email so you can stop what you were doing and make the build green again. The downside is those will quickly fill up your inbox without custom rules.

In overall, if you're satisfied with, say, Travis, Semaphore, or Gitlab CI solutions, there is little need to jump the ship as it won't offer you any remarkable benefits as of now. It's terrific to see Github providing their in-house CI solutions, though, keeping the competition going strong.

Sign in to participate in the conversation
Mastodon for Tech Folks

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!