Consider a job (downstream job) that watches several other jobs (upstream jobs) and is triggered when anyone of them succeeds. Then the downstream job goes into quiet period. During that period upstream jobs finish up multiple times and later Jenkins shows all triggered upstream jobs inside downstream job build info.

      Now display-upstream-changes-plugin doesn't show changes from multiple upstream projects - only from the first one.

      My current workaround for this is to construct artifacts with redmine issue numbers and scm hashes with help of downstream job rather than seeing that info on it's changes page extended with this plugin.

      I've attached screenshot with example.

          [JENKINS-27048] Multiple upstream projects

          Maxim Nikolaev created issue -
          Rob Petti made changes -
          Assignee Original: Rob Petti [ rpetti ]

          Code changed in jenkins
          User: Rob Petti
          Path:
          src/main/java/jenkins/plugins/displayupstreamchanges/DisplayUpstreamChangesSummaryAction.java
          http://jenkins-ci.org/commit/display-upstream-changes-plugin/fd7f9994016539d62e1105972fba42adecb19a1c
          Log:
          JENKINS-27048 possible fix for issue

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Rob Petti Path: src/main/java/jenkins/plugins/displayupstreamchanges/DisplayUpstreamChangesSummaryAction.java http://jenkins-ci.org/commit/display-upstream-changes-plugin/fd7f9994016539d62e1105972fba42adecb19a1c Log: JENKINS-27048 possible fix for issue

          Thank you, Rob!

          I'm happy with your patch. Now every commit's message is visible on a single status page.

          I'll be using your snapshot until plugin version updates.

          Maxim Nikolaev added a comment - Thank you, Rob! I'm happy with your patch. Now every commit's message is visible on a single status page. I'll be using your snapshot until plugin version updates.
          Maxim Nikolaev made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

          omar khabbas added a comment -

          i have the same issue, why this old fix not applied or updated to plugin ?

          omar khabbas added a comment - i have the same issue, why this old fix not applied or updated to plugin ?
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 161240 ] New: JNJira + In-Review [ 208452 ]

          Philippos added a comment - - edited

          I can confirm this issue still exists on Jenkins 2.278 with Display Upstream Changes 0.3.2

          Upstream changes shows only the last job which triggers the downstream job.

          Philippos added a comment - - edited I can confirm this issue still exists on Jenkins 2.278 with Display Upstream Changes 0.3.2 Upstream changes shows only the last job which triggers the downstream job.
          Philippos made changes -
          Resolution Original: Fixed [ 1 ]
          Status Original: Closed [ 6 ] New: Reopened [ 4 ]

            Unassigned Unassigned
            simno Maxim Nikolaev
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: