Description Kim Moir 2009-11-11 17:07:08 EST

The signing process at eclipse takes our build about an hour.  For integration builds, this is rather inefficient because all of the bundles don't change every time.  Some background on how the build works:

When we run a build, we compare the bundles in the existing repo with the newly produced bundles.  If the bundle already exists in the repo, we use the old bundle in the zips.  The new bundles are discarded.  This replicates the user experience, where the user doesn't update their install unless there's a new version.  

From the perspective of the signing process, this is rather inefficient because we are signing bundles that we are discarding.  (In a nightly build, the qualifiers of the bundles are changed  to match the buildid so this doesn't apply.) The important case is for integration builds.  This case is especially useful during integration rebuilds where we only rebuild a few bundles.  

To fix this problem
1) Run the comparator before the bundles are signed
2) Generate a list of bundles that have changed
3) slice off these bundles from the repo
4) send them off to be signed
5) copy newly signed bundles into the repo
6) run p2.process.artifacts to update the artifact descriptors

For 1) the comparator needs to be updated have a parameter to ignore differences in the manifest (signed versus unsigned).  I talked to Andrew regarding this and he said it wouldn't be a problem so I'll open a bug against p2 for this issue.