On Sat, Apr 13, 2013 at 12:23:00PM -0400, Brent Atkinson wrote: > Magnus, > > The plugin has very minimal setup requirements. Using the xmlrpc > plugin with ticket updating enabled, a user with permissions to call > the xmlrpc methods, and connectivity from the jenkins server to your > trac installation's xmlrpc endpoint.
Yes indeed, that's why I'm so surprised. > Can you describe your trac and xmlrpc plugin versions and your > configuration details? For testing purposes I've set up two virtual machines, tracsrv.local and jenkinssrv.local. # tracsrv.local - trac - 1.0 - XMLRPC plugin built from SVN earlier today (not sure of exact revision) ## trac project - ProjectFoo - http://tracsrv.local/trac/ProjectFoo/ - magnus is an admin user, i.e. TRAC_ADMIN - authenticated users all have XML_RPC # jenkinssrv.local - jenkins - 1.504 - Trac plugin - 1.13 trac website : http://tracsrv.local/trac/ProjectFoo/ - Trac Publisher - 1.3 Trac XMLRPC URL : http://tracsrv.local/trac/ProjectFoo/login/rpc (also tried http://tracsrv.local/trac/ProjectFoo/login/xmlrpc, with no luck) Trac XMLRPC username : magnus (with correct username) # what I do and expect, what I see and don't see 1. I have a single (git) repo where I make a change and provide a commit message containing 'Closes #6' (ticket #6 is currently open). Then I push the change to my repo. 2. The git post-receive hook correctly notifies Trac about the added change, and finally it triggers a Jenkins build using ~~~~ curl http://jenkinssrv.local:8080/git/notifyCommit?url=http%3a%2f%2ftracsrv.local%2fgit%2ffoo.git ~~~~ I do see some of the expected bits here: - In Trac the changeset points to ticket #6, and a comment is added to ticket #6 pointing to the changeset, i.e. the Trac-related part of the git post-receive hook works. - My Jenkins project is triggered and a build is kicked off. I also get a "detail" page for the change that contains a link to Trac issue #6, as well as a "TracGit" link that leads to the Trac view of the changeset, i.e. the Trac plugin for Jenkins works and my config of it seems correct. What I don't see: - Looking at the console output there is no mention of the post-build action related to Trac Publish at all. My other post-build action, archiving, outputs a line and works just fine. - Looking at Trac issue #6 I'm expecting to find a comment with a link back to the Jenkins build, but there is no mention of that. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: [email protected] jabber: [email protected] twitter: magthe http://therning.org/magnus Perl is another example of filling a tiny, short-term need, and then being a real problem in the longer term. -- Alan Kay
pgp75ASyHTdou.pgp
Description: PGP signature
