Jenkins plug-in requires two manual runs before SCM changes are detected correctly

[mirkoseifert]

This is because the state of the working copy is examined by the plug-in before the actual checkout and before the actual build. Thus, the repository list does not exist when the task is triggered for the first time and a second (manual) run is required before the BuildBoostSCM plug-in can correctly determine SCM changes during polling.