Need advice about which tool to choose?Ask the StackShare community!
Bitbucket Pipelines vs wercker: What are the differences?
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; wercker: Build, test, and deploy container-native applications. Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.
Bitbucket Pipelines and wercker can be categorized as "Continuous Integration" tools.
Some of the features offered by Bitbucket Pipelines are:
- Continuous integration and delivery
- Map the branch structure
- Run as service
On the other hand, wercker provides the following key features:
- Pipelines - Wercker's Pipelines enable developers to fully automate builds, tests and deployments with Docker as a first class citizen.
- Workflows - With Workflows: a collection of pipelines can be chained and triggered to achieve complex automation goals.
- Steps Store - A step is a self contained best practice for accomplishing a specific automation task. Build your own or help yourself to our community based store.
FashionUnited, Hazeorid, and Wantedly are some of the popular companies that use wercker, whereas Bitbucket Pipelines is used by SmArtapps, Simian, and ADEXT. wercker has a broader approval, being mentioned in 40 company stacks & 23 developers stacks; compared to Bitbucket Pipelines, which is listed in 21 company stacks and 4 developer stacks.
Pros of Bitbucket Pipelines
Pros of wercker
- Automatic Deployments35
- Free33
- Easy config via yaml25
- Awesome UI23
- Github integration23
- Continuous Deployment22
- Supports both Github and Bitbucket16
- Easy to setup14
- Reliable12
- Bitbucket Integration11
- Community-driven components (boxes and steps)4
- Fast builds4
- Easy to get started4
- Docker based4
- Easy UI3
- Flexible configuration via YAML3
- Multi-target deploys2
- Trigger by branch name1
- Great UI, free and an active Slack channel :)1
- Docker support1
- Multiple configurable build steps1