This section describes how pipelines can be defined and updated on the hosted Wercker platform. Creating pipelines To create a new pipeline so that it can be used in Workflows you must:
Note that when creating an application on Wercker Web, a build pipeline, which contains a Git hook and executes a pipeline called build, will be automatically created.
An overview of all your pipelines is available in your appication’s
Workflows tab. Selecting a pipeline allows you to edit its settings.
You can configure a pipeline to run only when you manually trigger it. To do this:
Now when you run this pipeline from the Runs tab, you can see an “approve run” button (like a play button) in front of your pipeline.
Each pipeline can have its own set of environment variables, including SSH keys. You can read more about creating environment variables here.
Each pipeline can have one of the following permission requirements:
Public: If both your application and pipeline are set to public everyone will be able to see the runs executed for that pipeline. If your application is not public, all your collaborators (regardless of their permissions) will be able to see executions for that pipeline.
View runs: Allow only collaborators with ‘view runs’ permissions to manage this pipeline. This option is only available if the application is owned by a user rather than an organisation.
Execute & Manage pipelines: Allow only collaborators with ‘View Execute & Manage workflows’ to manage this pipeline
Admin: Only administrator collaborators can manage this pipeline