Hi, What I've noticed after studying BlameSubversion code is that this plugin do too much. In my case I used shared workspace for several jobs so I just wanted to copy changes and to be able to see them. Though I created my own plugin with some custom features specific for the project by forking BlameSubversion plugin and removing 80% of it's code (e.g. responsible for handling subversion notify).
Best regards R. On Thursday, December 20, 2012 9:06:04 AM UTC+1, Robert wrote: > > Hi Guys, > > I'm trying to configure a building environment in my project. We use for > that Jenkins server. > The problem is that I'm not able to configure post-commit-hook and > BlameSubversion plugin together. > > We have a very specific configuration here and have multiple jobs that use > the same workspace: > 1. svn update > 2. build module A > 3. build module B > ... > etc. > > We just update/checkout our source once at the beginning of the flow and > then update job trigger building module A and that one one success module > B, etc, etc. > Because module A and B doesn't know anything about code changes we need to > pass them from previous job (svn update). > We use BlameSubversion plugin for this. > > But one we turn on the mentioned above plugin our post-commit-hook stop > working. I belive the similar defect was published here: > https://issues.jenkins-ci.org/browse/JENKINS-9529 > > That's the logs with turn off BlameSubversion plugin > > Dec 19, 2012 2:40:33 PM hudson.scm.SubversionRepositoryStatus > doNotifyCommit > INFO: actual UUID: 285bf2e5-4b10-4245-a318-e4c178b63224 > Dec 19, 2012 2:40:33 PM hudson.scm.SubversionRepositoryStatus > doNotifyCommit > INFO: expected UUID: 285bf2e5-4b10-4245-a318-e4c178b63224 > Dec 19, 2012 2:40:33 PM hudson.scm.SubversionRepositoryStatus > doNotifyCommit > INFO: uuidFound: true > Dec 19, 2012 2:40:33 PM hudson.scm.SubversionRepositoryStatus > doNotifyCommit > INFO: Remaining: > Dec 19, 2012 2:40:33 PM hudson.scm.SubversionRepositoryStatus > doNotifyCommit > INFO: RemainingSlash: / > Dec 19, 2012 2:40:33 PM hudson.scm.SubversionRepositoryStatus > doNotifyCommit > INFO: Affected Path: /aa > Dec 19, 2012 2:40:33 PM hudson.scm.SubversionRepositoryStatus > doNotifyCommit > INFO: ProjectMatches: true > Dec 19, 2012 2:40:34 PM hudson.triggers.SCMTrigger$Runner run > INFO: SCM changes detected in hook-test. Triggering #16 > Dec 19, 2012 2:40:43 PM hudson.model.Run execute > INFO: hook-test #16 main build action completed: SUCCESS > > And after turn it on: > > Dec 19, 2012 2:56:02 PM hudson.scm.BlameSubversionRepositoryStatus > doNotifyCommit > INFO: -- scm found > Dec 19, 2012 2:56:02 PM hudson.scm.BlameSubversionRepositoryStatus > doNotifyCommit > *INFO: -- trigger not found (this is my debug log)* > Dec 19, 2012 2:56:02 PM hudson.scm.BlameSubversionRepositoryStatus > doNotifyCommit > *WARNING: No subversion jobs using SCM polling* > > I've checked 1.25 blamesubversion and 1.39/1.43 subversion plugins. > Could you please help? Perhaps I forget about kind of configuration step > or do you know any workaround? > Or maybe you know another plugin that is able to copy commit changes. > > Best regards > Robert > >
