Re: [dash-dev] Problems with signing

[Jacek Pospychała <jacek.p@xxxxxxxx>]

ok, I saw that cbi-soa-jwt-integration is red.
Anyway, I got signing back to work in by cbi build by setting:

buildServerUser=
signingDir=/home/data/httpd/download-staging.priv/commonBuild

and running on master.

________________________________________
From: dash-dev-bounces@xxxxxxxxxxx [dash-dev-bounces@xxxxxxxxxxx] on behalf of Jacek Pospychała [jacek.p@xxxxxxxx]
Sent: 05 October 2010 10:53
To: Tools for Committer Community
Subject: Re: [dash-dev] Problems with signing

hi Chris,
did you make signing in CBI to work in your job?

Jacek

________________________________________
From: dash-dev-bounces@xxxxxxxxxxx [dash-dev-bounces@xxxxxxxxxxx] on behalf of Christian Saad [saad.christian.ml@xxxxxxxxxxxxxx]
Sent: 04 October 2010 17:31
To: Tools for Committer Community
Subject: Re: [dash-dev] Problems with signing

Hi Nick,

thanks for the help. I tried setting the properties manually, but the
signing process now hangs (until the build is aborted) at:

     [build]      [echo] Signing JWT-Master-I201010040811.zip as
dashBuild@xxxxxxxxxxxxxxxxx in
/opt/public/download-staging.priv/commonBuild ...
     [build]
     [build] -timestamp:
     [build]      [echo] 08:14:00
     [build]      [echo] Push JWT-Master-I201010040811.zip to staging
directory

Regards,
Chris


Am 29.09.2010 22:38, schrieb Nick Boldt:
 > 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=dashBuild@xxxxxxxxxxxxxxxxx
 > 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@xxxxxxxxxxx
 >> https://dev.eclipse.org/mailman/listinfo/dash-dev
_______________________________________________
dash-dev mailing list
dash-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dash-dev
_______________________________________________
dash-dev mailing list
dash-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dash-dev