When comparing Buildkite vs Bitbucket Pipelines, the Slant community recommends Bitbucket Pipelines for most people. In the question“What are the best continuous integration tools?” Bitbucket Pipelines is ranked 22nd while Buildkite is ranked 23rd. The most important reason people chose Bitbucket Pipelines is:
Eg: ./1.setup.sh 48s ./2.build.sh 56s With this information, it's easy to find out which line of the script is the bottleneck of the build process.
Ranked in these QuestionsQuestion Ranking
Pro Very easy to set up
The web UI allows writing a build script inline, running a script from your repository, or creating a whole pipeline. Docker support is built-in.
Pro Allows parallel jobs
Buildkite allows you to configure your build in order to run parallel jobs and obtain considerably faster results.
Pro Scheduled builds
Run builds on a cron-like schedule to rebuild a master branch or run an import process.
Pro Run your own build servers
Run an agent on your own servers (AWS, etc) so that you have control over what your builds can access.
Pro Intergrates with VCS
Integrates with GitHub, GitHub Enterprise, Bitbucket, Bitbucket Server, GitLab, Codebase, or any custom Git repository.
One plan that gives you everything at a reasonable price.
Pro Plugin support for docker and docker-compose
Pro Concurrency control
Make sure only one deploy build runs at a time with concurrency control.
Pro Config driven build process
While you can define your build process in the dashboard, you can also run it from config files in the repository.
Pro Responsive support
Support respond quickly and listen to feedback.
Pro Provides time taken for each step
With this information, it's easy to find out which line of the script is the bottleneck of the build process.
Pro Great Jira integration
The same company Atlassian built Jira, which provides top-tier integration with Jira.
Pro Combined service: source control and CI
Con Only 50 mins/month free usage
The Free plan only gives you 50 minutes per month to run the build.