Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-46995

Changes in dependency information strangeness

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: jira-plugin
    • Labels:
      None
    • Environment:
      Jira 2.78, Win7, SVN (client set as v1.8 in settings)
    • Similar Issues:

      Description

      I have just started using a plugin to update JIRA with build status comments. Sometimes it will update a long list of tickets when there should only be one involved.

      I think it gets the list from the changes info in Jenkins, it goes wrong when a "changes in dependency" message is displayed which seems to have the wrong last versions.

      eg

      Job A (builds triggered on SCM change)

      • #821 - dependency on Job A #810 to #820
      • #822 - no changes in dependency: build failed
      • #823 - no changes in dependency
      • . . .
      • #826 - no changes in dependency
      • #827 - dependency on Job A #820 to #826
      • #828 - dependency on Job A #826 to #827 
      • #829 - no changes in dependency
      • #830 - dependency on Job A #827 to #829  
      • #831 - no changes in dependency
      • . . .
      • #837 - no changes in dependency
      • #838 - dependency on Job A #829 to #837

      There is not a paste error here, Job A is reported to depend on Job A.

      It seems to be occasionally deciding it needs to pull some token up to the current build, but I cannot work it out.

      I set the component as jira-plugin (from the very extensive list), but I think the problem is in jenkins/svn.

      This issue is similar, but not the same as JENKINS-16034

        Attachments

          Activity

          Hide
          warden Radek Antoniuk added a comment -

          What is your upstream/downstream job configuration? This seems rather a Jenkins dependency error rather than a JIRA issue. Can you describe scenario in which it can be reproduced?
          The component here should be either core or subversion-plugin.
          By the way, JIRA version is incorrect. Please state correctly JIRA, Jenkins, jira-plugin, subversion-plugin versions.

          Show
          warden Radek Antoniuk added a comment - What is your upstream/downstream job configuration? This seems rather a Jenkins dependency error rather than a JIRA issue. Can you describe scenario in which it can be reproduced? The component here should be either core or subversion-plugin. By the way, JIRA version is incorrect. Please state correctly JIRA, Jenkins, jira-plugin, subversion-plugin versions.
          Hide
          chrisaaaaa Chris Amis added a comment - - edited

          I have a simplified scenario, I just clicked build on the job.

          In the trace I have these items.

          Build step: Injecting JIRA variables into the environment, no applicable tickets, I just manually built it so that makes sense.

          11:55:45 [JIRA] Setting JIRA_ISSUES to .

          Post Build step: Update JIRA tickets:

          12:37:44 BUILD-769 issue doesn't exist in JIRA*
          12:37:44* BUILD-784 issue doesn't exist in JIRA*
          12:37:44* WIFIIOT-1750 issue doesn't exist in JIRA*
          12:37:44* WIFIIOT-1758 issue doesn't exist in JIRA*
          12:37:44* WIFIIOT-1686 issue doesn't exist in JIRA*
          12:37:44* R15262-2017 issue doesn't exist in JIRA*
          12:37:44* W3411-99987 issue doesn't exist in JIRA*
          12:37:51* W3400-333 issue doesn't exist in JIRA*
          12:37:51* W3400-7777777 issue doesn't exist in JIRA*
          12:37:56* [JIRA] Updating issue WSGSWPROC-4*
          12:37:57* [JIRA] Updating issue W3400-1*
          12:37:58* [JIRA] Updating issue WSGSWPROC-1*
          12:37:59* [JIRA] Updating issue W3400-22*
          12:38:00* [JIRA] Updating issue WSGSWPROC-2*
          12:38:01* [JIRA] Updating issue W3400-65*
          12:38:02* [JIRA] Updating issue W3400-33

          These tickets are gleaned from going back a dozen or more revisions.

          But how does it go from saying there is nothing as a build step, to a long list at post build?

           

          JIRA v7.3.6

          Jenkins v2.73.1 (had problems with 2.78/79 so went to LTS stream)

          JIRA Plugin 2.4.2

           

          Show
          chrisaaaaa Chris Amis added a comment - - edited I have a simplified scenario, I just clicked build on the job. In the trace I have these items. Build step: Injecting JIRA variables into the environment, no applicable tickets, I just manually built it so that makes sense. 11:55:45 [JIRA] Setting JIRA_ISSUES to . Post Build step: Update JIRA tickets: 12:37:44 BUILD-769 issue doesn't exist in JIRA* 12:37:44* BUILD-784 issue doesn't exist in JIRA* 12:37:44* WIFIIOT-1750 issue doesn't exist in JIRA* 12:37:44* WIFIIOT-1758 issue doesn't exist in JIRA* 12:37:44* WIFIIOT-1686 issue doesn't exist in JIRA* 12:37:44* R15262-2017 issue doesn't exist in JIRA* 12:37:44* W3411-99987 issue doesn't exist in JIRA* 12:37:51* W3400-333 issue doesn't exist in JIRA* 12:37:51* W3400-7777777 issue doesn't exist in JIRA* 12:37:56* [JIRA] Updating issue WSGSWPROC-4* 12:37:57* [JIRA] Updating issue W3400-1* 12:37:58* [JIRA] Updating issue WSGSWPROC-1* 12:37:59* [JIRA] Updating issue W3400-22* 12:38:00* [JIRA] Updating issue WSGSWPROC-2* 12:38:01* [JIRA] Updating issue W3400-65* 12:38:02* [JIRA] Updating issue W3400-33 These tickets are gleaned from going back a dozen or more revisions. But how does it go from saying there is nothing as a build step, to a long list at post build?   JIRA v7.3.6 Jenkins v2.73.1 (had problems with 2.78/79 so went to LTS stream) JIRA Plugin 2.4.2  
          Hide
          chrisaaaaa Chris Amis added a comment -

          The job I triggered manually triggers another job when it completes, this too records back to Jira, in this case I see this in the build step.

          [JIRA] Setting JIRA_ISSUES to WSGSWPROC-4,BUILD-769,BUILD-784,WIFIIOT-1750,WIFIIOT-1758,WIFIIOT-1686,R15262-2017,W3411-99987,W3400-1,WSGSWPROC-1,W3400-22,W3400-333,W3400-7777777,WSGSWPROC-2,W3400-65,W3400-33.
          

           At the post build step the same list was seen

          BUILD-769 issue doesn't exist in JIRA
          BUILD-784 issue doesn't exist in JIRA
          WIFIIOT-1750 issue doesn't exist in JIRA
          WIFIIOT-1758 issue doesn't exist in JIRA
          WIFIIOT-1686 issue doesn't exist in JIRA
          R15262-2017 issue doesn't exist in JIRA
          W3411-99987 issue doesn't exist in JIRA
          W3400-333 issue doesn't exist in JIRA
          W3400-7777777 issue doesn't exist in JIRA
          [JIRA] Updating issue WSGSWPROC-4
          [JIRA] Updating issue W3400-1
          [JIRA] Updating issue WSGSWPROC-1
          [JIRA] Updating issue W3400-22
          [JIRA] Updating issue WSGSWPROC-2
          [JIRA] Updating issue W3400-65
          [JIRA] Updating issue W3400-33
          

          So I am not sure if the plugin is getting confused or being given the wrong information from elsewhere?

          Show
          chrisaaaaa Chris Amis added a comment - The job I triggered manually triggers another job when it completes, this too records back to Jira, in this case I see this in the build step. [JIRA] Setting JIRA_ISSUES to WSGSWPROC-4,BUILD-769,BUILD-784,WIFIIOT-1750,WIFIIOT-1758,WIFIIOT-1686,R15262-2017,W3411-99987,W3400-1,WSGSWPROC-1,W3400-22,W3400-333,W3400-7777777,WSGSWPROC-2,W3400-65,W3400-33.  At the post build step the same list was seen BUILD-769 issue doesn't exist in JIRA BUILD-784 issue doesn't exist in JIRA WIFIIOT-1750 issue doesn't exist in JIRA WIFIIOT-1758 issue doesn't exist in JIRA WIFIIOT-1686 issue doesn't exist in JIRA R15262-2017 issue doesn't exist in JIRA W3411-99987 issue doesn't exist in JIRA W3400-333 issue doesn't exist in JIRA W3400-7777777 issue doesn't exist in JIRA [JIRA] Updating issue WSGSWPROC-4 [JIRA] Updating issue W3400-1 [JIRA] Updating issue WSGSWPROC-1 [JIRA] Updating issue W3400-22 [JIRA] Updating issue WSGSWPROC-2 [JIRA] Updating issue W3400-65 [JIRA] Updating issue W3400-33 So I am not sure if the plugin is getting confused or being given the wrong information from elsewhere?
          Hide
          warden Radek Antoniuk added a comment -

          Do you still see this issue happening? If so, can you update the versions in the issue to the current ones you are using?

          Show
          warden Radek Antoniuk added a comment - Do you still see this issue happening? If so, can you update the versions in the issue to the current ones you are using?

            People

            • Assignee:
              Unassigned
              Reporter:
              chrisaaaaa Chris Amis
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: