Re: [egit-dev] [mylyn-reviews-dev] what does gerrit connector use to lis

[Shawn Pearce <spearce@xxxxxxxxxxx>]

On Fri, Apr 6, 2012 at 10:31, Steffen Pingel <steffen.pingel@xxxxxxxxxxx> wrote:
> thanks for driving these changes! It will be very beneficial for Mylyn
> and other tools to have this. What would be the best (easiest) way for
> us to consume the changes? Are there nightly builds that we could
> deploy on our test server?

Not yet. The work hasn't been submitted to the project (its still just
a series of pending changes). You would have to check out my tip
change and build that to test against.

About half of my series has been reviewed and approved, but I'm
holding off on submitting because I'd like to get this as close to
right the first time as I can, which means trying to gather some
feedback from other projects that need to integrate with it.

I don't want to wait until everything is converted to REST JSON to
submit, and I'm working from my most critical needs backwards towards
the other stuff, which I think is the opposite of what Mylyn Reviews
cares about. But I also want the API to be relatively consistent
across all forms so there are less surprises.


> On Fri, Apr 6, 2012 at 6:25 AM, Shawn Pearce <spearce@xxxxxxxxxxx> wrote:
>> On Thu, Apr 5, 2012 at 00:22, Sascha Scholz <sascha.scholz@xxxxxxxxx> wrote:
>>>
>>> I'm glad to hear that you are working on a REST API for Gerrit. :-)
>>>
>>> In the Mylyn connector we use
>>> ProjectAdminService.visibleProjectDetails (fallback to visibleProjects
>>> for older Gerrit releases).
>>
>> So a replacement for this going forward would be the /projects/ URL:
>>
>>  https://gerrit-review.googlesource.com/34490  -- make /projects/
>>  https://gerrit-review.googlesource.com/34492  -- filtering
>>
>> All older versions of Gerrit will return a 404 for this URL, so newer
>> versions of the connector could ask for this URL first and fall back
>> to the visibleProject method approach.
>>
>> I'm starting to build newer APIs in a similar style, e.g. I have an
>> RFC now pending for /changes/ to search for changes:
>>
>>  https://gerrit-review.googlesource.com/34486
>>
>> Comments from teams that will actually call these APIs would be very
>> much appreciated, as we want these to be the start of a very long term
>> REST like API that everyone can build around with less hackery
>> involved.
>> _______________________________________________
>> egit-dev mailing list
>> egit-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/egit-dev
>
>
>
> --
> Steffen Pingel
> Senior Software Developer, Eclipse Mylyn
> Mylyn Tasks Lead
> http://tasktop.com