It calls home to the Signing server to see if your plugins have finished
being signed. If not, it goes back to sleep for 180 seconds and then
checks again. Around milestone time there is a back up typically on
the signing server so it may take longer. Which is why unless you are
doing Integration or Release builds, we don't recommend signing other
builds. Just takes to long.
Dave
Miles Parker wrote:
Hi all,
I'm curious what is happening in check for signed zip. I've been
noticing that I'm intermittently (I think) getting times outs during
this step, i.e.:
checkForSignedZip:
[exec] Result: 2
[echo] /bin/ls:
/opt/users/hudsonbuild/.hudson/jobs/cbi-amp-nightly/workspace/build/signing/I200912171449-out/AMP-Master-I200912171449.zip:
No such file or directory
[retry] Attempt [3]: error occurred; retrying...
[echo] Sleep for 180 seconds...
And in the signing dir at the same time I have something like:
ls
/opt/users/hudsonbuild/.hudson/jobs/cbi-amp-nightly/workspace/build/signing/I200912171449-out/
AMP-Master-I200912171449.zip.temp temp_AMP-Master-I200912171449.zip
It's gone up as high as 8 attempts that I've seen. Is this just some
kind of normal concurrent process?
cheers,
Miles
___
dash-dev mailing list
dash-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/dash-dev
___
dash-dev mailing list
dash-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/dash-dev
