|
|
|
|
| Re: internal error during importing [message #534527 is a reply to message #534517] |
Wed, 19 May 2010 12:48   |
 Johannes Utzig
Messages: 329
Registered: July 2009 |
Senior Member |
|
|
Hi Andreas,
comments inline
Am 19.05.2010 14:10, schrieb Andreas Pakulat:
>
> Unfortunately I currently don't see how this should work (but that may
> just be because I don't know buckminster that well yet). The reason is that
> to be able to run a perform mailto:xxx@save.env I'd first have to do an
> import to make the component known to buckminster. At least buckminster
> complains
> about not knowing the component when I do the perform first and then the
> import. And as the import triggers the failure the perform after it
> won't be
> executed. I've hence specified an ant-job that runs before buckminster
> that calls the echoproperties (see the end of this message for the
> content).
That's right of course, stupid suggestion from my side :)
But your idea with the ant build step works just fine of course.
>
> The other option I thought about to at least find out what it tries to
> resolve there that throws the error would be building buckminster myself,
> but unfortunately I didn't find instructions that worked for that.
>
>
You don't really need to build buckminster yourself. As long as you have
the source code available in Eclipse you should be able to do a remote
debugging in Eclipse if you add something like this as an additional
startup parameter to your Buckminster build step:
-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=104 4
I don't really understand the behavior you're observing, it just doesn't
make sense that it works if you invoke it manually, but not from within
Hudson. The only explanation seems to be the env.vars.
Before version 1.0.3 of the Hudson Plugin the environment variables
given by hudson were not passed to buckminster (a bug).
Maybe if you uninstall the plugin and then install 1.0.2
( http://hudson-ci.org/download/plugins/buckminster/1.0.2/buck minster.hpi) it
would get clearify if it really is caused by one of the environment
variables or not.
I wish I could do more to help you find this issue, but local resolution
works just fine on my build server and I don't know how I'd be able to
reproduce this.
Regards,
Johannes
|
|
|
|
Powered by
FUDForum. Page generated in 0.03002 seconds
] 
Search
Help
Register
Login
Home
Yesterday I was able to solve the certificate problem and then could run the build successfully. Today I worked on making the target platform download from update-sites and also auto-installed buckminster into hudson (from the 3.6 update-site). Unfortunately ever since I started to change things I'm getting an internal error while buckminster runs its import command:
