On Fri, May 10, 2013 at 9:20 AM, Mark Phippard <markphip_at_gmail.com> wrote:
> On Fri, May 10, 2013 at 9:07 AM, C. Michael Pilato <cmpilato_at_collab.net> wrote:
>> On 05/09/2013 07:04 PM, Daniel Shahaf wrote:
>>> Can we get a periodic data dump of subversion.tigris.org/issues/ onto
>>> ASF hardware?
>>>
>>> Not because we need to migrate from tigris, but because we need to have
>>> our own backup of our data. (Yes, there is the issues@ history, but,
>>> besides it is not designed for machine parsing, and excludes attachments.)
>>>
>>> I haven't found a way to export the data via the UI. I'm not sure
>>> whether there is no way, or whether my tigris account lacks the "may
>>> export project config and history" bit.
>>
>> As far as I know, there is no export option available via the UI.
>>
>> Moving our tracking off of Tigris and onto ASF hardware has been a
>> longstanding (albeit non-blocking) TODO item since we first began courting
>> the ASF. I think that if we can all agree on a viable ASF-hosted
>> alternative tracker (Bloodhound, bugzilla, or whatever), we should act soon
>> to complete this migration and put this issue (no pun intended) to rest.
>
> Getting the data is someone that anyone can do fairly easily. I think
> it can even be done anonymously. We created an Eclipse plugin years
> ago that created a Eclipse UI for working with the issue tracker and
> it uses these mechanisms.
>
> I will dig into the code and send an example later today. I know the
> format is XML and I am pretty sure there is a button in the UI to do
> this as well. But if not, it is just sending the right GET request.
OK, here is an easy example. This gets the task data for Issue 4365.
http://subversion.tigris.org/issues/xml.cgi?include_attachments=false&id=4365
You will see the XML contains the information about the attachments,
so it would be easy to go get them.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
Received on 2013-05-10 15:40:56 CEST