Magnus, I was able to successfully using:
* Jenkins ver. 1.480.3 w/Trac Publisher Plugin 1.3 * Trac 1.0.1 w/XmlRpcPlugin 1.1.2-r12546 I configured the sample build by: * Checking the 'Add link to Trac issues' checkbox * URL = http://example.com/trac/login/rpc * User = user with permissions * Password = user's password I simply made a commit using: svn commit -m "#1: testing publisher plugin for trac 1.0.1" And when built, a message in the console output shows: Updating 1 Trac issue(s): server=http://example.com/trac/login/rpc , user=xmlrpcuser Updating successful issue 1 with sample #4 Checking the ticket referenced, it was successfully updated (once I set jenkin's 'Jenkins URL') So, the good news is, it should work. The bad news is, there isn't a whole lot that can go wrong here. If you don't see the message in the console output, it seems the plugin isn't running. If you can give more details about what you have setup, it would help to venture a better guess. Brent On Mon, Apr 15, 2013 at 1:17 AM, Magnus Therning <mag...@therning.org>wrote: > 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: mag...@therning.org jabber: mag...@therning.org > 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 > -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
