Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Directory Issues
-
Hi,
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.
Product: BuildMaster
Version: 4.1.1
-
In short, if you are relying on exact paths, you should use the ~\ syntax with directories (e.g. ~\Source, ~\BuildOutput, etc.) which represents an application-relative path and doesn't use any SRC or WRK directories.
How the SRC and WRK directories work under the hood is as follows:
The WRK directory is used as either the source or target directory if they are not both set to use their default paths. If there is a source and target path that are both set to the default, a SRC directory is used as the Source and WRK becomes the target. Before this, the contents of WRK left over from the previous action are moved into SRC in order to work with those files (you'll see "Source and Target directory same; splitting." in the logs when this happens.)