FYI - that's the "Operation" for our Otter product, but the BuildMaster Action works about the same... But in either case you will need to have an agent installed in order to stop the app pool on that server. Alternatively, you could use powershell script to do it, but that would require additional ports and the like be open on the remote server (RPC, maybe?)

For all lookers, answer chain above resolves the question Awesome, thanks for the great support. I'll look forward to the Extension, in the meantime I think I have enough going now to generalize for the rest of our environment. Thanks for the assistance, and as I mentioned -- the product so far is excellent and we will definitely be purchasing the Enterprise as soon as I get quotes back! ;-) Cheers!

Hey Alana, That option sounds fine to me. I certainly think it would cut down the time to spawn up new Applications for us.

We have fixed this for v4.5.8. For users of v4.5.7, you may download a script patch here: http://44.inedo.com/buildmaster/v4.5.7-JS-Patch.zip This .zip file will contain a JavaScript file that should be saved in the \Resources\jQuery subdirectory of the BuildMaster web application installation. Its presence will override that of the existing DeploymentPlans.Common.js.gz file, and the page should refresh correctly once it's there (you may need to CTRL+F5 the browser once if it doesn't work right away).

Sure, we'll add that to the next maintenance release which should be out later today.

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.

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

This is not supported, as the comparison report is multiple HTML files; perhaps send a link to the build page itself?

Hi Bryant, This is not supported as of yet, though we do hope to address it in BuildMaster 4.1. It is possible to write your own custom actions... and now that BuildMaster is on .NET 4.0 it wouldn't be so difficult to... query the database for the members of a server group do a Parallel.ForEach on the results, and perform the file transfer in that manner

It was very helpful.

When you say delete, do you mean remove from a workflow such that the build never travels into that environment? If so, just delete the workflow step from the workflow. If you actually want to keep the workflow step but remove all the action groups, just delete them one-by-one.