Need advice about which tool to choose?Ask the StackShare community!

Bamboo

496
504
+ 1
17
GitLab CI

2.1K
1.5K
+ 1
73
Add tool

Bamboo vs GitLab CI: What are the differences?

What is Bamboo? Tie automated builds, tests, and releases together in a single workflow. Focus on coding and count on Bamboo as your CI and build server! Create multi-stage build plans, set up triggers to start builds upon commits, and assign agents to your critical builds and deployments.

What is GitLab CI? GitLab integrated CI to test, build and deploy your code. GitLab offers a continuous integration service. If you add a .gitlab-ci.yml file to the root directory of your repository, and configure your GitLab project to use a Runner, then each merge request or push triggers your CI pipeline.

Bamboo and GitLab CI belong to "Continuous Integration" category of the tech stack.

"Integrates with other Atlassian tools" is the top reason why over 7 developers like Bamboo, while over 16 developers mention "Robust CI with awesome Docker support" as the leading cause for choosing GitLab CI.

According to the StackShare community, GitLab CI has a broader approval, being mentioned in 210 company stacks & 93 developers stacks; compared to Bamboo, which is listed in 62 company stacks and 24 developer stacks.

Advice on Bamboo and GitLab CI
Needs advice
on
CircleCICircleCIGitLab CIGitLab CI
and
Jenkins XJenkins X

We are a mid-size startup running Scala apps. Moving from Jenkins/EC2 to Spinnaker/EKS and looking for a tool to cover our CI/CD needs. Our code lives on GitHub, artifacts in nexus, images in ECR.

Drone is out, GitHub actions are being considered along with Circle CI and GitLab CI.

We primarily need:

  • Fast SBT builds (caching)
  • Low maintenance overhead (ideally serverless)
  • Everything as code
  • Ease of use
See more
Replies (3)
Glenn Gillen
Recommends
BuildkiteBuildkite

I think I've tried most of the CI tools out there at some point. It took me a while to get around to Buildkite because at first I didn't see much point given it seemed like you had to run the agent yourself. Eventually it dawned on me why this approach was more ingenious than I realised:

Running my app in a production (or production-like) environment was already a solved problem, because everything was already in some form of "everything as code". Having a test environment where the only difference was adding the Buildkite agent was a trivial addition.

It means that dev/test/prod parity is simple to achieve and maintain. It's also proven to be much easier to support than trying to deal with the problems that come with trying to force an app to fit into the nuances and constraints that are imposed by the containers/runtime of a CI service. When you completely control all of the environment the tests are running in you define those constraints too. It's been a great balance between a managed service and the flexibility of running it yourself.

And while none of my needs have hit the scale of Shopify (I saw one of their engineers speak about it at a conference once, I can't find the video now though 😞) it's good to know I can scale out my worker nodes to hundreds of thousands of workers to reduce the time it takes for my tests to run.

See more
Recommends
jFrogjFrog

I would recommend you to consider the JFrog Platform that includes JFrog Pipelines - it will allow you to manage the full artifact life cycle for your sbt, docker and other technologies, and automate all of your CI and CD using cloud native declarative yaml pipelines. Will integrate smoothly with all your other toolset.

See more
Estu Fardani
Recommends
GitLab CIGitLab CI

more configurable to setup ci/cd: * It can provide caching when build sbt, just add this section to yml file * Easy to use, many documentation

Weakness: * Need use gitlab as repository to bring more powerful configuration

See more
Decisions about Bamboo and GitLab CI

Buddy is one of the most easy-to-use tools for CI I ever met. When I needed to set up the pipeline I was really impressed with how easy it is to create it with Buddy with only a few moments. It's literally like: 1. Add repo 2. Click - Click - Click 3. You're done and your app is on prod :D The top feature that I've found is a simple integration with different notification channels - not only Slack (which is the one by default), but Telegram and Discord. The support is also neat - guys respond pretty quickly on even a small issue.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Bamboo
Pros of GitLab CI
  • 10
    Integrates with other Atlassian tools
  • 4
    Great notification scheme
  • 2
    Great UI
  • 1
    Has Deployment Projects
  • 22
    Robust CI with awesome Docker support
  • 12
    Simple configuration
  • 8
    All in one solution
  • 7
    Source Control and CI in one place
  • 5
    Easy to configure own build server i.e. GitLab-Runner
  • 5
    Integrated with VCS on commit
  • 5
    Free and open source
  • 2
    Hosted internally
  • 1
    Pipeline could be started manually
  • 1
    Built-in support of Review Apps
  • 1
    Built-in Docker Registry
  • 1
    Built-in support of Kubernetes
  • 1
    Enable or disable pipeline by using env variables
  • 1
    Gitlab templates could be shared across logical group
  • 1
    Easy to setup the dedicated runner to particular job

Sign up to add or upvote prosMake informed product decisions

Cons of Bamboo
Cons of GitLab CI
  • 6
    Expensive
  • 1
    Low community support
  • 1
    Bad UI
  • 1
    Bad integration with docker
  • 2
    Works best with GitLab repositories

Sign up to add or upvote consMake informed product decisions

What is Bamboo?

Focus on coding and count on Bamboo as your CI and build server! Create multi-stage build plans, set up triggers to start builds upon commits, and assign agents to your critical builds and deployments.

What is GitLab CI?

GitLab offers a continuous integration service. If you add a .gitlab-ci.yml file to the root directory of your repository, and configure your GitLab project to use a Runner, then each merge request or push triggers your CI pipeline.

Need advice about which tool to choose?Ask the StackShare community!

What companies use Bamboo?
What companies use GitLab CI?
See which teams inside your own company are using Bamboo or GitLab CI.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Bamboo?
What tools integrate with GitLab CI?

Sign up to get full access to all the tool integrationsMake informed product decisions

What are some alternatives to Bamboo and GitLab CI?
Jenkins
In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
Eucalyptus
Eucalyptus is open source software for building private, AWS-compatible IT, QA, and developer clouds. It makes it easy to deliver cloud computing, just like AWS, from within your data center.
Travis CI
Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.
CircleCI
Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.
GitHub Actions
It makes it easy to automate all your software workflows, now with world-class CI/CD. Build, test, and deploy your code right from GitHub. Make code reviews, branch management, and issue triaging work the way you want.
See all alternatives