My previous test was done according to jenkins-php.org configuration on the Jenkins side, and install-and-use config (according to Trac Wiki's mod_wsgi instructions) on the Trac side.
I've a solution (upgrade Trac to 0.12.3) that works. Since I was due for Debian distribution upgrade, I did that after my previous post here. It didn't affect Jenkins (using Jenkins' deb repo, not Debian's) but it did affect Trac and the surrounding system. After the normal upgrade routine through aptitude and trac-admin, authenticated xml-rpc calls from Jenkins to Trac works as you (Brent) described. For Magnus: The "Jenkins URL" value that Brent mentioned becomes relevant after you get this working. The comment output might look like: Referenced in build [null/job/Jenkins%20Demo/29/ Jenkins Demo #29] > That null should be filled by Jenkins URL from Jenkins > Manage Jenkins > Configure System, but on my system that value is filled but still coming out null. :) On Thursday, 29 August 2013 19:45:34 UTC-4, Brent Atkinson wrote: > > Jenkins 1.529 >> Trac Plugin 1.13 >> Trac Publisher 1.3 >> >> Trac 0.11.7-4 >> trac-xmlrpc 1.0.6+svn6598-1 > > > Could you also provide the configuration settings you are using? > > 127.0.0.1 - - [29/Aug/2013:18:10:49 -0400] "POST /trac HTTP/1.1" 500 829 >> "-" "Apache XML RPC 3.1.3 (Jakarta Commons httpclient Transport)" >> > > >> [Thu Aug 29 18:10:49 2013] [error] [client 127.0.0.1] mod_wsgi >> (pid=11632): Exception occurred processing WSGI script >> '/home/user/webproject.trac/cgi-bin/trac.wsgi'. >> [Thu Aug 29 18:10:49 2013] [error] [client 127.0.0.1] RuntimeError: >> response has not been started > > > These are telling you that Trac is encountering an error and it is > returning an HTTP 500 error. This could be for a number of reasons, but > Trac does a terrible job of reporting the reason, and instead just returns > "RuntimeError: response has not been started". My advice would be to try > and use the xmlrpc interface with the use you setup for jenkins. If you can > verify it works manually, then it confirms this is a defect in the plugin. > Unfortunately, I can't use your setup so you will have to help to identify > any issue. > > I'd also check the file permissions and xmlrpc setup and make sure that > all looks good. Just searching on google for "RuntimeError: response has > not been started" shows how many people get this error from Trac for a > number of reasons. > > Brent > > > On Thu, Aug 29, 2013 at 6:32 PM, Daniel Ritchie > <whatrev...@gmail.com<javascript:> > > wrote: > >> I'll join Magnus on this being an unresolved issue for us. In my >> scenario, we're using Debian 6.0.7 apt versions of Jenkins and Trac. >> >> Jenkins 1.529 >> Trac Plugin 1.13 >> Trac Publisher 1.3 >> >> Trac 0.11.7-4 >> trac-xmlrpc 1.0.6+svn6598-1 >> >> Basically, take today's Debian Squeeze (previous stable), install both >> locally, and let Jenkins install and upgrade its own plugins. That's what I >> did this week. >> >> The result is that Trac Publisher behaves exactly as Magnus has >> described. Console output of a build claims success on commenting to the >> ticket, but it's not true. This is what I see in Apache access.log: >> >> 127.0.0.1 - - [29/Aug/2013:18:10:49 -0400] "POST /trac HTTP/1.1" 500 829 >>> "-" "Apache XML RPC 3.1.3 (Jakarta Commons httpclient Transport)" >>> >> >> And this is error.log: >> >> [Thu Aug 29 18:10:49 2013] [error] [client 127.0.0.1] mod_wsgi >>> (pid=11632): Exception occurred processing WSGI script >>> '/home/user/webproject.trac/cgi-bin/trac.wsgi'. >>> [Thu Aug 29 18:10:49 2013] [error] [client 127.0.0.1] RuntimeError: >>> response has not been started >>> >> >> Having configured Jenkins to use a brand-new Trac account, I can also see >> that this exception prevented Jenkins from having logged an access on Trac, >> because the user's "Last Login" is still null. Also note that this occurs >> with or without a user/password pair. >> >> >> >> On Monday, 15 April 2013 16:07:45 UTC-4, Brent Atkinson wrote: >> >>> 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<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<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-use...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- 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.
