Community
Participate
Working Groups
Build Identifier: buckminster headless_1.4.0.v20110915-1108 Buckminster seems no to resolve plugin fragments included in features for platforms other than those the buckminster instance is running on. The import command seems to resolve the plugins. But the build command seems not (see warning). If the site.p2 action needs the plugin for repository build, the above warning results in an error. See attached error log. The problem is simplified for reproduction using plugins without any functionality. Reproducible: Always Steps to Reproduce: 1. build headless out of jenkins using buckminster blugin 1.1 checkout the project (see attached code) into ${WORKSPACE}/testproj 1.2 create buckminster action import '${WORKSPACE}/testproj/my.test.site/site.cquery' build -c -D target.os=* -D target.ws=* -D target.arch=* perform -D target.os=win32 -D target.ws=* -D target.arch=* my.test.site#site.p2 perform -D target.os=win32 -D target.ws=win32 -D target.arch=x86 -D tprepo='file:///C:/workspace/serviceTargetPlatform/repo' my.test.site#create.product.zip 1.3 run job
Created attachment 207182 [details] bug and env description for reproduction
Created attachment 207183 [details] error log containing the build result
Seems to me you don't pass the -D target.os=* -D target.ws=* -D target.arch=* to the import command. Do you have them declared as properties in your cquery?
Created attachment 207184 [details] source code of siplified test project
O.K. great that was it... sorry for the bug. Unfortunately i didn't found any hint that the platform has to be given at import time already (maybe should be added to definitive guide next time). Over 300 views on eclipse forum thread didn't bring answer as well...
(In reply to comment #5) > O.K. great that was it... sorry for the bug. > Unfortunately i didn't found any hint that the platform has to be given at > import time already (maybe should be added to definitive guide next time). Over > 300 views on eclipse forum thread didn't bring answer as well... I would be grateful if you could log an enhancement request for the documentation with a reference to where in the documentation you would like to see something added. (Where did you try to find relevant information for what you were doing).
