On Sun, Apr 14, 2013 at 11:28:34AM -0400, Brent Atkinson wrote: > Magnus, > > Yes you are right about the logging. You should definitely be seeing an > attempt to update the tickets in the trailing lines of the build output. As > for the multi-project comment, the plugin was actually written based on the > xmlrpc interface of trac 0.11. However, you should at least see failures in > http logs or on the Jenkins side. What you are seeing sounds strange.
Yes, that is what I was thinking too. I had a quick look at the code of the plugin, while it's not chatty it's definitely not completely quiet either. I don't see anything related to Trac Publisher in - webserver logs on the Trac side - build logs of the Jenkins build jobs - stdout on the Jenkins server (I still haven't turned Jenkins into a service so I see its output on the terminal where I started it) Is there some other place I should be looking for errors and warnings that could explain the behaviour? /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: [email protected] jabber: [email protected] twitter: magthe http://therning.org/magnus Most software today is very much like an Egyptian pyramid with millions of bricks piled on top of each other, with no structural integrity, but just done by brute force and thousands of slaves. -- Alan Kay
pgpmISyZ_91pm.pgp
Description: PGP signature
