wercker.yml defines the configuration of your automation pipelines with a collection of Steps that you wish to execute.
wercker.yml you can specify any pipeline you like. There is one special pipeline called
dev which will only be executed when running it with the CLI using the
wercker dev command. Examples of pipeline names:
Upon creating a project in Wercker, we automatically create a
build Workflow with a Git hook which executes a
A pipeline can have its own base box, i.e Docker container that is used as a starting point. You can use different base boxes per pipeline.
Each pipeline can also specify its own Services. For example, a testing Pipeline may require access to a database server, whereas a deploy pipeline probably wouldn't.