Wercker yml

The wercker.yml defines the configuration of your automation pipelines with a collection of steps that you wish to execute.

In your 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: build-base-container, build, push-to-registry, deploy-kubernetes.

Upon creating a project in Wercker, we automatically create a build Workflow with a Git hook that executes a build pipeline.

A pipeline can have its own base box. For example, it might use a Docker container as a starting point. You can use different base boxes for each 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 would not.

Learn more about creating a wercker.yml file