We've been using the remote-run commit after build option to ensure our changes don't break the repository, but there is a problem when the build and commit has finished - the files committed from IDEA are not updated with the new repository revision, and performing a manual 'Update File' or 'Update Project' doesn't fix this. However, as the correct revision is in the repository, performing a 'Rollback' on the files does update them with the new revision (which is a bit disturbing).
The only way I can make sense of this, is that the files are sent to the agent for the build, and if it is successful, they get committed to the repository from the agent rather than from IDEA - so as far as IDEA is concerned, they haven't been committed yet, even though there's a new revision in the repository. Thus, an update has no effect, and a rollback replaces them with the latest revision.
Because of the problems caused by this, we have had to drop using the automatic pre-tested commit option, and revert to a manual build and commit process.
Is this a bug or a configuration problem? If the latter, what is the correct configuration to get this procedure to work as expected?