Exactness of build with respect to revisions

[Georges Racinet]

Currently, new changesets are detected (by poll or mirror) and that triggers a build, that performs bin/buildout, leading to update to the latest version. Due to inavoidable lag, the build could very well include changesets that were pushed after its triggering.

This is very classic, and can lead to confusion : the list of changesets (blamelist) related to a failure can be wrong, the wrong people notified, disturbed etc for that.

The new 'revisions' option of anybox.recipe.openerp offers an opportunity to have an exact blamelist : have the build process produce an extension buildout ('buildslave.cfg') with the precise revisions. This makes few sense without codebases, and would probably not be a minor effort, but would make for a much saner system.