Submit a patch suggesting what you'd rather have happen.
Or, more simply, override the relevant properties by setting your own
values in your build.properties file:
buildserveruser=dashbu...@build.eclipse.org
signingDir=/home/data/httpd/download-staging.priv/commonBuild
or
buildServerUser=
signingDir=${writableBuildRoot}/signing
That said if the old defaults are no longer valid on the new
build.eclipse.org / hudson.eclipse.org box (eg., dashBuild no longer
exists or no longer has ssh permission) then we need to look at setting
a new default.
Nick
On 09/29/2010 04:51 AM, Christian Saad wrote:
Hi all,
we've adapted our CBI build to run on the new hudson slaves. It works
well until it reaches the signing stage. The signing fails with:
[build] checkForSignedZip:
[build] [exec] Result: 2
[build] [echo] ls: cannot access
<https://hudson.eclipse.org/hudson/job/cbi-soa-jwt-integration/ws/build/signing/I201009281132-out/JWT-Master-I201009281132.zip>:
No such file or directory
This seems to be related to bug 324170.
Problem is, if running in Hudson, buildAllHelper.xml sets the signing
dir to "${writableBuildRoot}/signing" instead of
"/home/data/httpd/download-staging.priv/commonBuild/". Is there a way to
change this behavior?
Thanks,
Chris
_______________________________________________
dash-dev mailing list
dash-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/dash-dev
--
Nick Boldt :: http://nick.divbyzero.com
Release Engineer :: Eclipse Modeling & Dash Athena
_______________________________________________
dash-dev mailing list
dash-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/dash-dev
