ExportXMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor
    • None
    • Environment:
      Jenkins: 2.555.3
      Atlassian Jira Software Cloud Plugin: 2.0.15
      Jira Cloud
      Automatic deployment reporting enabled
      Pipeline stage regex:
      ^deploy to (?<envName>.*)$

      We are using the Atlassian Jira Software Cloud Jenkins plugin with automatic deployment reporting enabled.

      The deployment stage is correctly recognized, and Jira creates a deployment record associated with the issue. However, after the Jenkins pipeline completes successfully, the deployment remains permanently in the "In Progress" state in Jira.

      Expected Behavior

      When the deployment stage completes successfully, Jira should update the deployment status from In Progress to Successful.

      Actual Behavior

      Jira receives the initial deployment event and displays the deployment as In Progress, but never updates it to Successful, even though Jenkins reports that the final deployment event was accepted.

      Jenkins Log Evidence

      The Jenkins logs show:

      1. The deployment stage is detected:

       
       
       deployment node was determined, envName=stg
        # An in_progress deployment event is sent and accepted:

       
       
       {{Sending in-progress deployment event

      SUCCESS_DEPLOYMENT_ACCEPTED
      Successfully sent deployment information to Jira}}
        # After the stage completes, a successful deployment event is also sent:

       
       
       {{Sending final deployment event
      status":"successful"}}
        # Jira again responds:

       
       
       {{SUCCESS_DEPLOYMENT_ACCEPTED
      Successfully sent deployment information to Jira}}
        # The Jenkins pipeline ends normally:

       
       
       Finished: SUCCESS
       
      Despite this, Jira continues to display the deployment as In Progress.

      Additional Observation

      Comparing the two deployment payloads, the only notable anomaly we found is that both events appear to use the same:
       
       
       {{deploymentSequenceNumber = 41
      updateSequenceNumber = 1783713953}}
       
      while only the following fields change:

      • state
        • in_progress
        • successful
      • lastUpdated

      We are unsure whether this is expected behavior or whether the final event should contain a newer updateSequenceNumber.

      Question

      Is this expected plugin behavior?

      Should the plugin generate a new updateSequenceNumber when sending the final deployment event, or is there another reason Jira would accept both requests while leaving the deployment in the In Progress state?

            Assignee:
            shan shan
            Reporter:
            Sam
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: