Need advice about which tool to choose?Ask the StackShare community!
Buddy vs GitLab: What are the differences?
Introduction
In this article, we will compare and highlight the key differences between Buddy and GitLab.
Integration Capabilities: Buddy offers seamless integration with a wide array of tools and services, such as AWS, Google Cloud Platform, Azure, Docker, Kubernetes, and more. On the other hand, GitLab also supports integrations with various tools and services like Slack, Jira, Jenkins, and Kubernetes, but its integration capability is slightly more limited compared to Buddy.
Simple User Interface: Buddy has an intuitive and user-friendly interface that makes it easy for users to navigate and perform tasks. It provides a visually appealing dashboard where users can manage their projects efficiently. GitLab, on the other hand, has a more complex interface with a steep learning curve, especially for new users. It offers a comprehensive set of features, but the user interface can be overwhelming for some.
Continuous Integration/Continuous Deployment (CI/CD) Pipelines: Buddy offers a highly flexible and customizable CI/CD pipeline configuration, allowing users to automate their software development workflows effectively. It provides a visual editor for creating pipelines and an extensive library of actions for code testing, building, and deployment. GitLab also offers CI/CD pipelines, but the configuration and customization options are not as robust as Buddy's. It may require more manual configuration and scripting to achieve complex workflows.
Pricing Model: Buddy follows a subscription-based pricing model, offering different plans based on the number of users and projects. It provides a 14-day free trial and transparent pricing tiers for easy scalability. GitLab, on the other hand, offers both self-hosted and cloud-based options. The self-hosted version allows users to have complete control over infrastructure but requires additional setup and maintenance. The cloud-based version has various pricing tiers based on the number of users and additional features.
Built-in Code Review: Buddy provides a built-in code review feature that allows for collaborative code review directly within the platform. It facilitates efficient teamwork and improves the overall code quality. GitLab also offers code review capabilities, but it may require additional setup and integration with external tools like GitLab Merge Requests for a seamless code review process.
Deployment to Multiple Environments: Buddy allows users to deploy their applications to multiple environments, such as staging, production, or development, easily. Users can define custom deployment actions for different environments and automate the deployment process with just a few clicks. GitLab also supports multi-environment deployments, but the configuration and setup may require more manual intervention compared to Buddy's user-friendly approach.
In summary, Buddy stands out with its extensive integration capabilities, user-friendly interface, flexible CI/CD pipelines, subscription-based pricing, built-in code review, and easy deployment to multiple environments. GitLab, on the other hand, offers some integration options, a comprehensive feature set, both self-hosted and cloud-based options, code review capabilities, and multi-environment deployment, but with some limitations compared to Buddy.
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 Buddy
- Easy setup56
- Docker53
- Continuous Integration50
- Integrations49
- Beautiful dashboard46
- Git hosting45
- Free43
- Unlimited pipelines42
- Monitoring39
- Backup39
- Great UX37
- On-Premises32
- Awesome support31
- AWS Integrations6
- Great UI5
- Hosted internally (Enterprise)3
- Slack integration3
- Continuous deployment3
- Simple deployments3
- Bitbucket integration3
- Github integration2
- UI and YML configuration2
- Node.js support2
- Azure integration2
- Amazing + free2
- Support for build pipelines1
- Docker support1
- Gitlab integration1
- Android support1
- Pushover integration1
- DigitalOcean integration1
- UpCloud integration1
- Shopify integration1
- New Relic integration0
- Rollbar integration0
- Sentry integration0
- Loggly integration0
- Datadog integration0
- Bugsnag integration0
- Honeybadger integration0
- Telegram integration0
- HipChat integration0
- Discord integration0
- Pushbulet integration0
- AWS integration0
- Slack Integration0
- Google Cloud integration0
- Heroku integration0
- Rackspace integration0
- Kubernetes support0
Pros of GitLab
- Self hosted508
- Free430
- Has community edition339
- Easy setup242
- Familiar interface240
- Includes many features, including ci137
- Nice UI113
- Good integration with gitlabci84
- Simple setup57
- Free private repository34
- Has an official mobile app34
- Continuous Integration31
- Open source, great ui (like github)22
- Slack Integration18
- Full CI flow14
- Free and unlimited private git repos11
- User, group, and project access management is simple10
- All in one (Git, CI, Agile..)9
- Built-in CI8
- Intuitive UI8
- Both public and private Repositories6
- Full DevOps suite with Git6
- Build/pipeline definition alongside code5
- CI5
- So easy to use5
- Integrated Docker Registry5
- It's powerful source code management tool5
- Issue system4
- Dockerized4
- Unlimited free repos & collaborators4
- Security and Stable4
- On-premises4
- It's fully integrated4
- Mattermost Chat client4
- Excellent4
- Great for team collaboration3
- Built-in Docker Registry3
- Low maintenance cost due omnibus-deployment3
- I like the its runners and executors feature3
- Free private repos3
- Because is the best remote host for git repositories3
- Not Microsoft Owned3
- Opensource3
- Groups of groups2
- Powerful software planning and maintaining tools2
- Review Apps feature2
- Kubernetes integration with GitLab CI2
- It includes everything I need, all packaged with docker2
- Multilingual interface2
- HipChat intergration2
- Powerful Continuous Integration System2
- One-click install through DigitalOcean2
- The dashboard with deployed environments2
- Native CI2
- Many private repo2
- Kubernetes Integration2
- Published IP list for whitelisting (gl-infra#434)2
- Wounderful2
- Beautiful2
- Supports Radius/Ldap & Browser Code Edits1
Sign up to add or upvote prosMake informed product decisions
Cons of Buddy
- Deleted account after 1 month of not pushing code1
Cons of GitLab
- Slow ui performance28
- Introduce breaking bugs every release8
- Insecure (no published IP list for whitelisting)6
- Built-in Docker Registry2
- Review Apps feature1