|Re: product feature cannot be resolved in build [message #557040 is a reply to message #557027]
||Fri, 03 September 2010 17:11
| Alex Kravets
Registered: November 2009
|Johannes Utzig wrote on Fri, 03 September 2010 11:57|
Am 03.09.2010 17:45, schrieb Alex:
> About TP in Hudson. If you already don't have this in place, I suggest
> you create a separate job for TP and reuse the job in your builds. This
> has two advantages: first, you can independently build you TP, second
> your builds are faster because TP does not need to be imported on each
> build but reused. You can reference
> http://www.eclipse.org/forums/index.php?t=msg&th=163429& amp; amp;start=0&S=42b5f47586ad19bd17a9f9fe0e0cb93c
> post for information on how to do it.
Two additional comments on this approach:
1. If you do not delete the materialized TP after the build, the
execution time should be rather similar
2. So far the Target Platform Publisher does not work in a distributed
environment, so it's important that the TP job runs on the same physical
machine as all the builds that use this TP.
I'll have to double check on #1, I was certain that with importtargetdefintion it was always a bit slower.
Thanks for mentioning #2.
Powered by FUDForum
. Page generated in 0.08365 seconds