> What the other comments on this bug haven't mentioned is that the timestamp that is used is the timestamp at the time the build is put into the queue. It is not the timestamp of when the checkout happens.
Woah, that's even worse than I thought (and explains some 'strange' builds which I've seen, which didn't pick up all the changes).
My intuition would have been that it should take the timestamp of when the build is actually started.
Speaking about the options about what should be checked out, I think that there are 3 of them:
I) use latest from repository (i.e. HEAD for SVN)
IMHO the most senseful default for almost all job type
II) use state as of a given timestamp
Probably only useful for matrix jobs
III) build a specific revision
Maybe also usable for matrix jobs. Otherwise useful for post-commit hooks which should trigger a build for this specific revision
Most SCMs I know of should be able to implement all 3 of these options (with the exception of CVS which AFAIR doesn't have a global revision)