I am experiencing the same issue. My post-commit hooks were working as expected until recently. Having applied various Jenkins upgrades in between that time, I cannot say with which version post-commits started to fail. Currently we're running Jenkins 1.460, subversion 1.4.2.
I'll create an issue in Jira unless I can find an existing issue. Here are answers to your questions: Do you have the job in Jenkins? > Yes. > What happens when you press the "Build Now" button? > Job builds as expected Is there a certain spot where it's failing? The job itself does not fail. A build simply isn't triggered upon commit -- in the logs a message appears: Apr 22, 2012 8:46:02 AM hudson.scm.SubversionRepositoryStatus doNotifyCommit WARNING: No subversion jobs found What is the post-commit hook for? Normally, with Subversion, [snip] > The post-commit hook is for triggering corresponding builds. It is superior than polling subversion, for reasons stated on the wiki. I'll follow-up with the issue key I'll create. ~kc On Tuesday, April 10, 2012 9:56:47 PM UTC-7, qazwart wrote: > > So, exactly what are you trying to do and exactly what is failing? > > * Do you have the job in Jenkins? > * What happens when you press the "Build Now" button? > * Can Jenkins detect when you do a commit? > * Is there a certain spot where it's failing? > * What is the post-commit hook for? Normally, with Subversion, you can > let Jenkins detect when a commit is done on the project. With CVS, you > sometimes have to setup a post-commit hook to start the Jenkins job > because CVS takes so much time and resources to determine whether or > not a change has occurred. With Subversion, it takes less than a > second and very few resources. > > * What does your post commit script look like? > * What error messages are you getting? Are you able to see an update > with the Subversion job? Is there any build going on? Is the problem > just with updating the Maven repository? > * Have you tried manually doing this on the Jenkins server logged in > as the user who is running Jenkins. > > On Wed, Apr 11, 2012 at 12:07 AM, Bryan Campbell <[email protected]> > wrote: > > I have been trying to setup a basic post-hook commit with Jenkins for > > about 2 weeks now. I can't seem to get past this issue. I find this > issue > > often on forums, blogs, google, and in this user group. Does anyone know > > why this is happening or how to fix it? I would really appreciate some > > help. Thanks! > > > > On 4/10/12 9:50 AM, "Bryan Campbell" <[email protected]> wrote: > > > >> > >>I am trying to setup Jenkins to work with my subversion repository. I > >>have 4 projects setup as maven projects but are configured with > >>subversion. When ran manually they do an svn up on the projects, > >>compile, run tests, and then deploy to a maven snapshot repository. > >>Right now they are polling SCM every 5 mins. I would like to change this > >>to be done through post commit hooks. > >> > >>I have Jenkins 1.458 installed on Windows OS. The subversion post hook > >>commit seems to work just fine. It hits a URL in jenkins with the > >>correct UUID via POST. It posts the change as data. I receive no issues > >>from the post-commit hook. However it doesn't do anything. When I check > >>the Jenkins logs it says: > >>SubversionRepositoryStatus doNotifyCommit, WARNING: No subversion jobs > >>found > >> > >>All of our jobs have subversion configured and work properly when ran > >>manually. I checked the subversion plugin's xml in Jenkins and it has > >>the right SVN credentials. I can't seem to get past this part. > >> > >>Help would be greatly appreciated. > >> > >>Thanks a lot! > >> > > > > -- > David Weintraub > [email protected] > >
