Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Fwd: [linuxtools-dev] PDE API Analysis enabled on linuxtools-gerrit Hudson Job

It's quite a bit of "manual" setup (ant, shell script, etc). I don't mind if we set it up for CDT but I think we really need a Tycho plugin for this. It would not be ideal for all projects to have to do all this setup. I think we should be able to just configure a Tycho plugin with a given baseline (.target?) and that's it.


From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Doug Schaefer [cdtdoug@xxxxxxxxx]
Sent: Friday, 08 January 2016 4:33 PM
To: CDT General developers list.
Subject: [cdt-dev] Fwd: [linuxtools-dev] PDE API Analysis enabled on linuxtools-gerrit Hudson Job

We should do the same for CDT, or do we already?

---------- Forwarded message ----------
From: Roland Grunberg <rgrunber@xxxxxxxxxx>
Date: Fri, Jan 8, 2016 at 2:15 PM
Subject: [linuxtools-dev] PDE API Analysis enabled on linuxtools-gerrit Hudson Job
To: Linux Tools developer discussions <linuxtools-dev@xxxxxxxxxxx>

I have enabled the 'apianalysis' task from the apitooling-ant.jar that
resides within This is pretty much the same as
setting an API Baseline for a running Eclipse instance but in this case
it'll be done for every patch pushed to review.

The build proceeds in a normal way and additionally generates the api
description information as part of building each bundle. The final p2
repositories are then compared to a baseline version (eg. 4.2.0).
The time taken for the build is nearly the same as before.

This doesn't mean that reviewers need not worry about major/minor breakage
since it might happen that we designate a particular branch for only bug
fixes, but someone may mistakenly bump the minor version.

Roland Grunberg
linuxtools-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top