Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Buildkite vs Netlify, the Slant community recommends Netlify for most people. In the question“What are the best continuous deployment services?” Netlify is ranked 4th while Buildkite is ranked 14th.
Specs
Question Ranking
Pros
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.
Pro Affordable
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 Netlify CDN
Pro Free one-click SSL
Pro Continuous deployment
Pro Custom domains
Pro Versioning and rollbacks
Pro Free tier
Netlify's PRO Plan now Free for Open-Source Projects
Pro Webhooks and integrations
Pro Redirect, rewrite and proxy rules
Pro Full featured CLI
Pro Custom HTTP headers
Pro Support simple forms
Pro Post processing
The post processing doesn't really work. It's a good idea, though!
Pro Functions
Can deploy aws functions without an aws account.
Pro Multiple environment support
Pro Atomic deploys
Pro RESTful API
Cons
