|
| Re: problems using b3aggregator & hudson with buckminster [message #650000 is a reply to message #649997] |
Fri, 21 January 2011 11:49   |
 Johannes Utzig
Messages: 329
Registered: July 2009 |
Senior Member |
|
|
Hi David,
Am 21.01.2011 12:33, schrieb david@gonzalez-casin.de:
> After trying some other things i took a look in the workspace the jobs
> create and i just wondered how they could build the component because in
> this workspace was nearly nothing checked out from SVN (only the cquery
> and the rmap). I set the loglevel of Buckminster to 'Debug' and found
> out that Buckminster resolves the plugins from the target platform - and
> not from the aggregated repo or SVN. And i wonder why.
> In my rmap i have 3 locators. The first one catches the plugins of the
> components that should be loaded from SVN, the second one catches all
> other of our plugins that are needed and the last one catches alle
> eclipse plugins. The last two should both get their plugins from the
> aggregated repo.
Obviously your SVN Locator (at one point) did not find the plugins in
question, so another reader was selected. This reader probably found the
bundles in your aggregated repository.
Since you probably did not define an MSPEC, the default behaviour if a
binary bundle is found is to stuff it into the target platform.
If you do not want the binary bundles from the aggregated repository to
end up in the target platform then you need an mspec to define this
behaviour.
After that you might have fixed the rmap so buckminster would in theory
be able to find the stuff in SVN, but:
It will not even try your rmap anymore since these bundle are already
installed in your target platform now.
There is two things you could do in such a case:
1. Create an advisor node in your query and do not allow the resolution
scope "Target Platform" for the bundles you want to download from the
aggregated Repo. That means however, that they have to be downloaded on
every build, which might, or might not be what you want
2. Make sure in your IDE that the locator that points to your SVN really
works as expected. Once you confirmed in an empty workspace that your
rmap finds everything from the right place, delete the target platform
in hudson and start over.
Best regards,
Johannes
|
|
|
|
|
| Re: problems using b3aggregator & hudson with buckminster [message #651477 is a reply to message #649997] |
Mon, 31 January 2011 10:31 |
David Gonzalez
Messages: 24
Registered: January 2011 |
Junior Member |
|
|
Thank you, works fine for the moment!
Now I have another question. I use the following command to build my p2 site:
| Quote: | perform -P '${WORKSPACE}com.example.releng/buckminster_p2site.propertie s' com.example.releng#site.p2
|
Works fine, but i want to have the output in a specified folder. In my .properties file I could set a property like this:
| Quote: | buckminster.output.root=C:/test/
|
But then all the output goes there - I just want to have the output of the action #site.p2 there. Is there a possibility to do that? Otherwise I could move them with some shell commands via Hudson (but that doesn't sound like fun, I hope there is a better way to do that).
[Updated on: Mon, 31 January 2011 10:31] Report message to a moderator |
|
|
|
Powered by
FUDForum. Page generated in 0.03136 seconds
] 
Search
Help
Register
Login
Home
