The dependencies in BuildMaster don't quite work like, say, NuGet dependencies or something. It's more meant for sharing artifacts and the like. But, check out the "Create Build" or "Promote Build" actions.

There's no file verification per se as the mask is simply a string mask... there would be times where no matching is ideal - it all depends on the situation. If you wanted, you could log all the entries, it's part of the action's configuration.

It wasn't clear to me, from the UI, that I should be selecting the path to the solution file, rather than to the project. When I selected the solution file, the recipe proceeded to create a couple of problematic actions - "Subversion does not support the "Apply Label" operation. I think you're right - I'd be better served building up my deployments from scratch, rather than trying to use the recipes. The recipes seem to make assumptions that don't always fit, and it's easier to build your own than to figure out what they are doing that isn't working.

In BuildMaster 4.2.0, we are making variables usable across almost all of BuildMaster, including notifiers. If you can wait for the next version, you'll just be able to use a variable in an execution completed notifier. We will likely be shipping a 4.2 beta this week. If you need this functionality before then, you'll have to implement a custom notifier.

Hello JP, have you seen the Sleep Action? I think that would solve what you're looking for...

The extension bundles a version of svn.exe, and you can actually find it in and run it from the {BuildMasterInstallDir}\_WEBTMP\ExtTemp\Subversion\Resources\ directory. The command that it runs to validate a connection to a SVN repo is: svn.exe info http://inedo-test-project.googlecode.com/svn/trunk --xml --non-interactive --trust-server-cert [--username xxxx] [--password xxxx] Try that and see what happens when you run it.

We have added this fix to our issue tracker as BM-1428. Keep an eye out on the release notes for it (not sure if it will be 4.1.8 or in 4.2.X when it first comes out).

Thanks for the report - we have reproduced the issue and have implemented a fix for this in v4.1.7 due out later today.

What happens if you put the name of a specific artifact? If it were broken, it would be a problem with the extension (which can be easily fixed and published for download pretty quickly). The source code for this particular action is here: https://github.com/Inedo/bmx-jenkins/blob/master/GetArtifactAction.cs

It is... but in this case it seems the error is that an empty value is attempted to be added; it's hard to know exactly where that value is coming from by just seeing the error message unfortunately... In BuildMaster 4.1 and earlier, empty variable values are not allowed. This will change in 4.2, along with some other improvements.

Wanted to follow up on this issue and thank you for the response. We upgraded from 4.1.5 to 4.1.6 and I reran a script that should have failed and it did indeed throw an error. SQL Server Extension was upgraded to 4.1.3.0 and the expected error is thrown. Thanks again. Source and Target directory same; splitting. AgentBasedAction Initialization Complete: Temp Directory: C:\Program Files\BuildMasterAgent_AGTTMP_A4_S0\TMP Source Directory: C:\Program Files\BuildMasterAgent_AGTTMP_A4_S0\SRC Target Directory: C:\Program Files\BuildMasterAgent_AGTTMP_A4_S0\WRK Server: XXXXXXXXXXXXX (Id: 2) Initializing action... Initialization complete. Executing... DB Version: 1 Current Version: 1 Total Scripts in BuildMaster: 8 Scripts Reported Run by Target DB: 10 Determining scripts that need to be run... Scripts to run: 1 Executing FailFailFail The script "FailFailFail" execution failed. SQL Error: Cannot find the object "dbo.KSJHFKSHFKJSSKFLSJKDF" because it does not exist or you do not have permissions. Execution Complete. Execution complete. Finalizing... Target directory unused; joining with source. Finalization complete.

See: http://stackoverflow.com/questions/22767440/using-teamcity-build-number-in-buildmaster

It sounds like there are some encoding issues; i would make sure your assemblyinfo file in source control is saved as UTF-8.

That seems odd - it's possible Gallio changed the output format of the tests and they are no longer registering correctly as failures in BuildMaster. Can you post the issue on GitHub? https://github.com/Inedo/bmx-gallio/issues

This can sometimes happen if you import a plan from an application that only has a single deployable. It is possible that a deployment plan could be created without being assigned to a deployable, and since applications with a single deployable are designed to hide deployables from the UI, it's difficult to determine what would have caused this. From the UI, the easiest way to ensure that the correct deployables are assigned to an action group is to add a 2nd "dummy" deployable that will re-enable the ability to see assigned deployables from the UI perspective. This will then display the deployable name on the action group as it did before v4.0.

We do intend to upgrade the SDK used to get the newer version working, but there is no specific schedule for when this will happen at this point. If this is a showstopper for your team please email us at support@inedo.com

I'll try changing the type to IIS-hosted and see what comes of it. Just seems a little strange, since we've been running with the same configuration (TCP-hosted) since BM 4.0.5, without any issues. At some point (I believe within the last month), all build agents began failing at random times. Whatever version it was, around the same time we were no longer able to use SSL on the agents and we haven't tried using it since.

I believe someone from our support staff emailed you a quick fix for this. It appears the double.Parse() method was not taking the current NumberFormatInfo into account for some reason.

It's alphabetical. We've considered adding in a sequence, but have found that most folks will prefer the old "GWBasic" route of prepending an integer to the name to determine execution order. First SCript Second Script Last script This ordering comes after the release ordering.