action-tmate
cache
action-tmate | cache | |
---|---|---|
13 | 40 | |
2,652 | 4,264 | |
- | 1.5% | |
5.5 | 7.2 | |
19 days ago | 8 days ago | |
JavaScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
action-tmate
-
How to debug GitHub actions. Real-world example
The go-to method of debugging GitHub Actions is tmate. With tmate we can connect to our running Action terminal and see what is going on there by executing some simple commands!
-
GitHub Actions Are a Problem
In addition to the suggestions others have made for locally testing workflows, there are also reverse shell actions[0] that can be used for troubleshooting CI failures on the GH runners themselves.
[0] https://github.com/mxschmitt/action-tmate
-
GitHub Actions could be so much better
Been through that git commit; git push; repeat cycle too much as well until i discovered https://github.com/mxschmitt/action-tmate which gives a shell in between steps, which does not help with all problems but sure it's makes it less painful at times.
- How do you debug CI/CD pipelines? Breakpoints?
-
How easy is it to troubleshoot GHA workflows?
In addition to everything here, I also will set up https://github.com/mxschmitt/action-tmate when Iām debugging. It helps tremendously since you can temporarily access the server.
-
Act: Run your GitHub Actions locally
Unfortunately act is only capable of running very simple workflows. I've found this action to be more useful against the endless PR stream: https://github.com/mxschmitt/action-tmate
You drop it in your workflow and get an SSH shell into the worker, figure things out iteratively, then push when it's working.
-
CI/CD using GitHub Actions for Rails and Docker
Solution: Tip o' the hat to Daniela Baron here, there's a real life saver of tool call tmate.
-
Hosting VMs on GitHub Actions?
Here's a recent case where users of tmate - which lets you SSH into an actions worker - reported problems: https://github.com/mxschmitt/action-tmate/issues/104
-
Github actions error while pushing code to package registry
see: https://github.com/mxschmitt/action-tmate
-
Work with GitHub Actions in Your Terminal with GitHub CLI
Thought I'd get their docs updated - https://github.com/mxschmitt/action-tmate#manually-triggered...
cache
-
GitHub Actions could be so much better
> with no persistent storage
There's https://github.com/actions/cache though?
-
Optimizing GitHub Actions Performance: Enhance Workflows with Caching
Use Cache Actions: GitHub Actions provides cache actions that simplify caching implementation. The @actions/cache JavaScript library is a popular choice for managing caching in workflows. It offers flexible options for storing and retrieving cache artifacts based on keys, scopes, and paths.
-
Speeding up GitHub Actions with npm cache
GitHub maintain a set of repos called actions. One of which is called cache.
-
How I Sliced Deployment Times to a Fraction and Achieved Lightning-Fast Deployments with GitHub Actions
By utilizing the actions/cache action action, we implemented a strategy to store and retrieve dependencies, preventing redundant installations.
-
Use GitHub Actions to Make Your GitHub Profile Dynamic
I do think it's good practice to enable caching, such that your script doesn't hit RubyGems / pip / npm / etc every time it runs.
That way at least the automation activity stays entirely within the GitHub / Azure network.
It looks like you can do that for Ruby by adding this:
https://github.com/actions/cache/blob/master/examples.md#rub...
- uses: ruby/setup-ruby@v1
-
A guide to using act with GitHub Actions
ā getting-started-with-act git:(master) act -j build WARN ā You are using Apple M1 chip and you have not specified container architecture, you might encounter issues while running act. If so, try running it with '--container-architecture linux/amd64'. ā [Node.js CI/build] š Start image=node:16-buster-slim [Node.js CI/build] š³ docker pull image=node:16-buster-slim platform= username= forcePull=false [Node.js CI/build] š³ docker create image=node:16-buster-slim platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] [Node.js CI/build] š³ docker run image=node:16-buster-slim platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] [Node.js CI/build] ā git clone 'https://github.com/actions/setup-node' # ref=v3 [Node.js CI/build] ā git clone 'https://github.com/actions/cache' # ref=v3 [Node.js CI/build] ā git clone 'https://github.com/actions/upload-artifact' # ref=v3 [Node.js CI/build] ā Run Main actions/checkout@v3 [Node.js CI/build] š³ docker cp src=/Users/andrewevans/Documents/projects/getting-started-with-act/. dst=/Users/andrewevans/Documents/projects/getting-started-with-act [Node.js CI/build] ā Success - Main actions/checkout@v3 [Node.js CI/build] ā Run Main Use Node.js 16.x [Node.js CI/build] š³ docker cp src=/Users/andrewevans/.cache/act/actions-setup-node@v3/ dst=/var/run/act/actions/actions-setup-node@v3/ [Node.js CI/build] š³ docker exec cmd=[node /var/run/act/actions/actions-setup-node@v3/dist/setup/index.js] user= workdir= [Node.js CI/build] š¬ ::debug::isExplicit: [Node.js CI/build] š¬ ::debug::explicit? false
- duplicated cache by cache action
-
runner image with MS office installed - do-able? is there a better way?
You could try to find some point in the process where you can set up Actions caches with actions/cache, otherwise Container customization for Self-Hosted Runners is currently in Beta.
-
[Question] Decrease Docker image's build time
I would configure Github Actions cache so Docker doesn't have to compile all layers from scratch every time
-
The strongest principle of the blog's growth lies in the human choice to deploy it
In the copied example, npm caching is done via actions/cache@v2 action. But we can simplify our workflow by dropping this step and using built-in functionality for caching
What are some alternatives?
reverse-rdp-windows-github-actions - Reverse Remote Desktop into Windows on GitHub Actions for Debugging and/or Job Introspection [GET https://api.github.com/repos/nelsonjchen/reverse-rdp-windows-github-actions: 403 - Repository access blocked]
upload-artifact
act - Run your GitHub Actions locally š
sccache - Sccache is a ccache-like tool. It is used as a compiler wrapper and avoids compilation when possible. Sccache has the capability to utilize caching in remote storage environments, including various cloud storage options, or alternatively, in local storage.
floatly - An extension that adds a floating button for browser quick actions
mongodb-github-action - Use MongoDB in GitHub Actions
actions-runner-controller - Kubernetes controller for GitHub Actions self-hosted runners
github-activity-readme - Updates README with the recent GitHub activity of a user
setup-buildx-action - GitHub Action to set up Docker Buildx
ssh-agent - GitHub Action to setup `ssh-agent` with a private key
checkout - Action for checking out a repo