[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] Releasing API changes

There is a shared launch configuration in the repo which points to the class to run all our non-UI tests:
/org.eclipse.equinox.p2.tests/All p2 Tests.launch
All of the tests should launch and pass without additional setup. The exceptions are:
- the reconciler test suite in which you need to download the platform runtime binary and set the "org.eclipse.equinox.p2.reconciler.tests.platform.archive" property to point to it.
- the full install and update test suites which require you to set "org.eclipse.equinox.p2.reconciler.tests.35.platform.archive".

If you would like to create a class/shared launch config which spans across bundles then that would be fine as long as it fits within the current bundle dependencies.

Like Curtis mentioned there is a project set file in the branch for most other projects' bundles. This unfortunately wasn't carried over to HEAD when the branch was merged. I will release it into HEAD.

It is also useful to do test builds on Hudson like Kim mentions. This is what I did on Friday morning and happened to catch some of the compile errors and prevent the build from breaking on Friday night.

Perhaps someone from the PDE team can comment on the target platform setup. I live in a world where I just have everything loaded from HEAD and I have access to quick build downloads so I don't feel your pain.

Inactive hide details for Thomas Hallgren ---03/01/2010 12:28:00 PM---Hi DJ, I have some suggestions that might make the procesThomas Hallgren ---03/01/2010 12:28:00 PM---Hi DJ, I have some suggestions that might make the process smoother.


Thomas Hallgren <thomas@xxxxxxx>


P2 developer discussions <p2-dev@xxxxxxxxxxx>


03/01/2010 12:28 PM


Re: [p2-dev] Releasing API changes

Sent by:


Hi DJ,
I have some suggestions that might make the process smoother.

On 03/01/2010 03:39 PM, DJ Houghton wrote:
> In order to minimize breaking the build, here is a reminder of the
> steps that need to be taken:
> 1). Run all the tests. It only takes a couple of minutes and we should
> be running all our tests before every change anyway.
We have several p2 bundles dedicated to tests. Rather then clicking
through them all and run their respective tests, I think it would be
great if we had one central launcher that would indeed run them all.
Perhaps we have that already and I just haven't found it yet? A single
place for local properties would be good too (where to find a package
zip etc.). Today, I need to tweak launcher properties to make some tests

> 2). Ensure that you have all our projects and dependent projects
> loaded. This includes all the p2 projects as well as the projects
> which are known to depend on us. (for instance PDE and Platform-UI, etc)
A psf file including everything that is expected to be in your workspace
would be helpful. While it may be common knowledge within some groups of
Eclipse, not all of us are aware of what goes beyond the "for instance
..." ;-)

In addition to the above, it would also help if it was easier to
maintain a target platform containing the latest nightly. Today, that
takes forever since most bundles change their qualifier on each build
(downloading from eclipse.org to my location isn't exactly rapid). The
same is true if I want to test the IDE using nightly builds.

- thomas

p2-dev mailing list

GIF image

GIF image