Adding support for the new Sourceforge trackers (Allura)

[Olivier Berger]

Hi.

Some time ago, SourceForge migrated some (or all of its ?) projects to
Allura, whose trackers have changed.

I wonder whether anyone has noticed and/or is working on that...

In any case, I've started some code to try and support it (hopefully not
reinventing another wheel).

You'll find my intial code in the 'allura' branch.

FYI, the trackers have a nice API, easily parseable with json.

However, I'm wondering how to better integrate this in the bts-link
architecture.

The SF Allura trackers are backward compatible : the old URL redirect to
the new ones.

For instance, the URL of
https://sourceforge.net/tracker/?func=detail&aid=3614186&group_id=21935&atid=373747
(a forwarded bug of #710513) is redirected to
http://sourceforge.net/p/docbook/bugs/1300/ (whose JSON variant is at
http://sourceforge.net/rest/p/docbook/bugs/1300/

In my current hack, it's only until we can't match a traditional
Sourceforge status table in the beautiful soup, that I'm trying to check
the redirects happening in the wget (hence the changes on the way to
invoke the wget command), to try the new allura variant.

Instead, I'm thinking of triggering an exception, that would make
bts-link retry with another Remote BTS class...

I'm just lost in the way the instances are constructed, to try and do
that.

Sandro (or anyone else), could you suggest a way to do that properly ?

I'll try and debug to understand more how that is all running.

Thanks in advance.

Best regards,
-- 
Olivier BERGER 
http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingenieur Recherche - Dept INF
Institut Mines-Telecom, Telecom SudParis, Evry (France)