Gitlab Alternatives
Similar projects and alternatives to gitlab
-
-
Scout APM
Scout APM: A developer's best friend. Try free for 14-days. Scout APM uses tracing logic that ties bottlenecks to source code so you know the exact line of code causing performance issues and can get back to building a great product faster.
-
-
chatwoot
Open-source customer engagement suite, an alternative to Intercom, Zendesk, Salesforce Service Cloud etc. 🔥💬
-
Gitbucket
A Git platform powered by Scala with easy installation, high extensibility & GitHub API compatibility
-
-
linguist
Language Savant. If your repository's language is being reported incorrectly, send us a pull request!
-
-
-
terratest
Terratest is a Go library that makes it easier to write automated tests for your infrastructure code.
-
-
-
-
v
Simple, fast, safe, compiled language for developing maintainable software. Compiles itself in <1s with zero library dependencies. https://vlang.io
-
-
-
-
Reviews and mentions
- CI/CD tool with customizable GUI and manual trigger like Jenkins
-
Any plans to move the KDE bug tracker from Bugzilla to Gitlab?
https://gitlab.com/gitlab-org/gitlab/-/issues/26581 mentions some of the issues.
In practice, large orgs that use GitLab seem to end up having people open issues in one central repo to alleviate the above issues, resulting in issue lists that number in the thousands, making it impossible for anyone to find anything due to the lack of structure. For example see the 40,000 issues in https://gitlab.com/gitlab-org/gitlab/-/issues.
May be it's worth adding up to date findings here: https://gitlab.com/gitlab-org/gitlab/-/issues/26581
Meanwhile, even the minimum required for that, the ability to even search multiple repos from a given date, is currently not implemented in Gitlab. Needless to say, relative dates are not a thing yet either.
Yeah, I need to find or file bug reports for all the things I brought up here. Finding anything in https://gitlab.com/gitlab-org/gitlab/-/issues is practically impossible though--a charge frequently levied against KDE's bugzilla instance, illustrating that a lot of the problem we face stem from our size rather than the tools we're using
-
On automated versioning strategies for CI/CD pipelines
The biggest problem with this approach is that it requires pulling the repository up to unknown depth. In a CI/CD pipeline you would generally pull only a shallow copy of the repository. Why slow down your jobs by downloading every commit since the beginning of time? Well, you rather have to with this strategy, or git describe might suddenly return something unexpected if the tag is more commits away than the clone depth.
-
Microservices Architecture on Google Cloud
> It is extremely difficult to change a monolith’s technology or language or framework because all components are tightly coupled and dependent on each other. As a result, even relatively small changes can require lengthy development and deployment times.
I disagree with this so much. I have personally worked with Rails application monoliths and Node.js microservices and I can tell you that making changes on the monolith is muliple times easier mostly depending on the code structure. I would take a properly structured monolith any day. This not only includes code/features but also deployments. Adding more services introduces more complexity in the deployment architecture as well.
A good example of this is just by looking at the GitLab codebase https://gitlab.com/gitlab-org/gitlab, it's a monolith but has good abstractions/structure vs say the Google Microservices Demo app https://github.com/GoogleCloudPlatform/microservices-demo which is not tightly coupled but introduces more complexity from implementation to deployment.
-
Utterances – a lightweight comments widget built on GitHub issues
Hey there,
I'm on the Community Relations team at GitLab. I'd love to learn more about your experience as a member of the GitLab community.
When you say that opening an issue on GitLab doesn't make you feel part of a community, are you referring issues on one of GitLab's projects (ex: https://gitlab.com/gitlab-org/gitlab) or are you referring to issues on open source projects being hosted on GitLab.com?
Community is very important to us so when there are areas for improvement that feedback is really valued.
-
Use URL https://gitlab.com/name for group, not user
The doc is updated with very release of GitLab. There should not be any broken links, so feel free to report through our issues system (https://gitlab.com/gitlab-org/gitlab/-/issues/). Also make sure you're using the right version of the doc, which is at the top right corner of the docs page.
-
Gitlab servers are being exploited in DDoS attacks in excess of 1 Tbps
It doesn't help if the file is not executable, but the parser executes it on its own:
> When uploading image files, GitLab Workhorse passes any files with the extensions jpg|jpeg|tiff through to ExifTool to remove any non-whitelisted tags.
> An issue with this is that ExifTool will ignore the file extension and try to determine what the file is based on the content, allowing for any of the supported parsers to be hit instead of just JPEG and TIFF by just renaming the uploaded file.
> One of the supported formats is DjVu. When parsing the DjVu annotation, the tokens are evaled to "convert C escape sequences".
-
How to disable various GitLab GUI nagging banners?
It takes a lot of engineering effort to make settings appear in each level of GitLab. Here's an example of making merge method available in each level. I understand your concerns though. We are looking to make GitLab more flexible in the future with workspaces.
- Gitlab server with CE has been compromised
-
Trojan Source: Invisible Vulnerabilities (pdf)
Looks like this was shipped with the latest security release https://gitlab.com/gitlab-org/gitlab/-/commit/3fb44197195b5789b99a13f7bf482e9a895dfc58
-
‘Trojan Source’ Bug Threatens the Security of All Code
I was impatient to find the example you were talking about; as far as I can tell, this is the line with the example: https://gitlab.com/gitlab-org/gitlab/-/commit/3fb44197195b57...
And here's what it looks like in various conditions/viewers:
With the fix, this is how it looks in the browser in the Gitlab interface:
if (accessLevel != "user�") {� // Check if admin ��
Stats
Popular Comparisons
Are you hiring? Post a new remote job listing for free.