action-tmate
gitlab-ci-local
action-tmate | gitlab-ci-local | |
---|---|---|
13 | 10 | |
2,652 | 1,880 | |
- | - | |
5.5 | 9.1 | |
19 days ago | 2 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...
gitlab-ci-local
-
š¦ GitLab CI YAML Modifications: Tackling the Feedback Loop Problem
Among these options, the one that has gained the most traction is gitlab-ci-local :
-
š¦ GitLab CI: 10+ Best Practices to Avoid Widespread Anti-patterns
The main reason behind this change is to have consistent scripts for local testing and remote runners during testing and debugging. However, there are already tools available, such as gitlab-ci-local, that allow you to run jobs locally, partially invalidating this argument. Additionally, working locally may not provide access to all necessary variables.
- GitHub Actions could be so much better
-
How do you debug CI/CD pipelines? Breakpoints?
Two tools I've used for local Gitlab CI runs: - https://github.com/firecow/gitlab-ci-local - https://gitlab.com/AdrianDC/gitlabci-local
-
makefiles in stages
What you might want to look at is this, to meet both needs https://github.com/firecow/gitlab-ci-local
-
Looking for a way to test CI pipeline (gitlab) locally
https://github.com/firecow/gitlab-ci-local exists but its not quite there yet. Personally Ive resorted to setting up a self-managed instance at home, relying on the included linter/validator and pushing repeatedly as before.
-
Selfhosted Gitlab for CI only
If you already have/had a working pipeline then maybe https://github.com/firecow/gitlab-ci-local has something worth looking at.
-
The End of CI
> One thing that would be nice, however, would be the ability to run the entire pipeline locally.
This cost me many hours of waiting for the Gitlab CI runner when debugging non-trivial pipelines, when the issue was something that did not have to do with the script steps inside of the jobs but rather how the Gitlab runner handled things.
I've found gitlab-ci-local [1] which actually does run the Gitlab pipeline locally, although I had to write some boilerplaye scripts to set up all the necessary 'CI_FOO_SOMETHING' environment variables before running the tool. (Which sometimes came back to bite me because the issue was actually in the content of some of those environment variables). It's still a very good tool.
[1] https://github.com/firecow/gitlab-ci-local
-
How to develop CI pipeline effectively?
Most CI/CD tools let you run pipelines locally. Just one example: https://circleci.com/blog/using-runner-for-local-testing/ . In my opinion Gitlab and Circleci have the test tools for this.
- firecow/gitlab-ci-local : Tired of pushing to test your .gitlab-ci.yml?
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]
dagger - Application Delivery as Code that Runs Anywhere
act - Run your GitHub Actions locally š
tekton-kickstarter - Templates, scripts and samples for quickly building CI/CD with Tekton.
floatly - An extension that adds a floating button for browser quick actions
mongodb-github-action - Use MongoDB in GitHub Actions
pypyr automation task runner - pypyr task-runner cli & api for automation pipelines. Automate anything by combining commands, different scripts in different languages & applications into one pipeline process.
github-activity-readme - Updates README with the recent GitHub activity of a user
goonstation - Repository for the Goonstation branch of SS13
ssh-agent - GitHub Action to setup `ssh-agent` with a private key
iamlive - Generate an IAM policy from AWS, Azure, or Google Cloud (GCP) calls using client-side monitoring (CSM) or embedded proxy