Optional
deploymentsThe entities to associate the Deployment information with. It must contain at least one of IssueIdOrKeysAssociation or ServiceIdOrKeysAssociation.
Optional
commands?: { command?: string }[]A list of commands to be actioned for this Deployment
This is the identifier for the deployment. It must be unique for the specified pipeline and environment. It must be a monotonically increasing number, as this is used to sequence the deployments.
A short description of the deployment
The human-readable name for the deployment. Will be shown in the UI.
The environment that the deployment is present in.
The name of the environment to present to the user.
The identifier of this environment, must be unique for the provider so that it can be shared across pipelines.
The type of the environment.
Optional
label?: stringAn (optional) additional label that may be displayed with deployment information. Can be used to display version information etc. for the deployment.
The last-updated timestamp to present to the user as a summary of the state of the deployment.
This object models the Continuous Delivery (CD) Pipeline concept, an automated process (usually comprised of multiple stages) for getting software from version control right through to the production environment.
The name of the pipeline to present to the user.
The identifier of this pipeline, must be unique for the provider.
A URL users can use to link to this deployment pipeline.
Optional
schemaVersion?: stringThe DeploymentData schema version used for this deployment data.
Placeholder to support potential schema changes in the future.
The state of the deployment
Optional
triggeredBy?: { email?: string }Describes the user who triggered the deployment
Optional
email?: stringThe email address of the user. Used to associate the user with a Jira user. Max length is 255 characters.
A number used to apply an order to the updates to the deployment, as identified by the deploymentSequenceNumber, in the case of out-of-order receipt of update requests. It must be a monotonically increasing number. For example, epoch time could be one way to generate the updateSequenceNumber.
A URL users can use to link to this deployment, in this environment.
Optional
propertiesProperties assigned to deployment data that can then be used for delete / query operations.
Examples might be an account or user ID that can then be used to clean up data if an account is removed from the Provider system.
Properties are supplied as key/value pairs, and a maximum of 5 properties can be supplied, keys cannot contain ':' or start with '_'.
Optional
providerInformation about the provider. This is useful for auditing, logging, debugging, and other internal uses. It is not considered private information. Hence, it may not contain personally identifiable information.
Optional
product?: stringAn optional name of the source of the deployments data.
A list of deployments to submit to Jira.
Each deployment may be associated with one or more Jira issue keys, and will be associated with any properties included in this request.