Not currently; but you could use a combination of actions (Generate RElease Notes, SEnd Email) to accomplsih a similar effect.

I'm getting the error with both the bundled client and with Collabnet's Subversion client. I'll into the credentials of the App Pool & Service.

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

Hi Arian, BuildMaster's Database Change Management follows the steps outlined in Database Changes Done Right: http://thedailywtf.com/Articles/Database-Changes-Done-Right.aspx So, basically, each script is assoiciated with a release, and BuildMaster change script executer (action, manual, or self-contained executoer) can tell if the script has been run against a database by maintaining a metadata table. You can use this to configure all sorts of patterns, including what (I think) you're refering to. Alex

I could have sworn I had this set to use asp.net 2. Anyway updated in IIS and seems to be working now. Thanks

Hi David i got a similar error after installing, but in the web server process (inedobmwebsrv). Im my case it occured because the port i chose for the webservice (80) was already in use. A quick check revealed that skype was using port 80 ... quitting skype and restarting the server solved the problem for me. Cheers, Boris

Good question – we’ll have to fix this in our documentation. The BuildMasterUser_Role is for the BuildMaster Application (WebApp/Service) talking to the BuildMaster Database – doesn’t have really anything to do with deploying to databases. The database deployment bits of BuildMaster need only the permissions that the scripts need to run. You set up the database credentials in a your connection string (or, if you’re using integrated authentication, the service account) – so it’s really up to you. We generally recommend giving db_owner against the target database, since your scripts will generally do a bunch of things like create, alter, etc. But that’s up to you. The script will just error out if permissions aren’t there.

The connection string format is just a typical database connection string. You can follow the examples listed here: http://connectionstrings.com/ Specifying init as "yes" will initialize the database if it hasn't already been initialized. You'll need to specify this if you're running the changescripter tool against a DB for the first time.

In case anyone else runs into difficulty with this, as I did, here are a couple of things to keep in mind: You WILL need to install Team Explorer 2012 on the server that will be connecting to TFS -- in my case, since I don't have a dedicated Build server, that means I needed to install Team Explorer BuildMaster server. Installing Team Explorer (http://www.microsoft.com/en-us/download/details.aspx?id=30656) WILL install a "shell" version of Visual Studio 2012. If (like me) you don't want extra tools like VS on your server, it's possible that you may only need the DLLs -- but according to Inedo support, that would be a violation of Microsoft's licensing rules for Team Explorer. In the "Server Name" field, you should enter the complete URL to the TeamProjectCollection you'll be working with, NOT just the main server or web access URL. In my case, this was http://tfs_host:8080/tfs/MyProjectCollection I hope these help someone else; it took a lot of guessing and finessing to figure all this out, as Inedo support reps really don't tend to explain things clearly AT ALL, at least if you're using their Free Support.

Hi, Please ignore this question. The issue was ultimately down to the config file having unescaped percentage symbols within it and hence variable substitution not working. Regards, Jay

Currently, parameters are not supported by that action, though it is likely we will add them. For now if you drop the 'param($SolutionPath)' line it will work.

Yes, just edit the value of the Core.BaseWorkingDirectory key in App_appSettings.config file in the service installation directory. I believe you'll have to restart the service in order for it to use this value as well.

Code sent! hope this helps. A general rule of thumb... An action that inherits from ProviderBasedAction<T> is designed to run an operation on a single provider (Issue, Source Control, Database, etc). The provider and action plumbing take care of the agent and cross-platform things. If the provider doesn't already do what you want it to, then it's almost always easier to just run a command-line action (CommandLineActionBase), as that takes care of all the process logging and other things.

Well, I guess it wasn't meant to be. I just ran a build and that error came back. I set that flag back to false, ran another build and the error went away.

Are you using IIS or the integrated web server? You may want to try the integrated web server. It's possible an IIS/system-wide setting is overriding some of the configration.

I think so, Gary. Thanks again for the pointers. I'll be sure to ask if I have any more questions. Have a great day! Matthew

This appears to be a problem with the tests themselves. I would take a look at the Cleanup method and see what objects could possibly be null. This post (http://stackoverflow.com/a/10751484/44765) shows the some of the differences with running in the command line MsTest vs. Visual Studio.

Are you trying to create a new instance ("tab") on the config file? If so, and if you're getting that error message, then you'll need to go to "Manage Instances" and click "Show Deleted" in the top of the window. From there, you can undelete the instance.

Hi Joe, Sorry for the poor experience... we do strive for a easy OOB experience, but obviously have only so much control over the underlying platform (IIS). SQL Server is required, but you don't have to install SQL Express; we'll try to clarify the "use your own" option on the installation screen. SQL Express is provided for those who don't have a SQL Server instance to use. We don't have much control over the obscene amount of time it takes, but that's why Lights Out is there... The redirection is a result of some IIS configuration. It could be a LOT of different things, maybe .NET 2 isn't installed/configured/enabled, maybe a global handler is there, etc. This is why we provide the integrated web server, to get started faster. Can you provide some specifics about what IIS you're using? We might be able to provide some pointers on where to start looking...

This has been updated; Oracle Extension 3.1 now supports multiple commands per script. You can update this from within BuildMaster