Need advice about which tool to choose?Ask the StackShare community!
Azure Pipelines vs wercker: What are the differences?
Azure Pipelines: Continuously build, test, and deploy to any platform and cloud. Fast builds with parallel jobs and test execution. Use container jobs to create consistent and reliable builds with the exact tools you need. Create new containers with ease and push them to any registry; wercker: Build, test, and deploy container-native applications. Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.
Azure Pipelines and wercker can be primarily classified as "Continuous Integration" tools.
Some of the features offered by Azure Pipelines are:
- Any language, any platform
- Containers and Kubernetes
- Extensible
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.
According to the StackShare community, wercker has a broader approval, being mentioned in 40 company stacks & 23 developers stacks; compared to Azure Pipelines, which is listed in 7 company stacks and 8 developer stacks.
We are currently using Azure Pipelines for continous integration. Our applications are developed witn .NET framework. But when we look at the online Jenkins is the most widely used tool for continous integration. Can you please give me the advice which one is best to use for my case Azure pipeline or jenkins.
If your source code is on GitHub, also take a look at Github actions. https://github.com/features/actions
Pros of Azure Pipelines
- Easy to get started4
- Unlimited CI/CD minutes3
- Built by Microsoft3
- Yaml support2
- Docker support2
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