Need advice about which tool to choose?Ask the StackShare community!
GitLab vs Go.CD: What are the differences?
Introduction
In this article, we will explore the key differences between GitLab and Go.CD. GitLab and Go.CD are both popular DevOps tools that help streamline the software development and deployment process. While they share some similarities, there are also significant differences between the two platforms. Let's delve into the key distinctions.
Deployment Pipeline Configuration: GitLab primarily focuses on providing a complete DevOps platform that includes version control, issue tracking, continuous integration, and continuous deployment. While GitLab does have a built-in CI/CD pipeline feature, it lacks the extensive customization options offered by Go.CD. Go.CD is specifically designed to simplify complex deployment pipelines by providing an intuitive and configurable interface. It allows users to define dependencies, orchestrations, fan-ins, and fan-outs, making it a powerful tool for managing intricate pipelines.
Configuration Management: GitLab and Go.CD differ in their approach to configuration management. GitLab employs a declarative configuration approach, where users specify the desired state in a configuration file, and GitLab handles the execution. On the other hand, Go.CD adopts an imperative configuration approach, where users define the exact steps required to achieve the desired state. This allows for more granular control and allows teams to build more complex and flexible pipelines.
Plugins and Extensions: Go.CD offers a vast library of plugins and extensions that enhance its functionality and make it easier to integrate with other tools in the DevOps ecosystem. These plugins provide support for various version control systems, notification mechanisms, analytics tools, and more. GitLab, on the other hand, offers a more integrated approach, where many functionalities are natively built into the platform. While GitLab does provide some plugins and integrations, it may require additional customization to achieve the same level of extensibility as Go.CD.
User Interface: The user interface of GitLab and Go.CD differs significantly. GitLab provides a comprehensive web-based interface that encompasses all aspects of the DevOps lifecycle, including code management, issue tracking, and CI/CD pipelines. On the other hand, Go.CD focuses primarily on the pipeline orchestration and provides a simple, intuitive interface for pipeline configuration and visualization. This streamlined interface makes it easier for users to understand and manage their pipelines.
Community and Support: GitLab has a large and active community, which contributes to its continuous improvement and provides a wealth of resources for users. The community-driven model allows for rapid development and innovation. Go.CD, while also having a dedicated community, is more commercially driven, with support and additional features available through commercial subscriptions. The choice between the two platforms depends on the level of community support desired and the need for commercial support and features.
Pricing Model: GitLab offers a range of pricing options, including a free tier for small teams and a paid tier for enterprise customers. It follows a subscription-based pricing model that includes technical support and access to additional features. Go.CD, on the other hand, offers a free and open-source version that is suitable for many organizations. However, commercial support and additional enterprise features are available through a commercial subscription.
In summary, GitLab provides a complete DevOps platform with built-in CI/CD pipeline features, while Go.CD specializes in pipeline orchestration and configurability. GitLab adopts a declarative configuration approach, while Go.CD follows an imperative approach. Go.CD offers a broader range of plugins and extensions, while GitLab focuses on integration within its own platform. The user interface and community support differ between the two platforms, and the pricing models also vary. Overall, the choice between GitLab and Go.CD depends on the specific requirements and preferences of the organization.
I'm open to anything. just want something that break less and doesn't need me to pay for it, and can be hosted on Docker. our scripting language is powershell core. so it's better to support it. also we are building dotnet core in our pipeline, so if they have anything related that helps with the CI would be nice.
Google cloud build can help you. It is hosted on cloud and also provide reasonable free quota.
I first used BitBucket because it had private repo's, and it didn't disappoint me. Also with the smooth integration of Jira, the decision to use BitBucket as a full application maintenance service was as easy as 1, 2, 3.
I honestly love BitBucket, by the looks, by the UI, and the smooth integration with Tower.
Do you review your Pull/Merge Request before assigning Reviewers?
If you work in a team opening a Pull Request (or Merge Request) looks appropriate. However, have you ever thought about opening a Pull/Merge Request when working by yourself? Here's a checklist of things you can review in your own:
- Pick the correct target branch
- Make Drafts explicit
- Name things properly
- Ask help for tools
- Remove the noise
- Fetch necessary data
- Understand Mergeability
- Pass the message
- Add screenshots
- Be found in the future
- Comment inline in your changes
Read the blog post for more detailed explanation for each item :D
What else do you review before asking for code review?
Using an inclusive language is crucial for fostering a diverse culture. Git has changed the naming conventions to be more language-inclusive, and so you should change. Our development tools, like GitHub and GitLab, already supports the change.
SourceLevel deals very nicely with repositories that changed the master branch to a more appropriate word. Besides, you can use the grep linter the look for exclusive terms contained in the source code.
As the inclusive language gap may happen in other aspects of our lives, have you already thought about them?
One of the magic tricks git performs is the ability to rewrite log history. You can do it in many ways, but git rebase -i
is the one I most use. With this command, It’s possible to switch commits order, remove a commit, squash two or more commits, or edit, for instance.
It’s particularly useful to run it before opening a pull request. It allows developers to “clean up” the mess and organize commits before submitting to review. If you follow the practice 3 and 4, then the list of commits should look very similar to a task list. It should reveal the rationale you had, telling the story of how you end up with that final code.
Out of most of the VCS solutions out there, we found Gitlab was the most feature complete with a free community edition. Their DevSecops offering is also a very robust solution. Gitlab CI/CD was quite easy to setup and the direct integration with your VCS + CI/CD is also a bonus. Out of the box integration with major cloud providers, alerting through instant messages etc. are all extremely convenient. We push our CI/CD updates to MS Teams.
Gitlab as A LOT of features that GitHub and Azure DevOps are missing. Even if both GH and Azure are backed by Microsoft, GitLab being open source has a faster upgrade rate and the hosted by gitlab.com solution seems more appealing than anything else! Quick win: the UI is way better and the Pipeline is way easier to setup on GitLab!
At DeployPlace we use self-hosted GitLab, we have chosen GitLab as most of us are familiar with it. We are happy with all features GitLab provides, I can’t imagine our life without integrated GitLab CI. Another important feature for us is integrated code review tool, we use it every day, we use merge requests, code reviews, branching. To be honest, most of us have GitHub accounts as well, we like to contribute in open source, and we want to be a part of the tech community, but lack of solutions from GitHub in the area of CI doesn’t let us chose it for our projects.
Pros of GitLab
- Self hosted508
- Free431
- Has community edition339
- Easy setup242
- Familiar interface240
- Includes many features, including ci137
- Nice UI113
- Good integration with gitlabci84
- Simple setup57
- Has an official mobile app35
- Free private repository34
- Continuous Integration31
- Open source, great ui (like github)23
- Slack Integration18
- Full CI flow15
- Free and unlimited private git repos11
- All in one (Git, CI, Agile..)10
- User, group, and project access management is simple10
- Intuitive UI8
- Built-in CI8
- Full DevOps suite with Git6
- Both public and private Repositories6
- Integrated Docker Registry5
- So easy to use5
- CI5
- Build/pipeline definition alongside code5
- It's powerful source code management tool5
- Dockerized4
- It's fully integrated4
- On-premises4
- Security and Stable4
- Unlimited free repos & collaborators4
- Not Microsoft Owned4
- Excellent4
- Issue system4
- Mattermost Chat client4
- Great for team collaboration3
- Free private repos3
- Because is the best remote host for git repositories3
- Built-in Docker Registry3
- Opensource3
- Low maintenance cost due omnibus-deployment3
- I like the its runners and executors feature3
- Beautiful2
- Groups of groups2
- Multilingual interface2
- Powerful software planning and maintaining tools2
- Review Apps feature2
- Kubernetes integration with GitLab CI2
- One-click install through DigitalOcean2
- Powerful Continuous Integration System2
- It includes everything I need, all packaged with docker2
- The dashboard with deployed environments2
- HipChat intergration2
- Many private repo2
- Kubernetes Integration2
- Published IP list for whitelisting (gl-infra#434)2
- Wounderful2
- Native CI2
- Supports Radius/Ldap & Browser Code Edits1
Pros of GoCD
- Open source32
- Pipeline dependencies27
- Pipeline structures25
- Can run jobs in parallel22
- Very flexible20
- Plugin architecture15
- Environments can keep config secure13
- Great UI12
- Good user roles and permissions10
- Supports many material dependencies9
- Fan-in, Fan-out7
- Designed for cd not just ci6
- Empowers product people to make delivery decisions4
- Flexible & easy deployment2
- Pass around artifacts2
- Build once1
Sign up to add or upvote prosMake informed product decisions
Cons of GitLab
- Slow ui performance28
- Introduce breaking bugs every release9
- Insecure (no published IP list for whitelisting)6
- Built-in Docker Registry2
- Review Apps feature1
Cons of GoCD
- Lack of plugins2
- Horrible ui2
- No support1