Our build is using a repository from Surround SCM. It seems that only the latest changeset is associated with a build even though the configuration is set to associate all changesets since last successful build. Looking at the build history there are no build with more than one changeset associated for each repository.
The trigger that starts the build is also configured to associate all changesets since last successful build.
We have not been able to reproduce this issue. Note that that the `associate all changesets since last successful build’ option only looks for changesets on the current build branch for each repository which are not already part of a successful build.
Can you post some screenshots of your build history and trigger settings (or send them to me via direct message)?