gitaly
gitlab-ci-local
gitaly | gitlab-ci-local | |
---|---|---|
9 | 10 | |
- | 1,880 | |
- | - | |
- | 9.1 | |
- | about 5 hours ago | |
TypeScript | ||
- | 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.
gitaly
-
Gitlab Gitaly project now supports the SHA-256 hashing algorithm
Clicking through to https://gitlab.com/gitlab-org/gitaly yields
> Gitaly is a Git RPC service for handling all the git calls made by GitLab
So I think this means that a major piece of gitlab now supports sha256 git repos? But probably not everything and therefore we can't actually push sha256 git repos to gitlab yet?
-
heads up Github host key issue
With https transport, the webserver can make a simple database call (or hit a cache) to check your authorization, and then make your git operation call. No exec need.
- makefiles in stages
- Does core create a git repo in /etc?
- Pihole running on VM constantly running out of space due to FTL copies in git packfile
-
magit + libgit2
There are things where libgit2 is faster than git, and there are things libgit2 can't do. Here is a brief note from another discussion:
-
GitLab plans to delete dormant projects from free accounts: Hopes to save a quarter of hosting costs by binning repos that haven't been touched for a year
Not easily, because their storage backend requires computing.
-
Gitly: A light and fast GitHub/Gitlab alternative written in V lang (pre-alpha)
You might have trademark issues with Gitlab's Gitaly https://gitlab.com/gitlab-org/gitaly
-
Any idea if this is realistically doable in rails?
Yeah, they use a thing they built themselves called gitaly: https://gitlab.com/gitlab-org/gitaly
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?
onedev - Git Server with CI/CD, Kanban, and Packages. Seamless integration. Unparalleled experience.
dagger - Application Delivery as Code that Runs Anywhere
Gitbucket - A Git platform powered by Scala with easy installation, high extensibility & GitHub API compatibility
tekton-kickstarter - Templates, scripts and samples for quickly building CI/CD with Tekton.
libegit2 - Emacs bindings for libgit2
act - Run your GitHub Actions locally 🚀
magit - It's Magit! A Git porcelain inside Emacs.
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.
gitlab
action-tmate - Debug your GitHub Actions via SSH by using tmate to get access to the runner system itself.
goonstation - Repository for the Goonstation branch of SS13
iamlive - Generate an IAM policy from AWS, Azure, or Google Cloud (GCP) calls using client-side monitoring (CSM) or embedded proxy