GitLab DevSecOps platform enables software innovation by aiming to empower development, security, and operations teams to build better software, faster. With GitLab, teams can create, deliver, and manage code quickly and continuously instead of managing disparate tools and scripts. GitLab helps teams across the complete DevSecOps lifecycle, from developing, securing, and deploying software. Differentiators, as described by Gitlab:
Simplicity: With GitLab, DevSecOps can…
$0
per month per user
Jenkins
Score 8.3 out of 10
N/A
Jenkins is an open source automation server. Jenkins provides hundreds of plugins to support building, deploying and automating any project. As an extensible automation server, Jenkins can be used as a simple CI server or turned into a continuous delivery hub for any project.
The company has had prior experience with Bamboo. GitLab has much more functionality than Bamboo and worked better with some of our legacy projects. While Jenkins is free, it really isn't free - the amount of work required to get something up and running would have been …
GitLab fits our needs much better because it is a all-in-one solution and is easier to learn. We have a wide range of users - senior software developers and people who only write small, easy scripts or just start pipelines. Jenkins is rather useful when e.g. more fine-grained …
It was a management decision to use GitLab over other tools. It integrates well with RBAC using Terraform. Runners are easy to setup. Almost all the features the organization used before are available in GitLab.
Software delivery is the key objective and GitLab made it much easier to hit the group quickly. It worked well with automation, and integrations with other SDLC tools used in the Organization and it is really easy to use. It's widely adopted and has the power to deliver what we …
GitLab's online IDE and code modification is much better compared to Stash. While pricier than Bitbucket, Gitlab also provides CI CD configuration better than BB.
We migrated from Gerrit to GitLab, and minus a few minor bumps during migration, GitLab has been hands down better. Our devs have faster time to code review with notifications, the UI is easy to navigate and, and our pipeline is integrated and automated, so once everything is …
Gitlab provided on par functionality and it provided a good option for us to self host which is very important for our business. We think the business continuity story is more solid with Gitlab.
GitLab is easily the preferred tool when it comes to versioning and source control. With other tools the UI often feels outdated and clunky leading to inefficiency and confusion. With some of the sleeker tools such as GitKraken, while the aesthetic is pleasing, the experience …
Git has a Distributed Model. SVN has a Centralized Model. In git every user has their own copy of code on their local like their own branch. In SVN there is central repository has working copy that also make changes and committed in central repository
1) Good support from the community. 2) Easy to implement and understand 3) Easy to manage GitLab runners.
Verified User
Team Lead
Chose GitLab
Sometimes it gets very slow and provides a problem to connect or update the servers. Search is difficult on some pages. Some features are missing that are available on GitHub.
Even though all three tools are also useful for their own merit, we found GitLab to be the best supported and most customizable for our needs. It is useful to know that the product today is what we need it to be and the community is there to keep it updated if we need more …
GitLab is the best combination of all the other tools. They are still viable in their own sense, but for the projects we were using, GitLab proved to be an excellent alternative.
Gitlab surpasses Bitbucket in all areas except of course the very tight integration Bitbucket has with JIRA and Confluence. Almost everyone uses JIRA at some level or time so Bitbucket has a more natural and tight integration feel. However, there is good JIRA integration with …
Overall, Jenkins is the easiest platform for someone who has no experience to come in and use effectively. We can get a junior engineer into Jenkins, give them access, and point them in the right direction with minimal hand-holding. The competing products I have used (TravisCI/G…
GitLab CI and GitHub Actions are other powerful options in the market also with a rising popularity and high interoperability with their respective platform. But Jenkins is still a good option for complex pipelines that require scripting and logic. Also, Jenkins uses as runtime …
Verified User
Engineer
Chose Jenkins
It's mostly stable and well-known within the DevOps community.
Both Jenkins and TeamCity do a good job of automating CI/CD. Jenkins runs much leaner than TeamCity - it only needs about a Gig of free memory, whereas TeamCity needs a fat 4 Gig free. Many tasks in Jenkins yml config can be very cumbersome, especially running local and …
Originally Jenkins was selected because it was the best around, but it has since been outclassed by more specific services or cloud-based services and tools that will do all of the heavy lifting for you. Jenkins still has a use case - but it's hard to argue the additional …
Jenkins immense flexibility and its large and impressive selection of available community-driven plugins makes it ideal choice for solving non-traditional problems.
However, for CI/CD - consider the benefit of modern tools that enforce reusable, infrastructure as code design …
I would use TeamCity if Jenkins was not already in place. TeamCity seems a lot more stable when it comes to upgrading the software and job templates the way TeamCity handles them is an absolute killer feature. Jenkins is a bit of a wild animal, quite unpredictable but with the …