Magnus,

If I remember correctly, the pattern is similar if not the same as Trac's
issue pattern. It is odd you don't see anything at all in the build log,
but since you mentioned you are using trac 1.0 and a project, the xmlrpc
interface may not be compatible. It was built on older revs of trac that
didnt support multiple projects.

There is not a lot of information to go on here, but I have been meaning to
try the plugin in a trac 1.0 multi-project setup since it may break
assumptions this was built on. Feel free to take a peek at the source
yourself in the mean time. It is a quick read.

Brent
On Apr 14, 2013 2:30 AM, "Magnus Therning" <mag...@therning.org> wrote:

> On Sat, Apr 13, 2013 at 07:54:48PM +0200, Magnus Therning wrote:
> [...]
> > - 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)
>
> Just for fun I changed the URL to the wrong one, one that doesn't
> require authentication.  I still see *nothing* in the build log on the
> Jenkins side.
>
> Something that hit me yesterday is that I don't *know* what Trac
> Publisher is looking for in the commit messages.  I just assumed it
> would work with the same strings as the Trac CommitTicketUpdater
> plugin does.  Is that assumption correct?
>
> /M
>
> --
> Magnus Therning                      OpenPGP: 0xAB4DFBA4
> email: mag...@therning.org   jabber: mag...@therning.org
> twitter: magthe               http://therning.org/magnus
>
> I invented the term Object-Oriented, and I can tell you I did not have
> C++ in mind.
>      -- 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.


Reply via email to