XML-RPC/SOAP/etc. interface

[jon@…]

It would be kinda nice to have an interface for Trac that would allow people to develop things like allowing tickets to be reported from within an application.

[rocky]

Xml-rpc should be fairly easy to accomplish. Preferably we would support both xml-rpc and SOAP/WSDL. Unfortunately, it seems that WSDL for python at this point seems to be rather immature.

[cmontpetit@…]

Is there progress on this issue?

Is there a way to programatically interact with the Trac system using ​REST for example?

[daniel]

I think we should at least have a minimal web-services API for 1.0.

[daniel]

This is part of the 2.0 redesign process as well.

[Steffen Pingel]

I would welcome an rpc inferface very much as it would make it possible to implement an interface to the issue tracker in Eclipse (as a plugin).

[cmlenz]

​WikiRPC looks interesting as a generic XML-RPC based API for Wikis.

[mgood]

This is something I'd like to look into.

[coderanger]

Though still experimental, the XmlRpcPlugin? over at trac-hacks is probably a good starting point for this. WikiRPC is implemented already, and I'm sure the ticket system could be setup for RPC manipulation.

[Markus Tacker <m@…>]

Do not close tickets without a comment.

[athomas]

The ​XmlRpcPlugin implements the WikiRPC API, thanks to mgood, and also exports an API for manipulating the ticket system. You can see the builtin methods ​here.

[mgood]

#3385 has been marked as a duplicate.

[cboos]

Milestone 2.0 deleted

[pascal.seitz@…]

Any progress here? I would be very interested in an API

[cboos]

No, it's still unscheduled, which means the members of TracTeam have currently no interest in implementing it themselves, but they're not opposed either to someone else's contributions on the topic, provided there's a good rationale for it and a good quality patch.

[cboos]

… and I suppose Matt is not really interested in the noise here either ;-)

[Thijs Triemstra <lists@…>]

The XML-RPC plugin now includes a pluggable API for extending protocols, and see for instance ​TracRpcProtocolsPlugin for more protocols.

[dean.poulin@…]

it's amazing to see that as I could use this today, a ticket opened 7 years ago with no implementation is blocking me from simple interraction with Trac via web service. If you want an AWESOME example of the simple implementation of this please see: ​http://wiki.hudson-ci.org/display/HUDSON/Remote+access+API

[lkraav <leho@…>]

i am not sure what @dean.poulin is talking about, as ​th:XmlRpcPlugin works more than fabulously. as a matter of fact, i'm not sure why this ticket is still open. perhaps ​th:XmlRpcPlugin could be brought into tracopt and be done with it or something?

[dean.poulin@…]

@lkraav - I'm just referring to the fact that people like simple APIs to program against, especially in the area of continuous integration/build process/release management. I run an API that gets millions of requests a day and if our API was complicated it wouldn't get used. Our team is specifically looking to trigger ticket resolutions via the build/release process.

I'm just recommending that Trac implement a simple API as Hudson has done (​http://wiki.hudson-ci.org/display/HUDSON/Remote+access+API) which is accessible via basic RESTful URLs to access data and trigger actions in a programmable fashion.

I'm a very satisfied Trac user of 4 years. I was just surprised that in order to access Trac data I have to install a third party plug-in… XmlRpc?.

[uwe.keim@…]

We are providing a small Trac interface within our Test Management tool ​Zeta Test.

If anyone is interested in the source code of the interface, just give me a ​quick note.