This sound like it's just a tough process to model. No matter what you do, you can't have it both ways such that you could deploy to either a subset of DevX servers to an arbitrary subset of QAX servers. The options you'll have to decide on are either: use different workflows and different environments to separate Dev1 from Dev2, which will force releases to use a specific set of servers after a build is created for it use abstract environments (Dev, QA) with server variables that resolve to different server groups (e.g. DevSet1, DevSet2, or whatever), and select the result either at release, build, or promotion time so it provides historical context with the release/build In BuildMaster, the idea of an Environment (i.e. a different stage of testing) is meant to be abstracted from a Server (i.e. a physical/virtual machine), so whatever follows most closely to this paradigm would be the way to go.

Thanks for the report - this should be fixed on the server end now, and you should be able to see the release notes on your end.

No, the URL triggered builds are designed to be "fire and forget". However, even without a quiet period, the builds are still queued in a sense that they will not run over the top of themselves until the previous one is completed.

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.

I didn't run it as an admin, but I think it popped up the UAC prompt. Also, it managed to delete most of the contents of the proget directory in program files. Unfortunately, that's all the info I've got. Hope it helps you out.

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.

Unfortunately at this point, we have no good examples of this sort of thing. You might be able to get away with inheriting from DirectoryPackageStore and extending its behavior on EnableChangeNotifications() to add your own FileSystemWatcher, but it all seems unnecessarily complicated when a simple scheduled task would do the trick.

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.

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).

We've made settings part of BuildMaster like that in the past (e.g. FormsAuthenticationTimeout). Since I'm not sure how we'll handle this particular setting in the future, you can set the value in machine.config for the time being. You can find the .config here: C:\Windows\Microsoft.NET\Framework[version]\config\machine.config

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...

Are you still experiencing this problem? The ProGet service is very lightweight and should startup almost instantly, though it's possible that the database connection is what's taking the time. Could you try running the ProGet service interactively? (Make sure to stop the service and run the ProGet.Service.exe executable) This will give instant logging feedback and detail any errors or connection slowness as it happens.

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

we fixed our problem. after many tests we found out that we must use the absolute name of the package "CompanyName.Project.Common.Application" and not only application.

Thanks Tod! Works like a charm. Perhaps a better approach would be to clear the handlers and add only the ones used by the application? In any case that pretty much solves it for us (until the next problematic suffix...) Thank you.

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.

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.