To list the currently-configured pipelines and their paused state, run:
$ fly -t example pipelines
To rename a pipeline, run:
$ fly -t example rename-pipeline \ --old-name my-pipeline \ --new-name my-cool-pipeline
To pause a pipeline, run:
$ fly -t example pause-pipeline --pipeline my-pipeline
This will prevent jobs from being scheduled and stop the periodic checking for new versions of resources. Builds that are in-flight will still finish.
To unpause a pipeline, run:
$ fly -t example unpause-pipeline --pipeline my-pipeline
This will resume job scheduling and resource checking.
By default, newly configured pipelines are only visible to the pipeline's team. To make a pipeline viewable by other teams and unauthenticated users, run:
$ fly -t example expose-pipeline --pipeline my-pipeline
This feature is useful if you're using Concourse for an open source project and you'd like your community to be able to see into your build pipeline.
To undo this change, see
Exposing a pipeline reveals basically everything but the output of builds. The pipeline will be publicly viewable, as well as resource versions and metadata, which includes things like commit messages. Build output will remain hidden by default unless the job configures
Currently, step names within a build are visible in the API even without
public: true. See concourse #2116 for more info.
If you realize that you've made a terrible mistake in exposing your pipeline, you can run:
$ fly -t example hide-pipeline --pipeline my-pipeline
If you're panicking you can run the command's short form,
Fly can be used to fetch and update the configuration for your pipelines. This is achieved by using the
fly get-pipeline and
fly set-pipeline commands. For example, to fetch the current configuration of your
my-pipeline Concourse pipeline and print it on
STDOUT run the following:
$ fly -t example get-pipeline --pipeline my-pipeline
To get JSON instead of YAML you can use the
--json argument. This can be useful when inspecting your config with jq.
Every now and then you just don't want a pipeline to be around anymore. Running
fly destroy-pipeline will stop the pipeline activity and remove all data collected by the pipeline, including build history and collected versions.
For example, to destroy the
my-pipeline pipeline, you would run:
$ fly -t example destroy-pipeline --pipeline my-pipeline
To configure the ordering of pipelines, run:
$ fly -t example order-pipelines \ --pipeline pipeline-1 \ --pipeline pipeline-2 \ --pipeline pipeline-3
Note that this command only ensures that the given pipelines are in the given order. If there are other pipelines that you haven't included in the command, they may appear in-between, before, or after the given set.