The following plugin provides functionality available through Pipeline-compatible steps. Read more about how to integrate steps into your Pipeline in the Steps section of the Pipeline Syntax page.

For a list of other such plugins, see the Pipeline Steps Reference page.

Atlassian Jira Software Cloud

View this plugin on the Plugins site

checkGatingStatus: Atlassian Jira Service Desk Software Cloud Jenkins Integration (Deployment Gating)

  • environmentId : String
  • site : String (optional)

jiraSendBuildInfo: Atlassian Jira Software Cloud Jenkins Integration (Build)

Once you install the Jenkins plugin and set up the configuration page, you need to add a ‘build step’ in your pipeline. This is what tells the Jenkins pipeline, when running, to send data to Jira or not. You can use the optional 'branch' parameter to override the branch name we use to determine the issue keys associated with the current build.
You generate a Pipeline script, then use this in your Jenkinsfile.
Please select the Jira Software Cloud site name you would like to create the pipeline script for. You can only select 1 site at this time. If you want to send information to multiple sites, please create multiple Pipeline Scripts.
  • branch : String (optional)
  • site : String (optional)

jiraSendDeploymentInfo: Atlassian Jira Software Cloud Jenkins Integration (Deployment)

Once you install the Jenkins plugin and set up the configuration page, you need to add a ‘deployment step’ in your pipeline. This is what tells the Jenkins pipeline, when running, to send data to Jira or not.
You generate a Pipeline script, then use this in your Jenkinsfile.
Please select the Jira Software Cloud site name you would like to create the pipeline script for. You can only select 1 site at this time. If you want to send information to multiple sites, please create multiple Pipeline Scripts. You also need to specify the environment ID, name and type. Valid environment types are 'unmapped', 'development', 'testing', 'staging' and 'production'.
State, Service Ids and IssueKeys are optional parameters. Use state to explicitly describe your deployment state or it will determine from the Jenkins job for you. Valid state values: 'unknown', 'pending', 'in_progress', 'cancelled', 'failed', 'rolled_back', 'successful' Service Ids uses to automatically create a change management request for your deployment Please see https://developer.atlassian.com/cloud/jira/software/rest/#api-group-Deployments for more information.
  • environmentId : String (optional)
  • environmentName : String (optional)
  • environmentType : String (optional)
  • enableGating : boolean (optional)
  • issueKeys : Array / List of String (optional)
    • serviceIds : Array / List of String (optional)
      • site : String (optional)
      • state : String (optional)

      step([$class: 'FreeStylePostBuildStep']): Send build information to Jira

      Once you install the Jenkins plugin and set up the configuration page, you need to add a ‘build step’ in your pipeline. This is what tells the Jenkins pipeline, when running, to send data to Jira or not. You can use the optional 'branch' parameter to override the branch name we use to determine the issue keys associated with the current build.
      You generate a Pipeline script, then use this in your Jenkinsfile.
      Please select the Jira Software Cloud site name you would like to create the pipeline script for. You can only select 1 site at this time. If you want to send information to multiple sites, please create multiple Pipeline Scripts.
      • branch : String (optional)
      • site : String (optional)

      Was this page helpful?

      Please submit your feedback about this page through this quick form.

      Alternatively, if you don't wish to complete the quick form, you can simply indicate if you found this page helpful?

          


      See existing feedback here.