Checksums are generated automatically, we check them against the previous build's checksums.
> How would we inform the user that the build was unnecessary?
Send an email saying "The daily build for Project X was not kept as it was identical to the previous build (http://link-to-previous-build)." We could put a limit on these emails, perhaps only send them out three times, or just once saying "Builds will be kept again once the built image changes"
> How do we point people at the latest build? Perhaps a "current" symlink like cdimage?
Sounds good. There's a current symlink there already which points at the current build, but I'm not sure if that gets synced to oem share or not. Probably not as it can point at a failed build. A "latest" symlink sounds good though.
> How would we do the comparison?
Checksums are generated automatically, we check them against the previous build's checksums.
> How would we inform the user that the build was unnecessary?
Send an email saying "The daily build for Project X was not kept as it was identical to the previous build (http:// link-to- previous- build)." We could put a limit on these emails, perhaps only send them out three times, or just once saying "Builds will be kept again once the built image changes"
> How do we point people at the latest build? Perhaps a "current" symlink like cdimage?
Sounds good. There's a current symlink there already which points at the current build, but I'm not sure if that gets synced to oem share or not. Probably not as it can point at a failed build. A "latest" symlink sounds good though.