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

Upstream committers not always passed to downstream jobs

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: core
    • Labels:
    • Environment:
      jenkins 2.89
      blame-committer-plugin 1.2
    • Similar Issues:

      Description

      I am seeing cases where upstream culprits are not always  passed to downstream jobs

      I have the following configuration

      Job A triggers Job C (fingerprint file .hnd_trail)

      Job B triggers Job C (fingerprint file .hudson_trail)

      Job C triggers Job D (fingerprint files .hnd_trail and .hudson_trail)

      Job D is not getting upstream committer from Job A (filter files .hnd_trail and .hudson_trail)

      I believe I've configured the necessary dependencies with fingerprint files. The missing upstream commiter seems to missing sometime and not others. I can't determine why.

        Attachments

          Activity

          Hide
          em_boehm Eric Boehm added a comment - - edited

          I can see the culprits in the build.xml file but downstream they go missing.

          For example

          Job A #534, userA in build.xml <culprits>userA</culprits>

          Job B #538, userB in build.xml <culprits>userB</culprits>

          Job C #880, only userB in build.xml <culprits>userB</culprits>.

          Job C was triggered by Job A #534 and contains fingerprints from Job A #534 and Job B #538. This seems to be the breakdown. The job was triggered by Job A but shows the culprit from Job B, instead of showing both culprits.

          Job D #761, only userB in build.xml <culprits>userB</culprits> but contains fingerprints from Job A #534 and Job B #538.

          Show
          em_boehm Eric Boehm added a comment - - edited I can see the culprits in the build.xml file but downstream they go missing. For example Job A #534, userA in build.xml <culprits>userA</culprits> Job B #538, userB in build.xml <culprits>userB</culprits> Job C #880, only userB in build.xml <culprits>userB</culprits>. Job C was triggered by Job A #534 and contains fingerprints from Job A #534 and Job B #538. This seems to be the breakdown. The job was triggered by Job A but shows the culprit from Job B, instead of showing both culprits. Job D #761, only userB in build.xml <culprits>userB</culprits> but contains fingerprints from Job A #534 and Job B #538.
          Hide
          em_boehm Eric Boehm added a comment -

          This may have been a configuration error on my part. I relied entirely on Culprits in the Email-ext plugin. I've updated my configuration to add 'Upstream Committers' as well.

          Show
          em_boehm Eric Boehm added a comment - This may have been a configuration error on my part. I relied entirely on Culprits in the Email-ext plugin. I've updated my configuration to add 'Upstream Committers' as well.

            People

            • Assignee:
              Unassigned
              Reporter:
              em_boehm Eric Boehm
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: