When comparing Bitbucket Pipelines vs Wercker, the Slant community recommends Wercker for most people. In the question“What are the best continuous integration tools?” Wercker is ranked 8th while Bitbucket Pipelines is ranked 22nd. The most important reason people chose Wercker is:
Wercker is based on Docker and it allows developers to create their own deployment stacks inside Docker containers. These stacks range from programming languages, to services, and even to notifications.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Provides time taken for each step
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.
Pro Great Jira integration
The same company Atlassian built Jira, which provides top-tier integration with Jira.
Pro Combined service: source control and CI
Pro Ability to create and use custom environments
Wercker is based on Docker and it allows developers to create their own deployment stacks inside Docker containers. These stacks range from programming languages, to services, and even to notifications.
Pro Free unlimited number of private repositories CI while in Beta
While in beta, Wercker offers unlimited free public and private repositories.
Pro Social networking elements
Wercker has an activity feed with which different team members can see and follow everything their colleagues have been doing. This gives the tool a certain social network feel, much like GitHub itself.
Cons
Con Only 50 mins/month free usage
The Free plan only gives you 50 minutes per month to run the build.
Con Sparse documentation and examples
