Comment 3 for bug 1603679
Revision history for this message
| Colin Watson (cjwatson) wrote Re: Remote tracker for gitlab.com | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Driving the GitLab issues API itself will be pretty easy based on the GitHub implementation; there are differences in details, but if anything it's mostly slightly simpler.
However, one tricky bit here will be that GitLab's issues API absolutely requires authentication. Now, we do authenticate to GitHub as well, but there's only one instance there so we can afford for that to be configured manually. Not so much with the many GitLab instances out there.
I think what we'll probably need to do as part of this is:
* extend the BugTracker table with somewhere to store credentials
* add (probably) an OAuth flow to the relevant GitLab instance as part of setting up a bug tracker, so we'd end up with the external bug tracker instance set up to use a particular person's credentials; we might set up some of the more important instances using a dedicated role account
* add some way to reauthorise an external bug tracker if the previous credentials expire or break or whatever