I have been experiencing some odd behaviour with BuildMaster - which I will try to put succinctly, and see if you have an explanation or can give me some advice.
It seems I have to re-create some actions or action groups every so often in order for them to pick up the correct src\wrk directory or a sub directory within that. Sometimes moving around Actions within Action Groups fixes the issue.
For example, today I had a msbuild action that could not find the solution in the SRC directory. When I looked at the directories after the build failed, there was no SRC directory, only a wrk directory. If I copied WRK directory to SRC, Msbuild ran successfully in a command window. When I moved the Build action to the action group above, it worked. I then created a new action group, moved the build action to it and it worked - even though as far as I can tell there was no difference between the new action group and the original failing group.
Another issue I had was, I tried sharing some Action groups from an Application that I set up as a template, with the intention of sharing the action groups across applications. But I when I shared those groups with an existing application, I found that the shared Action group seem to be depositing files in a different directory to non-shared action groups.
Is there something I am missing? Is this some consequence of a set of actions that were created in an earlier version of BuildMaster.