--- title: "Run a pipeline" method: POST path: "/repositories/{workspace}/{repo_slug}/pipelines" tags: ["Pipelines"] --- # Run a pipeline `POST /repositories/{workspace}/{repo_slug}/pipelines` Endpoint to create and initiate a pipeline. There are a number of different options to initiate a pipeline, where the payload of the request will determine which type of pipeline will be instantiated. ## Trigger a pipeline for a branch One way to trigger pipelines is by specifying the branch for which you want to trigger a pipeline. The specified branch will be used to determine which pipeline definition from the `bitbucket-pipelines.yml` file will be applied to initiate the pipeline. The pipeline will then do a clone of the repository and checkout the latest revision of the specified branch. ### Example ``` $ curl -X POST -is -u '{atlassian_account_email}:{api_token}' \ -H 'Content-Type: application/json' \ https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/pipelines/ \ -d ' { "target": { "ref_type": "branch", "type": "pipeline_ref_target", "ref_name": "master" } }' ``` ## Trigger a pipeline for a commit on a branch or tag You can initiate a pipeline for a specific commit and in the context of a specified reference (e.g. a branch, tag or bookmark). The specified reference will be used to determine which pipeline definition from the bitbucket-pipelines.yml file will be applied to initiate the pipeline. The pipeline will clone the repository and then do a checkout the specified reference. The following reference types are supported: * `branch` * `named_branch` * `bookmark` * `tag` ### Example ``` $ curl -X POST -is -u '{atlassian_account_email}:{api_token}' \ -H 'Content-Type: application/json' \ https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/pipelines/ \ -d ' { "target": { "commit": { "type": "commit", "hash": "ce5b7431602f7cbba007062eeb55225c6e18e956" }, "ref_type": "branch", "type": "pipeline_ref_target", "ref_name": "master" } }' ``` ## Trigger a specific pipeline definition for a commit You can trigger a specific pipeline that is defined in your `bitbucket-pipelines.yml` file for a specific commit. In addition to the commit revision, you specify the type and pattern of the selector that identifies the pipeline definition. The resulting pipeline will then clone the repository and checkout the specified revision. ### Example ``` $ curl -X POST -is -u '{atlassian_account_email}:{api_token}' \ -H 'Content-Type: application/json' \ https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/pipelines/ \ -d ' { "target": { "commit": { "hash":"a3c4e02c9a3755eccdc3764e6ea13facdf30f923", "type":"commit" }, "selector": { "type":"custom", "pattern":"Deploy to production" }, "type":"pipeline_commit_target" } }' ``` ## Trigger a specific pipeline definition for a commit on a branch or tag You can trigger a specific pipeline that is defined in your `bitbucket-pipelines.yml` file for a specific commit in the context of a specified reference. In addition to the commit revision, you specify the type and pattern of the selector that identifies the pipeline definition, as well as the reference information. The resulting pipeline will then clone the repository a checkout the specified reference. ### Example ``` $ curl -X POST -is -u '{atlassian_account_email}:{api_token}' \ -H 'Content-Type: application/json' \ https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/pipelines/ \ -d ' { "target": { "commit": { "hash":"a3c4e02c9a3755eccdc3764e6ea13facdf30f923", "type":"commit" }, "selector": { "type": "custom", "pattern": "Deploy to production" }, "type": "pipeline_ref_target", "ref_name": "master", "ref_type": "branch" } }' ``` ## Trigger a custom pipeline with variables In addition to triggering a custom pipeline that is defined in your `bitbucket-pipelines.yml` file as shown in the examples above, you can specify variables that will be available for your build. In the request, provide a list of variables, specifying the following for each variable: key, value, and whether it should be secured or not (this field is optional and defaults to not secured). ### Example ``` $ curl -X POST -is -u '{atlassian_account_email}:{api_token}' \ -H 'Content-Type: application/json' \ https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/pipelines/ \ -d ' { "target": { "type": "pipeline_ref_target", "ref_type": "branch", "ref_name": "master", "selector": { "type": "custom", "pattern": "Deploy to production" } }, "variables": [ { "key": "var1key", "value": "var1value", "secured": true }, { "key": "var2key", "value": "var2value" } ] }' ``` ## Trigger a pull request pipeline You can also initiate a pipeline for a specific pull request. ### Example ``` $ curl -X POST -is -u '{atlassian_account_email}:{api_token}' \ -H 'Content-Type: application/json' \ https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/pipelines/ \ -d ' { "target": { "type": "pipeline_pullrequest_target", "source": "pull-request-branch", "destination": "master", "destination_commit": { "hash": "9f848b7" }, "commit": { "hash": "1a372fc" }, "pullrequest": { "id": "3" }, "selector": { "type": "pull-requests", "pattern": "**" } } }' ``` # On-demand pipeline By default, pipelines run using the YAML in the repository’s `bitbucket-pipelines.yml` configuration file. With an _on-demand_ pipeline, you include the pipeline’s YAML in the request body. That YAML applies only to that run and overrides the YAML in `bitbucket-pipelines.yml`. Just like with regular pipelines, there is a number of different options to initiate an on-demand pipeline. However, since the payload contains YAML configuration in this case, _query parameters_ are used to supply the necessary metadata to determine which type of pipeline will be instantiated. These query parameters are derived from the JSON equivalent by turning each property into a key-value pair with the JSON path of the property as the new key. ## Trigger on-demand pipeline for a branch You can initiate an on-demand pipeline for a specific branch. This branch will be used to determine which pipeline definition from the supplied YAML configuration will be applied to initiate the pipeline. The pipeline will then do a clone of the repository and check out the latest revision of the specified branch. To trigger an on-demand pipeline for a _branch_ the requesting user must have **write permission** for that branch (which can be limited by [branch restrictions](https://support.atlassian.com/bitbucket-cloud/docs/use-branch-permissions/)). ### Example ``` $ curl -X POST -is -u '{atlassian_account_email}:{api_token}' \ -H 'Content-Type: application/yaml' \ https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/pipelines?target.type=pipeline_ref_target&target.ref_type=branch&target.ref_name=master \ -d ' pipelines: default: - step: script: - echo This is an on-demand pipeline' ``` ## Trigger on-demand pipeline for a commit on a branch or tag You can initiate an on-demand pipeline for a specific commit and in the context of a specified reference (branch or tag). The specified reference will be used to determine which pipeline definition from the supplied YAML configuration will be applied to initiate the pipeline. The pipeline will clone the repository and check out the specified reference. To trigger an on-demand pipeline for a _branch_ the requesting user must have **write permission** for that branch (which can be limited by [branch restrictions](https://support.atlassian.com/bitbucket-cloud/docs/use-branch-permissions/)). ### Example ``` $ curl -X POST -is -u '{atlassian_account_email}:{api_token}' \ -H 'Content-Type: application/yaml' \ https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/pipelines?target.type=pipeline_ref_target&target.ref_type=branch&target.ref_name=master&target.commit.hash=ce5b7431602f7cbba007062eeb55225c6e18e956 \ -d ' pipelines: default: - step: script: - echo This is an on-demand pipeline' ``` ## Trigger a specific on-demand pipeline definition for a commit You can trigger a specific pipeline that is defined in the supplied YAML configuration for a specific commit. In addition to the commit revision, you specify the type and pattern of the selector that identifies the pipeline definition. The resulting pipeline will then clone the repository and checkout the specified revision. ### Example ``` $ curl -X POST -is -u '{atlassian_account_email}:{api_token}' \ -H 'Content-Type: application/yaml' \ https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/pipelines?target.type=pipeline_commit_target&target.commit.hash=a3c4e02c9a3755eccdc3764e6ea13facdf30f923&target.selector.type=custom&target.selector.pattern=security-scan \ -d ' pipelines: custom: security-scan: - step: script: - echo Run on-demand security scan ``` ## Trigger a custom on-demand pipeline with variables In addition to triggering a custom on-demand pipeline that is defined in the supplied YAML configuration as shown in the examples above, you can specify variables that will be available for your build. In the request, provide each variable as an indexed set of query parameters representing its key, value, and whether it should be secured or not (this field is optional and defaults to not secured). ### Example ``` $ curl -X POST -is -u '{atlassian_account_email}:{api_token}' \ -H 'Content-Type: application/yaml' \ https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/pipelines?target.type=pipeline_ref_target&target.ref_type=branch&target.ref_name=master&target.selector.type=custom&target.selector.pattern=security-scan&variables[0].key=var1key&variables[0].value=var1value&variables[0].secured=true&variables[1].key=var2key&variables[1].value=var2value \ -d ' pipelines: custom: security-scan: - variables: - name: var1key - name: var2key - step: script: - echo Run on-demand security scan' ``` ## Trigger a pull request pipeline You can also initiate an on-demand pipeline for a specific pull request. ### Example ``` $ curl -X POST -is -u '{atlassian_account_email}:{api_token}' \ -H 'Content-Type: application/yaml' \ https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/pipelines?target.type=pipeline_pullrequest_target&target.source=pull-request-branch&target.destination=destination&target.destination_commit.hash=9f848b7&target.commit.hash=1a372fc&target.pullrequest.id=3&target.selector.type=pull-requests&target.selector.pattern=** \ -d ' pipelines: pull-requests: "**": - step: script: - echo This is an on-demand pipeline' ``` ## Path parameters - `workspace` string, required - `repo_slug` string, required ## Request body - Pipeline — A Bitbucket Pipeline. This represents an actual pipeline result. - `type` string, required - `uuid` string — The UUID identifying the pipeline. - `build_number` integer — The build number of the pipeline. - `creator` Account — An account object. - `type` string, required - `links` AccountLinks — Links related to an Account. - `avatar` Link — A link to a resource related to this object. - `href` string, uri - `name` string - `created_on` string, date-time - `display_name` string - `uuid` string - `repository` Repository — A Bitbucket repository. - `type` string, required - `links` object - `self` object — A link to a resource related to this object. - `href` string, uri - `name` string - `html` object — A link to a resource related to this object. - `href` string, uri - `name` string - `avatar` object — A link to a resource related to this object. - `href` string, uri - `name` string - `pullrequests` object — A link to a resource related to this object. - `href` string, uri - `name` string - `commits` object — A link to a resource related to this object. - `href` string, uri - `name` string - `forks` object — A link to a resource related to this object. - `href` string, uri - `name` string - `watchers` object — A link to a resource related to this object. - `href` string, uri - `name` string - `downloads` object — A link to a resource related to this object. - `href` string, uri - `name` string - `clone` object[] - `href` string, uri - `name` string - `hooks` object — A link to a resource related to this object. - `href` string, uri - `name` string - `uuid` string — The repository's immutable id. This can be used as a substitute for the slug segment in URLs. Doing this guarantees your URLs will survive renaming of the repository by its owner, or even transfer of the repository to a different user. - `full_name` string — The concatenation of the repository owner's username and the slugified name, e.g. "evzijst/interruptingcow". This is the same string used in Bitbucket URLs. - `is_private` boolean - `parent` Repository — recursive - `scm` 'git' - `owner` Account — An account object. - `type` string, required - `links` AccountLinks — Links related to an Account. - `avatar` Link — A link to a resource related to this object. - `href` string, uri - `name` string - `created_on` string, date-time - `display_name` string - `uuid` string - `name` string - `description` string - `created_on` string, date-time - `updated_on` string, date-time - `size` integer - `language` string - `has_issues` boolean — The issue tracker for this repository is enabled. Issue Tracker features are not supported for repositories in workspaces administered through admin.atlassian.com. - `has_wiki` boolean — The wiki for this repository is enabled. Wiki features are not supported for repositories in workspaces administered through admin.atlassian.com. - `fork_policy` 'allow_forks' | 'no_public_forks' | 'no_forks' — Controls the rules for forking this repository. * **allow_forks**: unrestricted forking * **no_public_forks**: restrict forking to private forks (forks cannot be made public later) * **no_forks**: deny all forking - `project` Project — A Bitbucket project. Projects are used by teams to organize repositories. - `type` string, required - `links` object - `html` object — A link to a resource related to this object. - `href` string, uri - `name` string - `avatar` object — A link to a resource related to this object. - `href` string, uri - `name` string - `uuid` string — The project's immutable id. - `key` string — The project's key. - `owner` Team — A team object. - `type` string, required - `links` object — Links related to a Team. - `avatar` Link — A link to a resource related to this object. - `href` string, uri - `name` string - `self` Link — A link to a resource related to this object. - `href` string, uri - `name` string - `html` Link — A link to a resource related to this object. - `href` string, uri - `name` string - `members` Link — A link to a resource related to this object. - `href` string, uri - `name` string - `projects` Link — A link to a resource related to this object. - `href` string, uri - `name` string - `repositories` Link — A link to a resource related to this object. - `href` string, uri - `name` string - `created_on` string, date-time - `display_name` string - `uuid` string - `name` string — The name of the project. - `description` string - `is_private` boolean — Indicates whether the project is publicly accessible, or whether it is private to the team and consequently only visible to team members. Note that private projects cannot contain public repositories. - `created_on` string, date-time - `updated_on` string, date-time - `has_publicly_visible_repos` boolean — Indicates whether the project contains publicly visible repositories. Note that private projects cannot contain public repositories. - `mainbranch` Branch — A branch object, representing a branch in a repository. - `type` string, required - `links` object - `self` object — A link to a resource related to this object. - `href` string, uri - `name` string - `commits` object — A link to a resource related to this object. - `href` string, uri - `name` string - `html` object — A link to a resource related to this object. - `href` string, uri - `name` string - `name` string — The name of the ref. - `target` Commit — A repository commit object. - `type` string, required - `hash` string - `date` string, date-time - `author` Author — The author of a change in a repository - `type` string, required - `raw` string — The raw author value from the repository. This may be the only value available if the author does not match a user in Bitbucket. - `user` Account — An account object. - `type` string, required - `links` AccountLinks — Links related to an Account. - … - `created_on` string, date-time - `display_name` string - `uuid` string - `committer` Committer — The committer of a change in a repository - `type` string, required - `raw` string — The raw committer value from the repository. This may be the only value available if the committer does not match a user in Bitbucket. - `user` Account — An account object. - `type` string, required - `links` AccountLinks — Links related to an Account. - … - `created_on` string, date-time - `display_name` string - `uuid` string - `message` string - `summary` object - `raw` string — The text as it was typed by a user. - `markup` 'markdown' | 'creole' | 'plaintext' — The type of markup language the raw content is to be interpreted in. - `html` string — The user's content rendered as HTML. - `parents` BaseCommit[] - `type` string, required - `hash` string - `date` string, date-time - `author` Author — The author of a change in a repository - `type` string, required - `raw` string — The raw author value from the repository. This may be the only value available if the author does not match a user in Bitbucket. - `user` Account — An account object. - … - `committer` Committer — The committer of a change in a repository - `type` string, required - `raw` string — The raw committer value from the repository. This may be the only value available if the committer does not match a user in Bitbucket. - `user` Account — An account object. - … - `message` string - `summary` object - `raw` string — The text as it was typed by a user. - `markup` 'markdown' | 'creole' | 'plaintext' — The type of markup language the raw content is to be interpreted in. - `html` string — The user's content rendered as HTML. - `parents` BaseCommit[] - `repository` Repository — recursive - `participants` Participant[] - `type` string, required - `user` Account — An account object. - `type` string, required - `links` AccountLinks — Links related to an Account. - … - `created_on` string, date-time - `display_name` string - `uuid` string - `role` 'PARTICIPANT' | 'REVIEWER' - `approved` boolean - `state` string - `participated_on` string, date-time — The ISO8601 timestamp of the participant's action. For approvers, this is the time of their approval. For commenters and pull request reviewers who are not approvers, this is the time they last commented, or null if they have not commented. - `merge_strategies` string[] — Available merge strategies for pull requests targeting this branch. - `default_merge_strategy` string — The default merge strategy for pull requests targeting this branch. - `target` PipelineTarget — A representation of the target that a pipeline executes on. - `type` string, required - `trigger` PipelineTrigger — A representation of the trigger used for a pipeline. - `type` string, required - `state` PipelineState — The representation of the progress state of a pipeline. - `type` string, required - `variables` PipelineVariable[] — The variables for the pipeline. - `type` string, required - `uuid` string — The UUID identifying the variable. - `key` string — The unique name of the variable. - `value` string — The value of the variable. If the variable is secured, this will be empty. - `secured` boolean — If true, this variable will be treated as secured. The value will never be exposed in the logs or the REST API. - `created_on` string, date-time — The timestamp when the pipeline was created. - `completed_on` string, date-time — The timestamp when the Pipeline was completed. This is not set if the pipeline is still in progress. - `build_seconds_used` integer — The number of build seconds used by this pipeline. - `configuration_sources` PipelineConfigurationSource[] — An ordered list of sources of the pipeline configuration - `source` string, required — Identifier of the configuration source - `uri` string, uri, required — Link to the configuration source view or its immediate content - `links` PipelinesPipelineLinks — Links section for a Pipeline. - `type` string, required - `self` PipelinesLinksSectionHref — A links section href - `type` string, required - `href` string, uri — A link - `steps` PipelinesLinksSectionHref — A links section href - `type` string, required - `href` string, uri — A link ## Response `201` The initiated pipeline. - Pipeline — A Bitbucket Pipeline. This represents an actual pipeline result. - `type` string, required - `uuid` string — The UUID identifying the pipeline. - `build_number` integer — The build number of the pipeline. - `creator` Account — An account object. - `type` string, required - `links` AccountLinks — Links related to an Account. - `avatar` Link — A link to a resource related to this object. - `href` string, uri - `name` string - `created_on` string, date-time - `display_name` string - `uuid` string - `repository` Repository — A Bitbucket repository. - `type` string, required - `links` object - `self` object — A link to a resource related to this object. - `href` string, uri - `name` string - `html` object — A link to a resource related to this object. - `href` string, uri - `name` string - `avatar` object — A link to a resource related to this object. - `href` string, uri - `name` string - `pullrequests` object — A link to a resource related to this object. - `href` string, uri - `name` string - `commits` object — A link to a resource related to this object. - `href` string, uri - `name` string - `forks` object — A link to a resource related to this object. - `href` string, uri - `name` string - `watchers` object — A link to a resource related to this object. - `href` string, uri - `name` string - `downloads` object — A link to a resource related to this object. - `href` string, uri - `name` string - `clone` object[] - `href` string, uri - `name` string - `hooks` object — A link to a resource related to this object. - `href` string, uri - `name` string - `uuid` string — The repository's immutable id. This can be used as a substitute for the slug segment in URLs. Doing this guarantees your URLs will survive renaming of the repository by its owner, or even transfer of the repository to a different user. - `full_name` string — The concatenation of the repository owner's username and the slugified name, e.g. "evzijst/interruptingcow". This is the same string used in Bitbucket URLs. - `is_private` boolean - `parent` Repository — recursive - `scm` 'git' - `owner` Account — An account object. - `type` string, required - `links` AccountLinks — Links related to an Account. - `avatar` Link — A link to a resource related to this object. - `href` string, uri - `name` string - `created_on` string, date-time - `display_name` string - `uuid` string - `name` string - `description` string - `created_on` string, date-time - `updated_on` string, date-time - `size` integer - `language` string - `has_issues` boolean — The issue tracker for this repository is enabled. Issue Tracker features are not supported for repositories in workspaces administered through admin.atlassian.com. - `has_wiki` boolean — The wiki for this repository is enabled. Wiki features are not supported for repositories in workspaces administered through admin.atlassian.com. - `fork_policy` 'allow_forks' | 'no_public_forks' | 'no_forks' — Controls the rules for forking this repository. * **allow_forks**: unrestricted forking * **no_public_forks**: restrict forking to private forks (forks cannot be made public later) * **no_forks**: deny all forking - `project` Project — A Bitbucket project. Projects are used by teams to organize repositories. - `type` string, required - `links` object - `html` object — A link to a resource related to this object. - `href` string, uri - `name` string - `avatar` object — A link to a resource related to this object. - `href` string, uri - `name` string - `uuid` string — The project's immutable id. - `key` string — The project's key. - `owner` Team — A team object. - `type` string, required - `links` object — Links related to a Team. - `avatar` Link — A link to a resource related to this object. - `href` string, uri - `name` string - `self` Link — A link to a resource related to this object. - `href` string, uri - `name` string - `html` Link — A link to a resource related to this object. - `href` string, uri - `name` string - `members` Link — A link to a resource related to this object. - `href` string, uri - `name` string - `projects` Link — A link to a resource related to this object. - `href` string, uri - `name` string - `repositories` Link — A link to a resource related to this object. - `href` string, uri - `name` string - `created_on` string, date-time - `display_name` string - `uuid` string - `name` string — The name of the project. - `description` string - `is_private` boolean — Indicates whether the project is publicly accessible, or whether it is private to the team and consequently only visible to team members. Note that private projects cannot contain public repositories. - `created_on` string, date-time - `updated_on` string, date-time - `has_publicly_visible_repos` boolean — Indicates whether the project contains publicly visible repositories. Note that private projects cannot contain public repositories. - `mainbranch` Branch — A branch object, representing a branch in a repository. - `type` string, required - `links` object - `self` object — A link to a resource related to this object. - `href` string, uri - `name` string - `commits` object — A link to a resource related to this object. - `href` string, uri - `name` string - `html` object — A link to a resource related to this object. - `href` string, uri - `name` string - `name` string — The name of the ref. - `target` Commit — A repository commit object. - `type` string, required - `hash` string - `date` string, date-time - `author` Author — The author of a change in a repository - `type` string, required - `raw` string — The raw author value from the repository. This may be the only value available if the author does not match a user in Bitbucket. - `user` Account — An account object. - `type` string, required - `links` AccountLinks — Links related to an Account. - … - `created_on` string, date-time - `display_name` string - `uuid` string - `committer` Committer — The committer of a change in a repository - `type` string, required - `raw` string — The raw committer value from the repository. This may be the only value available if the committer does not match a user in Bitbucket. - `user` Account — An account object. - `type` string, required - `links` AccountLinks — Links related to an Account. - … - `created_on` string, date-time - `display_name` string - `uuid` string - `message` string - `summary` object - `raw` string — The text as it was typed by a user. - `markup` 'markdown' | 'creole' | 'plaintext' — The type of markup language the raw content is to be interpreted in. - `html` string — The user's content rendered as HTML. - `parents` BaseCommit[] - `type` string, required - `hash` string - `date` string, date-time - `author` Author — The author of a change in a repository - `type` string, required - `raw` string — The raw author value from the repository. This may be the only value available if the author does not match a user in Bitbucket. - `user` Account — An account object. - … - `committer` Committer — The committer of a change in a repository - `type` string, required - `raw` string — The raw committer value from the repository. This may be the only value available if the committer does not match a user in Bitbucket. - `user` Account — An account object. - … - `message` string - `summary` object - `raw` string — The text as it was typed by a user. - `markup` 'markdown' | 'creole' | 'plaintext' — The type of markup language the raw content is to be interpreted in. - `html` string — The user's content rendered as HTML. - `parents` BaseCommit[] - `repository` Repository — recursive - `participants` Participant[] - `type` string, required - `user` Account — An account object. - `type` string, required - `links` AccountLinks — Links related to an Account. - … - `created_on` string, date-time - `display_name` string - `uuid` string - `role` 'PARTICIPANT' | 'REVIEWER' - `approved` boolean - `state` string - `participated_on` string, date-time — The ISO8601 timestamp of the participant's action. For approvers, this is the time of their approval. For commenters and pull request reviewers who are not approvers, this is the time they last commented, or null if they have not commented. - `merge_strategies` string[] — Available merge strategies for pull requests targeting this branch. - `default_merge_strategy` string — The default merge strategy for pull requests targeting this branch. - `target` PipelineTarget — A representation of the target that a pipeline executes on. - `type` string, required - `trigger` PipelineTrigger — A representation of the trigger used for a pipeline. - `type` string, required - `state` PipelineState — The representation of the progress state of a pipeline. - `type` string, required - `variables` PipelineVariable[] — The variables for the pipeline. - `type` string, required - `uuid` string — The UUID identifying the variable. - `key` string — The unique name of the variable. - `value` string — The value of the variable. If the variable is secured, this will be empty. - `secured` boolean — If true, this variable will be treated as secured. The value will never be exposed in the logs or the REST API. - `created_on` string, date-time — The timestamp when the pipeline was created. - `completed_on` string, date-time — The timestamp when the Pipeline was completed. This is not set if the pipeline is still in progress. - `build_seconds_used` integer — The number of build seconds used by this pipeline. - `configuration_sources` PipelineConfigurationSource[] — An ordered list of sources of the pipeline configuration - `source` string, required — Identifier of the configuration source - `uri` string, uri, required — Link to the configuration source view or its immediate content - `links` PipelinesPipelineLinks — Links section for a Pipeline. - `type` string, required - `self` PipelinesLinksSectionHref — A links section href - `type` string, required - `href` string, uri — A link - `steps` PipelinesLinksSectionHref — A links section href - `type` string, required - `href` string, uri — A link ## Other responses - `400` — The account or repository is not enabled, the yml file does not exist in the repository for the given revision, or the request body contained invalid properties. - `404` — The account or repository was not found. --- [API](https://skmtc.net/bitbucket/apis/bitbucket-api.md) · [All operations](https://skmtc.net/bitbucket/apis/bitbucket-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/bitbucket/bitbucket-api/versions/4ec8bd2515c5/schema)