Well be releasing BuildMaster 5.1 in just a bit (later today), which will have these operations.

Hi Jan, Subversion does not support the "Apply Label" operation, so it complains about this. The UI is supposed to prevent you from using this action, but I think one of the recipes will create this action for you. Just replace the Apply Label / Get Labeled action pair with: Tag /trunk/mypath to /tags/%RELNO%.%BLDNO% Get Latest from /tags/%RELNO%.%BLDNO% Hope that helps, Tod

Yes, as long as BuildMaster supports (see http://inedo.com/buildmaster/integration) the source control provider. It is a best-practice to label your code with a release and build number combination such that it can be retrieved at any point in the future, and more specifically, if you are promoting your code to a further environment. You can set up your BuildMaster action to use the built-in variables %RELNO% and %BLDNO% to accomplish this.

We do use the specific paths under the project root. The issue still occurred, but we altered our labels to have a text precursor and now it works. It appears to be an issue with mostly numeric labels and TFS. If two apps in the same root project happened to get similar release numbers... then it bombed.