GlenGAs is always the case... as soon as you post something, a light-bulb goes on... I've realised that it is the Server File that is being created 12-14 minutes after the last patch file is built. So that appears to be the holdup....
The 'wait' period after patches are created
GlenGOn my solution wyBuild takes around 8 minutes to create 42 patches between the old and the new versions. No problem there... that's great, it's a big solution. At this point I can see all the completed files in the output folder. What I am finding is that on average wyBuild then appears to 'sit' for another 12-14 minutes after creating all the patches before completing. This occurs both from the Command Line and UI. And the period appears to be the same in the new 2.6.16.2 release as it was in earlier releases.
I'm sure 'something' must be happening, but it's unclear what it is... or if nothing is happening, what is wyBuild waiting for? I don't see any CPU usage or memory increase/decrease in this 'sitting' period.
This is obviously not an urgent issue and it doesn't effect our final product... it's just adding time to the overall build process and I'm curious to find out if this is something unique to me (perhaps my build machine?), or if it is common, or if there is something I can do to 'help' wyBuild know it is done and can move on.
GlenG
Are your update files (*.wyu) very large? The holdup is most likely the signing process. This is where wyBuild reads in each whole *.wyu file and generates a cryptographically signed hash of the update. This is used for verifying the updates are correct.