Bitbucket Pipelines聽vs聽CircleCI

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

Bitbucket Pipelines

281
251
+ 1
0
CircleCI

9.3K
5.4K
+ 1
961
Add tool

Bitbucket Pipelines vs CircleCI: What are the differences?

What is Bitbucket Pipelines? An Integrated continuous integration and continuous deployment for Bitbucket. It is an Integrated continuous integration and continuous deployment for Bitbucket Cloud that's trivial to set up, automating your code from test to production. Our mission is to enable all teams to ship software faster by driving the practice of continuous delivery.

What is CircleCI? Automate your development process quickly, safely, and at scale. 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.

Bitbucket Pipelines and CircleCI belong to "Continuous Integration" category of the tech stack.

Some of the features offered by Bitbucket Pipelines are:

  • Continuous integration and delivery
  • Map the branch structure
  • Run as service

On the other hand, CircleCI provides the following key features:

  • Language-Inclusive Support
  • Custom Environments
  • Flexible Resource Allocation

Instacart, Lyft, and StackShare are some of the popular companies that use CircleCI, whereas Bitbucket Pipelines is used by SmArtapps, Simian, and ADEXT. CircleCI has a broader approval, being mentioned in 944 company stacks & 388 developers stacks; compared to Bitbucket Pipelines, which is listed in 21 company stacks and 4 developer stacks.

Advice on Bitbucket Pipelines and CircleCI
Needs advice
on
Jenkins XJenkins XGitLab CIGitLab CI
and
CircleCICircleCI

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
Needs advice
on
JenkinsJenkinsTravis CITravis CI
and
CircleCICircleCI

From a StackShare Community member: "Currently we use Travis CI and have optimized it as much as we can so our builds are fairly quick. Our boss is all about redundancy so we are looking for another solution to fall back on in case Travis goes down and/or jacks prices way up (they were recently acquired). Could someone recommend which CI we should go with and if they have time, an explanation of how they're different?"

See more
Replies (6)
Dustin Falgout
Developer at Elegant Themes | 13 upvotes 路 259.8K views

We use CircleCI because of the better value it provides in its plans. I'm sure we could have used Travis just as easily but we found CircleCI's pricing to be more reasonable. In the two years since we signed up, the service has improved. CircleCI is always innovating and iterating on their platform. We have been very satisfied.

See more
Peter Thomas
Distinguished Engineer at Intuit | 9 upvotes 路 238.9K views
Recommends
Travis CITravis CI
at

As the maintainer of the Karate DSL open-source project - I found Travis CI very easy to integrate into the GitHub workflow and it has been steady sailing for more than 2 years now ! It works well for Java / Apache Maven projects and we were able to configure it to use the latest Oracle JDK as per our needs. Thanks to the Travis CI team for this service to the open-source community !

See more

I use Google Cloud Build because it's my first foray into the CICD world(loving it so far), and I wanted to work with something GCP native to avoid giving permissions to other SaaS tools like CircleCI and Travis CI.

I really like it because it's free for the first 120 minutes, and it's one of the few CICD tools that enterprises are open to using since it's contained within GCP.

One of the unique things is that it has the Kaniko cache, which speeds up builds by creating intermediate layers within the docker image vs. pushing the full thing from the start. Helpful when you're installing just a few additional dependencies.

Feel free to checkout an example: Cloudbuild Example

See more
Recommends
Travis CITravis CI

I use Travis CI because of various reasons - 1. Cloud based system so no dedicated server required, and you do not need to administrate it. 2. Easy YAML configuration. 3. Supports Major Programming Languages. 4. Support of build matrix 6. Supports AWS, Azure, Docker, Heroku, Google Cloud, Github Pages, PyPi and lot more. 7. Slack Notifications.

See more
Oded Arbel
Recommends
GitLab CIGitLab CI

You are probably looking at another hosted solution: Jenkins is a good tool but it way too work intensive to be used as just a backup solution.

I have good experience with Circle-CI, Codeship, Drone.io and Travis (as well as problematic experiences with all of them), but my go-to tool is Gitlab CI: simple, powerful and if you have problems with their limitations or pricing, you can always install runners somewhere and use Gitlab just for scheduling and management. Even if you don't host your git repository at Gitlab, you can have Gitlab pull changes automatically from wherever you repo lives.

See more
Recommends
BuildkiteBuildkite

If you are considering Jenkins I would recommend at least checking out Buildkite. The agents are self-hosted (like Jenkins) but the interface is hosted for you. It meshes up some of the things I like about hosted services (pipeline definitions in YAML, managed interface and authentication) with things I like about Jenkins (local customizable agent images, secrets only on own instances, custom agent level scripts, sizing instances to your needs).

See more
Decisions about Bitbucket Pipelines and CircleCI

My website is brand new and one of the few requirements of testings I had to implement was code coverage. Never though it was so hard to implement using a #docker container. Given my lack of experience, every attempt I tried on making a simple code coverage test using the 4 combinations of #TravisCI, #CircleCi with #Coveralls, #Codecov I failed. The main problem was I was generating the .coverage file within the docker container and couldn't access it with #TravisCi or #CircleCi, every attempt to solve this problem seems to be very hacky and this was not the kind of complexity I want to introduce to my newborn website. This problem was solved using a specific action for #GitHubActions, it was a 3 line solution I had to put in my github workflow file and I was able to access the .coverage file from my docker container and get the coverage report with #Codecov.

See more

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

We were long time users of TravisCI, but switched to CircleCI because of the better user interface and pricing. Version 2.0 has had a couple of trips and hiccups; but overall we've been very happy with the continuous integration it provides. Continuous Integration is a must-have for building software, and CircleCI continues to surprise as they roll out ideas and features. It's leading the industry in terms of innovation and new ideas, and it's exciting to see what new things they keep rolling out.

See more

Jenkins is a pretty flexible, complete tool. Especially I love the possibility to configure jobs as a code with Jenkins pipelines.

CircleCI is well suited for small projects where the main task is to run continuous integration as quickly as possible. Travis CI is recommended primarily for open-source projects that need to be tested in different environments.

And for something a bit larger I prefer to use Jenkins because it is possible to make serious system configuration thereby different plugins. In Jenkins, I can change almost anything. But if you want to start the CI chain as soon as possible, Jenkins may not be the right choice.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Bitbucket Pipelines
Pros of CircleCI
    Be the first to leave a pro
    • 224
      Github integration
    • 176
      Easy setup
    • 152
      Fast builds
    • 94
      Competitively priced
    • 74
      Slack integration
    • 54
      Docker support
    • 44
      Awesome UI
    • 33
      Great customer support
    • 18
      Ios support
    • 14
      Hipchat integration
    • 12
      SSH debug access
    • 11
      Free for Open Source
    • 5
      Mobile support
    • 5
      Bitbucket integration
    • 4
      Nodejs support
    • 4
      AWS CodeDeploy integration
    • 3
      YAML configuration
    • 3
      Free for Github private repo
    • 3
      Great support
    • 2
      Clojure
    • 2
      Simple, clean UI
    • 2
      Clojurescript
    • 2
      OSX support
    • 2
      Continuous Deployment
    • 1
      Android support
    • 1
      Autoscaling
    • 1
      Fair pricing
    • 1
      All inclusive testing
    • 1
      Helpful documentation
    • 1
      Japanese in rspec comment appears OK
    • 1
      Favorite
    • 1
      Build PR Branch Only
    • 1
      Really easy to use
    • 1
      Unstable
    • 1
      So circular
    • 1
      Easy setup, easy to understand, fast and reliable
    • 1
      Parallel builds for slow test suites
    • 1
      Easy setup. 2.0 is fast!
    • 1
      Parallelism
    • 1
      Extremely configurable
    • 1
      Easy to deploy to private servers
    • 1
      Works

    Sign up to add or upvote prosMake informed product decisions

    Cons of Bitbucket Pipelines
    Cons of CircleCI
      Be the first to leave a con
      • 12
        Unstable
      • 6
        Scammy pricing structure
      • 0
        Aggressive Github permissions

      Sign up to add or upvote consMake informed product decisions

      What is Bitbucket Pipelines?

      It is an Integrated continuous integration and continuous deployment for Bitbucket Cloud that's trivial to set up, automating your code from test to production. Our mission is to enable all teams to ship software faster by driving the practice of continuous delivery.

      What is 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.

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

      What companies use Bitbucket Pipelines?
      What companies use CircleCI?
      See which teams inside your own company are using Bitbucket Pipelines or CircleCI.
      Sign up for Private StackShareLearn More

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

      What tools integrate with Bitbucket Pipelines?
      What tools integrate with CircleCI?

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

      Blog Posts

      GitNode.jsFirebase+5
      7
      1695
      GitHubPythonGit+22
      17
      13463
      GitHubGitDocker+34
      29
      40813
      GitHubGitSlack+30
      25
      15580
      What are some alternatives to Bitbucket Pipelines and CircleCI?
      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.
      GitLab
      GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers.
      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.
      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.
      Envoyer
      Envoyer deploys your PHP applications with zero downtime. Just push your code, and let Envoyer deliver your application to one or many servers without interrupting a single customer. In this series, we'll discuss each feature of Envoyer, demonstrating how to use them with a sample project.
      See all alternatives