For information on how these pipeline variables would be used in your configuration see the overview of pipeline variables.
Not all values will be available in all circumstances, for instance, the first push to a repository will not have a pipeline.trigger.base_revision
.
If a value isn’t available it will resolve to an empty string during config expansion, values documented as having a boolean type will resolve to false
.
(THIS LIST IS UNDER DESIGN - FEEDBACK WELCOMED.)
First batch:
pipeline.id
- a globally unique id representing the pipelinepipeline.number
- a project unique integer id for the pipelinepipeline.project.git_url
- e.g. https://github.com/circleci/circleci-docspipeline.project.type
- e.g. “github”pipeline.git.tag
- the tag triggering the pipelinepipeline.git.branch
- the branch triggering the pipelinepipeline.git.revision
- the current git revisionpipeline.git.base_revision
- the previous git revisionSecond batch:
pipeline.project.name
pipeline.project_slug
pipeline.created_timestamp
pipeline.trigger.rerun_of
pipeline.trigger.actor
Other potential variables:
pipeline.pull_request.draft
(boolean)pipeline.pull_request.number
pipeline.pull_request.url
pipeline.pull_request.source_branch
pipeline.pull_request.source_repo
pipeline.pull_request.target_branch
pipeline.pull_request.target_repo
pipeline.pull_request.fork
(boolean - useful, or should we prefer comparing source/target?)
pipeline.project.default_branch
pipeline.project.organization_name
(Speculative):
pipeline.project.settings.*