Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 456680

Summary:	Allow build platform for specific environment only
Product:	[Eclipse Project] Platform	Reporter:	Andrey Loskutov <loskutov>
Component:	Releng	Assignee:	Platform-Releng-Inbox <platform-releng-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	david_williams, Lars.Vogel, mknauer, pwebster, thanh.ha
Version:	4.5	Keywords:	helpwanted
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Andrey Loskutov

2015-01-05 09:16:51 EST

cd eclipse.platform.releng.aggregator
mvn -e clean verify -Dmaven.test.skip=true

generates the *all* possible sdk builds for *all* platforms into 
eclipse.platform.releng.tychoeclipsebuilder/sdk/target/products/

As discussed on mailing list [1] I would like to request a feature: allow trigger the Eclipse platform build for specific environment only (e.g. Linux GTK 64 bit).

Currently if one has a small patch which need to be integrated for tests into some SDK build on current platform, one has to trigger full build for all environments which takes 1.5 - 2 hours.

It would be really helpful to have some specific profile or goal or setting to trigger the SDK build for specific platform only.

[1] http://dev.eclipse.org/mhonarc/lists/cbi-dev/msg01311.html

Comment 1 Thanh Ha

2015-01-05 09:39:04 EST

I agree. I think what the build should do by default is auto-detect the user's system and build for that environment. I think we'd need to split the build into many profiles though and we will also need a profile to build ALL profiles so that on the build server we can still build for all platforms in the same build as today.

Comment 2 David Williams

2015-01-09 12:18:27 EST

I am not opposed to this idea, but probably more reserved about it than others. 

For a few simple reasons. 

1) I've heard (and from my little experience) the more "profiles" you have, the harder the build is to maintain. Hence, if we do got this route, I'd expect each "Platform profiles" to be a simple as possible. 

2) I'm not sure how much time it would really save. Sure, it will be faster, and maybe even substantially faster ... BUT it won't be 15 times as fast, or anything (I think we currently have 15 "platforms"?), After all, we compile the java once ... and that always has to be done ... and then it's just a small :) matter of copying and assembling. So, before we "commit" to the over head of multiple profiles, I'd appreciate some "time saved" numbers. 

3) There are probably some areas .. certainly swt patches, and similar, ... where a "patch" might be fine for one platform, but, "break" others. 

So, don't let me from discouraging anyone from submitting a high quality patch that accomplishes this, but I wanted to be sure to set expectations. 

If the desire is just to do a "quick personal build" say, as a sanity check, it might be easier to go into your source tree and cut out all the "target environments" you were not interested in?

Comment 3 Lars Vogel

2019-12-05 16:15:19 EST

Please reopen if you plan to work on this.