The Jenkins logging isn't set up for a use case like that; use the Subversion server's access log (and filter by Jenkins master and slave IP addresses) instead.
If you must use Jenkins, try setting up a log recorder for the following loggers: - hudson.scm.SubversionSCM - hudson.scm.listtagsparameter.ListSubversionTagsParameterDefinition - hudson.scm.CredentialsSVNAuthenticationProviderImpl (Which are also the loggers you'd find through autocompletion of 'svn' and 'subversion' since Jenkins 1.573.) SCMListener barely receives anything, as you can see in the Javadoc: http://javadoc.jenkins-ci.org/hudson/model/listeners/SCMListener.html On 10.11.2014, at 14:53, Jennifer Hofmeister <[email protected]> wrote: > Hello, > > I want to set up a logger to examine all attempts Jenkins makes to connect to > a Subversion server, successful or not. > > The jenkins and hudson APIs are huge, but I figured > hudson.model.listeners.SCMListener might be a good module to listen to. But > the log stays empty, although I set it to log level “all”. > > What did I miss? Or does anyone know a better listener module? > > Cheers > > Jennifer > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. -- 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]. For more options, visit https://groups.google.com/d/optout.
