GitLab Ultimate
GitLab | GitLab Ultimate 17.2.1 ReleaseLinux/Unix, Ubuntu 20.04 - 64-bit Amazon Machine Image (AMI)
External reviews
External reviews are not included in the AWS star rating for the product.
Gitlab is such an essential tool for us that every employee, not just engineers, work with it daily
What do you like best about the product?
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.
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
Software development, project management, documentation management, single tool used by the entire company
- Leave a Comment |
- Mark review as helpful
I have more than 3 years of years of experience using GitLab
What do you like best about the product?
Integration with all primary IDE like PDSOE (Progress Developer Studio) and IntelliJ. Cloued based UI supporting Git for version control. As a developer my code always will be safe. Less code conflicts since it allowed local checkout and multiple developer can work simultaneously in one program file. It supports both large-size projects and small-size projects.
What do you dislike about the product?
It is vibrant in functionality, so tricky to understand. Help documentation can be improved. Integration with other tools is a bit complex. Member permission implementation can be better.
What problems is the product solving and how is that benefiting you?
Version controlling for our project. Cherry-picking is very easy using a web-based application.
Recommendations to others considering the product:
It is best tool availbale in market for version control and project monitoring.
Git lab the best open source devopps platform
What do you like best about the product?
I like the below features:
1) Reduce cost.
2) Reduce developer time thus increasing productivity.
3) we can see the changes before pushing the change.
4) ui is quite good.
5) approval process can be setup to ensure changes are correct for the purpose of review.
1) Reduce cost.
2) Reduce developer time thus increasing productivity.
3) we can see the changes before pushing the change.
4) ui is quite good.
5) approval process can be setup to ensure changes are correct for the purpose of review.
What do you dislike about the product?
I don't think I can dislike any feature right now.
What problems is the product solving and how is that benefiting you?
I am solving below problems:
1) I am able to save time.
2) productivity is increased.
3) quite simple process to push the development changes.
4) I can see what changes I have made before pushing the changes to branch.
1) I am able to save time.
2) productivity is increased.
3) quite simple process to push the development changes.
4) I can see what changes I have made before pushing the changes to branch.
Recommendations to others considering the product:
I would definitely recommend this tool.
Great application to store and review code
What do you like best about the product?
I enjoy using GitLab mostly for RPA code packages. The code review features for reviewing version is great.
What do you dislike about the product?
The only issue I have had is when committing from a cloned repository. There is usually some kind of access error but it probably my configuration.
What problems is the product solving and how is that benefiting you?
Great for code storage and a good idea to always have a backup.
Recommendations to others considering the product:
Don't loose your code.
A good VCS tool
What do you like best about the product?
We can have free private repositories, but it has limited features. But we can get used to it before purchasing the product. Also, I like the web IDE in GitLab, which is far better than the text editor in other VCS. Also, we can check the GitLab ci config file before pushing it and testing it in the pipeline. We can validate the yml script on the GitLab site itself.
What do you dislike about the product?
There are some limitations in Gitlab. For example, we can not re-request for review from the co-workers. Also, I am not a fan of GitLab UI. Mainly the notification side.
What problems is the product solving and how is that benefiting you?
We can use it as a remote git repository to collaborate with co-workers on a project. We can make several branches based on what functionality is being developed. And we can create merge requests and then merge all the work in the main branch. Co-working on software project is very easy with GitLab.
Recommendations to others considering the product:
It is a good tool to use for version management and collaboration on a project. You should consider this software especially when you want a test pipeline with gitlab-ci.
Best business git repository management
What do you like best about the product?
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.
What do you dislike about the product?
Sometimes some of the bugs take longer to fix but is nothing that you can get a workaround for.
What problems is the product solving and how is that benefiting you?
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.
Great for managing codebase, CI/CD
What do you like best about the product?
Useful for git repo, code reviews, CI/CD
What do you dislike about the product?
It works fine for my needs. No complaints.
What problems is the product solving and how is that benefiting you?
Code Repo, CI/CD, code reviews
GitLab : More than version controlling
What do you like best about the product?
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.
GitLab is easy to configure with CI/CD pipeline.
What do you dislike about the product?
I have been using GitLab for more than 3 years but till now I could not find any issue with this feature-rich tool.
What problems is the product solving and how is that benefiting you?
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.
Recommendations to others considering the product:
This tool is an essential component of our security hardening and validation procedures.
Version control tool for maintaining source code easily!!!!
What do you like best about the product?
The GUI is impressive. We can integrate it with other platforms through CI/CD pipeline easily.
What do you dislike about the product?
It is almost similar to other git-based SVMs. No additional functionality is needed. It is suitable for essential code management.
What problems is the product solving and how is that benefiting you?
Managing code in repository, along with multiple branches able to merge once verified into master branch.
Recommendations to others considering the product:
It is easy to use and good to use for software development process.
Where does it explain what the default login credentials are?
Its easy to get this started. But there isn't any obvious documentation to tell the user how to login.
showing 511 - 520