So our problem was with the post-commit hook. We've got our hooks running a PHP script so we can easily manage them in a DB, and we had recently switched from using exec calls of wget to PHP's curl. We thought this had been working but it had not.
For anyone reading at home, PHP's curl doing POSTs will silently ignore your requests to change the Content-Type header to text/plain;charset=UTF-8. Instead, it will choose the Content-Type header for you <http://php.net/manual/en/function.curl-setopt.php#refsect1-function.curl-setopt-notes> based on what kind of data you provide to POSTFIELDS, and it appears you cannot override it. On Wednesday, February 25, 2015 at 11:51:31 AM UTC-5, Mark Lewis wrote: > > Daniel, > > I had set logging to ALL globally, and it didn't print anything for > SubversionRepositoryStatus when I triggered the post-commit. Weird. > > Following your instructions, I can see it is getting triggered. Thanks for > helping me rule that out. > > On Wednesday, February 25, 2015 at 4:18:26 AM UTC-5, Daniel Beck wrote: >> >> >> On 25.02.2015, at 00:39, Mark Lewis <[email protected]> wrote: >> >> > The OP set logging to FINE. >> >> For the wrong logger. Quoting: >> >> > I looked at the code for SubversionSCMSource.onNotify and setup a >> logger at level 'FINE' for that class. Nothing interesting. >> >> Make sure to create a log recorder for the logger >> hudson.scm.SubversionRepositoryStatus only, on level FINE or higher. What >> does it report the next time you send the post-commit hook? >> >> -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/71186570-969d-43af-8186-44802a35705a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
