we had two instances of the same pipeline, each spewing hundreds of
thousands of builds. this renames the auto-set one to the name used in
the docs. this will also archive the old one.
Signed-off-by: Aidan Oldershaw <aoldershaw@pivotal.io>
The first job should update the pipeline that the job belongs to. If
this doesn't happen then any changes to the pipeline won't take affect
until a second build is triggered
Signed-off-by: Taylor Silva <tsilva@pivotal.io>
Copied all the example pipelines from concourse-ci.org into this repo
and added a new example pipeline to show how the `set_pipeline` step
works
Signed-off-by: Taylor Silva <tsilva@pivotal.io>
Aidan Oldershaw
Taylor Silva