|
|
|
|
|
by zomglings
1861 days ago
|
|
In the last week, there have been at least two ~1 hour periods where actions were stuck in the queue. Even posted about this on the GitHub community, but no response. [0] As unreliable as GitHub Actions are, their convenience factor and price are right. We take a very simple measure so we don't get fucked by these kinds of incidents: we don't use any actions from the marketplace. All our GitHub Actions workflows are bash scripts that we wrote (and which often live in our repos at `deploy/deploy.bash`). The secrets necessary to run these scripts are available to the infrastructure team on 1Password. This makes it easy for us to deploy manually and retroactively reflect that release on GitHub (e.g. through a tag or a release). [0] https://github.community/t/github-action-stuck-on-starting-w... |
|
The portability could be fixed by having a local cli runner that understand action yamls. Would be interesting to explore this.
For a while i have been fantasizing about an universal pipeline language. Like having LLVM with a unified model that can translate into different vendor implementations.