Buildkite vs DotCi: What are the differences?
Buildkite: Fast, secure and scalable CI/CD for all your software projects. CI and build automation tool that combines the power of your own build infrastructure with the convenience of a managed, centralized web UI. Used by Shopify, Basecamp, Digital Ocean, Venmo, Cochlear, Bugsnag and more; DotCi: Jenkins plugin with GitHub and Docker integration. DotCi is a Jenkins plugin created by Groupon that makes job management easy with built-in GitHub integration, push-button job creation, and YAML powered build configuration and customization. It comes prepackaged with Docker support as well, which means bootstrapping a new build environment from scratch can take as little as 15 minutes. DotCi has been a critical tool for Groupon internally for managing build and release pipelines for the wide variety of technologies in their SOA landscape.
Buildkite and DotCi can be categorized as "Continuous Integration" tools.
Some of the features offered by Buildkite are:
- Fast and stable builds
- Open source agent runs on almost any machine and architecture
- Freedom to use your own internal or pre-release tools and services
On the other hand, DotCi provides the following key features:
- Deep Integration with Source Control – for us that’s Github Enterprise
- Integration with Github webhooks
- Feedback sent to the committer or pusher via Email, Hipchat, Campfire, etc.
DotCi is an open source tool with 505 GitHub stars and 65 GitHub forks. Here's a link to DotCi's open source repository on GitHub.
What is Buildkite?
What is DotCi?
Want advice about which of these to choose?Ask the StackShare community!
Why do developers choose DotCi?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Buildkite?
What are the cons of using DotCi?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Buildkite provides testing of the Rails application via a Docker container with Docker Compose. The Buildkite Agent runs on a small Digital Ocean droplet, runs the integration and model tests, and marks the GitHub commit for Heroku to perform their auto-deployments once the build is green.