The pipeline is the heart and soul of Wercker. It’s where you define the actions (steps) and environment for your tasks. It’s also often where you define your tests, builds and deploys. They are an aggregate of steps and will pass or fail based on the steps within.
Each pipeline also comes with an environment. Some environments are set by default by the Wercker tool. When run on wercker.com, they are defined by the settings you’ve entered on wercker.com.
Steps are the actions performed within pipelines.
The configuration file and format for your pipelines is the wercker.yml file.
Every artefact from a build pipeline is both a Docker container as well as a
tarball of the source code.