Unclaimed: Are are working at GitLab ?
GitLab Reviews & Product Details
GitLab is a robust platform designed to streamline the software development process by offering tools for version control, project management, and collaboration. It enables teams to manage repositories, track changes, and automate parts of the software delivery lifecycle through continuous integration and deployment features. With its user-friendly interface and extensive set of functionalities, GitLab supports developers in enhancing productivity and maintaining high-quality codebases. This platform is adaptable for projects of any size, from small startups to large-scale enterprise applications.
| Capabilities |
AI
API
CLI
OSS
|
|---|---|
| Ease of use |
Beginner
Intermediate
Advanced
|
| Deployment | Cloud / SaaS / Web-Based, Desktop Mac, Desktop Windows, Mobile Android, Mobile iPhone, On-Premise Linux |
| Support | 24/7 (Live rep), Chat, Email/Help Desk, FAQs/Forum, Knowledge Base, Phone Support |
| Training | Documentation |
| Languages | English |
GitLab Pros and Cons
- Comprehensive DevOps platform with integrated tools.
- Strong support for CI/CD pipelines.
- Open-source with a large community of contributors.
- Flexible deployment options including self-hosted and cloud-based.
- Extensive integration capabilities with third-party tools.
- Premium features can be costly for small teams.
- Steeper learning curve for beginners.
- Performance issues with large repositories.
- Limited native mobile support.
- Some features may require additional configuration.
Compare GitLab with other popular tools in the same category.
Its my favourite DevOps life cycle application with integration of application security testing. It allows my company to make step ahead that is needed for assurance of every application atleast bare minimum security.
So ffar so good,i have no dislike. I appreciate the existence of intuitive customer service.
GitLab performance a comprehensive security audit of application code. The dashboards-reports and real-time alerts to predict and eliminate delays,enable Visibility Activity of cycle-time,deployment frequency.
The bestest thing i liked in gitlab is their CI/CD pipeline functionality. It have my life easier in creating CI/CD pipeline for deployment on firebase and other platforms as respected. Other than that all of tools available in gitlab which differs from other scm tools are also up to the point sich as webhooks for triggering pipelines of jenkins is also the best thing i tested and worked on in gitlab.
Nothing find anything to dislike. One thing can make it more better is that you have to go premium if you want to give specific person permission to push or merge code.if they allow free users also that would be great for all gitlab users.
I completed my task which was assigned to me to create pipelines for firebase for deployment whenever developer pushes the code this was my first experience with gitlab. And from then i just loved using gitlab for day to day tasks.
We've been using Gitlab CE for ~5 years. I initially chose to migrate to GitLab from GitHub because of its, then unique, offering of built-in CI/CD functionality with the ability to use one's own servers as runners which was much more flexible and cost-effective compared to other alternatives. Since then, Gitlab has evolved, each month bringing new functionalities and improvements. Initially, it was mainly used by our engineers/developers writing code, with a couple of other people using GitLab's issue tracker. All engineers/developers loved it immediately, with its unified simple interface to manage git repos, issue trackers, and CI/CD pipelines. Sysops was the next logical step. By moving shell scripts, ansible/chef/puppet, docker files, helm charts etc to GitLab and authoring pipelines for their build, execution, and deployment, management of our entire infrastructure was now documented, automated and revision-controlled. At pretty much the same time, our company was struggling with what, at first glance, seemed like a completely unrelated issue: We had to maintain and constantly update extensive official documentation, like Software Product Technical Files, our Quality Management System, internal procedures, and a plethora of other documents. These are essentially very large, mostly-text, files or collections of files that need to be version-controlled while any changes to them need to be reviewed and approved under strict policies. And effectivily managing them in Google Docs was quickly becoming untenable. It was then that, being a software company, we noticed the similarities between the requirements of handling such documentation and handling software code. We ported all these documents to GitLab, organized in a few projects containing several markdown files. Git provides us with a clear audit log of all changes. All employees use Gitlab's Merge Requests and its integrated simple editor or web IDE to propose changes to these documents. Changes can be discussed by everyone and merged/approved by authorized personnel. Automated CI/CD pipelines build the documentation files in PDFs and websites deployed via GitLab Pages. We now also create GitLab Projects for several work projects, even if there's no coding required. They may contain issue trackers or wikis and help to organize, gather and share information. And this way, GitLab is now our most essential tool, used daily by every member of our team. And please note the fact that all this is by using the free and open-source edition of GitLab, not its more feature-rich paid edition.
There's honestly nothing I dislike about GitLab, I'm very happy with it. A dark them was a long-standing request of mine, but it has now been taken care of.
Software development, project management, documentation management, single tool used by the entire company
The self-managed version of GitLab lets you control your repository management the way you need. It has so many functionalities that allow your company to customize your repository management securely. I love the kanban integration and especially all the CI/CD that it has. It makes my job much more manageable.
Sometimes some of the bugs take longer to fix but is nothing that you can get a workaround for.
It's the tool we use to manage all of our repositories at the company. I've been able to streamline the entire process of deploying the applications with its powerful CI/CD integration.
Useful for git repo, code reviews, CI/CD
It works fine for my needs. No complaints.
Code Repo, CI/CD, code reviews
Notification alert, cherry-pick, Generate Merge request and assign to superior, add comments and many more features provided by GitLab. GitLab is easy to configure with CI/CD pipeline.
I have been using GitLab for more than 3 years but till now I could not find any issue with this feature-rich tool.
My whole team was able to work on the same feature using GitLab. Also, the peer code review feature allowed us to solve several issues before we integrate with the Master branch. Moreover, we have done security penetration testing using the Application Security Testing tool. We have been using this tool as a primary security validation process because it provides a holistic view of our security profile.
I like the full functionality which is available even for the free plan. Besides the must have code hosting support, you can configure runners and build jobs. Register your own server to build and deploy your product, so for hobby developers and small companies it is the universal solution for the first years.
The website for mobile is not optimised at all, so if you get the notification that your build failed, it is hard to check the result from your mobile. It also has a tricky login button location from mobile, so that part what they could put focus on.
We are hosting our entire code base on GitLab and also using the CI/CD for building and deploying the application.
its branching feature, compatibility, opensource, speed, secure
it will take some time to get flow into it, sometimes reverting the commit is tedious, commands are little bit tough to remember
I work in a concurrent software development team, we use git in parallel code management. we also maintain task, bug in git
When a project is employee-only it is just best to have it behind a system that only allows access by single sign-on and separate from the main public repository until it is ready to become live or discarded. This means no accidental pushes to the wrong remote branch or mistakenly making it public since it works in a completely different system.
Some projects that eventually get canned are actually very good but since its outside of the public eye they just get forgotten and no chance that someone else takes over them and if you are planning to go job hunting since the commits are private that means that no exposure to potential employers.
It is our internal tool for managing git projects before they go to GitHub
The best thing that I like about GitLab is that it is open source. Moreover it offer unlimited private repositories without limitation of contributors, when compared to GitHub. GitHub offers only 3 contributors to private repositories. It also supports continuous integration, delivery and integration with Jira. It also supports import using Git. It also supports different programming languages.
The one thing that I hates most about the GitLab is it's UI. It may be attractive for many of you guys, but I love the GitHub interface rather than GitLab interface.
It helped me to keep a centralized repository for my projects. It also helped me and my friends to work on the same project from different places. Since it is open source, I believe it more than anything. GitLab helped me to organize all my projects in a proper manner.