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

showDependencies for ${CHANGES} doesn't seem to work

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      I'm using the email-ext plugin and it works great except for this problem with "showDependencies".

      This is how I use it (I only use global configs for all jobs in email-ext, just triggers are set per job):
      ${CHANGES, showPaths=true, showDependencies=true}

      I have a 'build' project A that triggers 'unit test' project B, C and D. B, C and D are shown as "Downstream Projects" on project A's "Status" page.

      B and C are started by standard "Build other projects" post-build action of A.
      D is started by "Build other projects (extended)" post-build action of A if Build result is "Equal or over SUCCESS" and with "Trigger only if downstream project has SCM changes" - that is available due to https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin, version 2.21.

      When project B fails due to a change in project A's SCM, in the email I don't see the commits from project A that resulted in this failure, although "showDependencies" is true.

      Did I misunderstand what "showDependencies" is meant for or misused it? If that's not its purpose, then please consider this a feature req. to add the ability to have the changes from A above in email.

      Thanks.

      BTW: from token docs, it seems to me that you can't use "showDependencies" with ${CHANGES_SINCE_LAST_SUCCESS}, just with ${CHANGES}. Is that true? Cause that would be exactly what I want.

        Attachments

          Activity

          Hide
          dirk_hain Dirk Hain added a comment -

          Ok, I was able to resolve the issue by creating a correct chain of fingerprinting across my builds. The piece that was missing was that the build where I was not able to see dependent changes did not have a copy of the artifacts in the workspace. Although that particular build does not require the artifacts Jenkins needs them in the workspace to establish the connection that the build is dependent on a previous build that created the artifact. Since Jenkins does not support fingerprinting outside the workspace directory it is easiest just to use the "Copy artifacts from another build" option and tick the fingerprinting option.

          Show
          dirk_hain Dirk Hain added a comment - Ok, I was able to resolve the issue by creating a correct chain of fingerprinting across my builds. The piece that was missing was that the build where I was not able to see dependent changes did not have a copy of the artifacts in the workspace. Although that particular build does not require the artifacts Jenkins needs them in the workspace to establish the connection that the build is dependent on a previous build that created the artifact. Since Jenkins does not support fingerprinting outside the workspace directory it is easiest just to use the "Copy artifacts from another build" option and tick the fingerprinting option.
          Hide
          slide_o_mix Alex Earl added a comment -

          I think we can close this issue then, anyone opposed?

          Show
          slide_o_mix Alex Earl added a comment - I think we can close this issue then, anyone opposed?
          Hide
          dirk_hain Dirk Hain added a comment -

          Cool with me.

          Show
          dirk_hain Dirk Hain added a comment - Cool with me.
          Hide
          slide_o_mix Alex Earl added a comment -

          Please read Dirk's comments on how he got showDependencies=true to work.

          Show
          slide_o_mix Alex Earl added a comment - Please read Dirk's comments on how he got showDependencies=true to work.
          Hide
          costescuandrei Andrei Costescu added a comment -

          Ok, I'll try it out.

          Show
          costescuandrei Andrei Costescu added a comment - Ok, I'll try it out.

            People

            • Assignee:
              slide_o_mix Alex Earl
              Reporter:
              costescuandrei Andrei Costescu
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: