A Step is self-contained bash script or compiled binary for accomplishing specific automation tasks.
For example, a pip install, kubectl or a Docker push.
Because steps are small isolated actions they are portable, repeatable and reusable. They can be created from scratch or consumed from our open steps marketplace.
Pipelines are a series of steps that are triggered on a git push or the completion of another pipeline.
For example, a pipeline can be a build, push to a registry or a deploy.
The combination of multiple pipelines results in a Workflow.
Workflows are a set of chained and branched pipelines that allow you to form multi-stage, multi-branch complex CI/CD flows that take your project from code to production.
A workflow could be your end-to-end build and testing flow that deploys your application to multiple environments.
All Wercker pipelines execute inside a Docker container and every build artifact can be a Docker container.
Wercker pipelines enable you to spin up multiple containers alongside each other at the same time which is ideal for building and testing microservices in parallel.
With Wercker you can push your images to any container registry public or private such as Docker Hub, Quay, Amazon EC2 container registry and Google container registry using steps.
Wercker also enables you to easily version container artefacts for easy debugging.
After pushing your Docker images to any public or private registry, you're ready to deploy to any cloud provider.
Wercker natively supports common schedulers such as Kubernetes, Google Container Engine, Marathon and EC2 Container Service.