On 4/14/13, Magnus Therning <[email protected]> wrote:
> On Sun, Apr 14, 2013 at 08:26:57AM -0400, Brent Atkinson wrote:
>> 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.
>
> Wouldn't the plugin report the error to the build log (or somewhere
> else)?
> If it tries to use the URL I provided I ought to see something in the
> webserver's access log on tracsrv.local.  However, I really see
> *nothing*.  So it looks like the plugin never runs at all.
>
>> 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.

XmlRpcPlugin supports Trac>=1.x . However there are some subtle
differences in the API due to the fact that Trac core has introduced
new ways of doing things .

BTW , if you need any help with this I'm co-maintainer of Trac
XmlRpcPlugin , so I could help you develop some patches and propose
them to upstream trachacks repository , in case you find something .
Now I'm also starting to add support for RPC interface for Apache™
Bloodhoound>0.5 [2]_ (read comments below)

>> Feel free to take a peek at
>> the source yourself in the mean time. It is a quick read.
>
> I'm not sure what you mean by multi-project, but AFAIK nothing that
> would qualify as multi-project in my mind has entered Trac since 0.12.

jftr .

<ot>
Not in Trac core but among Trac plugins there are two concurrent options :

  1. trachacks:SimpleMultiProjectPlugin
  2. Apache™ Bloodhound [3]_

The former is limited in the sense that *projects* implementation is a
lightweight addition on top of single-environment setups . OTOH the
later adds full support for *product environments* [1]_ thus providing
everything you see in Trac single-project environments .
</ot>

> When I mentioned 'project' in the earlier post I think I was referring
> to a 'Jenkins project'.
>

.. [1] https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0003#product-envs

.. [2] https://bitbucket.org/olemis/bloodhound-rpc

.. [3] http://issues.apache.org/bloodhound

-- 
Regards,

Olemis.

Apache™ Bloodhound contributor
http://issues.apache.org/bloodhound

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article:

-- 
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to