Just to be clear, we set up a Hudson slave instance,
not a perfect replica of the build server.
To answer some of your questions:
- I'll look into enabling /usr/bin/sign on build2. Shouldn't be too
difficult since they share a filesystem. Signing will still occur on
the build.eclipse.org for now, but /usr/bin/sign enables you to place
files in the queue.
- You shouldn't need to ssh to build2 since it shares the filesystem
with build. In other words, your workspace should be accessible to the
master.
- For those who use a generic '*Build' account, such as modelingBuild
or wtpBuild, your home directory is not available to the slave server.
I'll see if I can change that.
Thanks for all the testing everyone's been doing. I'm glad to see your
builds are literally flying on build2.
Denis
On 05/14/2010 05:14 AM, Nicolas Bros wrote:
Hi,
With a few modifications, the MoDisco nightly build runs great
on build2 (3 times faster!).
Unfortunately, for the integration build (built with Athena
CBI), signing does not seem to work. It keeps waiting (for 45 minutes)
and then times out.
Maybe the signing "genie" needs to be installed/setup on build2?
In the signing log
I see:
Pseudo-terminal will not be allocated because stdin is not a terminal.
ssh: Could not resolve hostname cd /opt/users/hudsonbuild/workspace/cbi-modisco-integration/build/signing; /usr/bin/sign /opt/users/: Name or service not known
--
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
|
