Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

This plug-in provides utilities for getting svn info from upstream job to downstream job

Plugin Information

View Blame Subversion on the plugin site for more information.

The original purpose of creating BlameSubversion is to solve JENKINS-7509.

Why need BlameSubversion plugin?

*When some body check the code in , the Upstream job1 or upsteam job2 will build the source code.
*When the upstream job1 or upsteam job2 is done, it will invoke the build of downstream job2
*When the downstream job2 build failed, the svn info about who check in upstream job1 or upstream job2 was lost

How did BlameSubversion plugin work?

*1 get the build of upstream job who trigger this build of downstream
*2 get svn info from it
*3 copy svn info to downstream build
*4 provide interfaces for other official hudson plugins.

How did BlameSubversion plugin work?

Easy configure of BlameSubversion plugin
1 choose the checkbox of Blame Subversion in Souce code Management
2 choose the checkbox of Always Collect SVN info from upstream job if you are sure to do it.

Change Log

Version 1.200 (Jan 4, 2012)
  • Release 1.200 to get rid of version order issue with 1.121 (assuming this was a typo releasing 1.21)
Version 1.25 (Nov 1, 2010)
  • Fix a bug
Version 1.24 (Nov 1, 2010)
  • Add new feature for up down stream job build number synchronize
  • Add help.html
  • Fix a bug for notify
Version 1.121 (Oct 15, 2010)


  1. Unknown User (peter_schuetze)

    I am confused now. The last announcement I saw on the RSS ticker was for Version 1.25. Here version is listed as 1.121. So what is the correct version and more importantly, what changed? I was thinking on implementing this plugin, but I am not doing it without knowing what was changed.

    1. Unknown User (mindless)

      Sorry, no one noticed this comment. I just discovered separately that the update-center does not have the latest release (1.121 is considered a larger version number than 1.25). 1.25 will be available in the update-center soon.

  2. Unknown User (tangjinou@gmail.com)

    Hi,the latest version is 1.25.

  3. Unknown User (tangjinou@gmail.com)

    any problems or request, pls send the mail to tangjinou@gmail.com, i will reply as quickly as possible.

  4. Unknown User (asirvinskas)

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

  5. Unknown User (vprasad79)


    Our jenkins jobs are hung while triggering notifications due to below code in BlameSubversionMailAddressResolverImpl class on BlameSubversion plugin

    We have 1000+ jobs and its not fair to search all projects to resolve mail address for each commit user.

    public class BlameSubversionMailAddressResolverImpl extends MailAddressResolver {
        public String findMailAddressFor(User u) {
            for (AbstractProject<?,?> p : u.getProjects()) {
                SCM scm = p.getScm();
                if (scm instanceof BlameSubversionSCM) {
                    BlameSubversionSCM svn = (BlameSubversionSCM) scm;
                    for (BlameSubversionSCM.ModuleLocation loc : svn.getLocations(p.getLastBuild())) {
                        String s = findMailAddressFor(u,loc.remote);
                        if(s!=null) return s;
            // didn't hit any known rules
            return null;

    Can you please simply remove this loop and return username so that email notification plugins will resolve from LDAP or appends @domain?