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

need get svn info from upstream job to downstream job

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: subversion-plugin
    • Labels:
      None
    • Environment:
      linux, windows
    • Similar Issues:

      Description

      if the upstream job is triggered by svn, the downstream job which is triggered by this upstream job will not get any svn info from the upstream job. So if the downstream job's build failed, we could't know who should be blamed. Although there is a plugin called BlameUpstreamJob can solve this problem, it only can send sample mail which can't be configured to who trigger the upstream job and can't be
      used in chain of upstream-downstream jobs. I Insist on we need a SCM plugin that can collect svn info from upstram job to downstream job, then we could use email-ext plugin and other plugin to help us blame who trigger the svn to make build failed in downstream job.

        Attachments

          Activity

          Hide
          mdp mdp added a comment -

          Is not hudson.upstreamCulprits described under http://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties what is needed and good enough?

          Show
          mdp mdp added a comment - Is not hudson.upstreamCulprits described under http://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties what is needed and good enough?
          Hide
          tangjinou tangjinou added a comment -

          I have tried to use the command -Dhudson.upstreamCulprits=true, but it did't work for this issue.Now you could use the BlameSubversion plugin to solve this problem, for more detail, you could visit this wiki:
          http://wiki.jenkins-ci.org/display/JENKINS/BlameSubversion

          Show
          tangjinou tangjinou added a comment - I have tried to use the command -Dhudson.upstreamCulprits=true, but it did't work for this issue.Now you could use the BlameSubversion plugin to solve this problem, for more detail, you could visit this wiki: http://wiki.jenkins-ci.org/display/JENKINS/BlameSubversion
          Hide
          asirvinskas Arturas Sirvinskas added a comment -

          Is there any chance to get it work with mercurial?
          BlameSubversion plugin works just fine with SVN.

          Show
          asirvinskas Arturas Sirvinskas added a comment - Is there any chance to get it work with mercurial? BlameSubversion plugin works just fine with SVN.

            People

            • Assignee:
              Unassigned
              Reporter:
              tangjinou tangjinou
            • Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: