The built-in action only supports setting the value for a known variable, but you could either write a custom action/extension or add 3 actions that set: key=(value) => $Value (key)=value => $Key Then add a Set Variable Value action that sets $Key = $Value

This behavior is supported, yes; however, starting/stopping services requires Admin privileges. Does the user hosting the BuildMaster service have this?

This question is answered here: http://stackoverflow.com/questions/26592119/buildmaster-net-framework

Have you seen this? http://inedo.com/support/tutorials/creating-an-auto-deploying-custom-extension-application But in short, you put {YourExtension}.dll inside {YourExtension}.bmx, where .bmx is simply a .zip file renamed to .bmx. For the ClickOnce action, take a look at: http://inedo.com/buildmaster/extensions/.NET/Inedo.BuildMasterExtensions.DotNet2.ClickOnceAction

How are you creating your application, can you provide an repro steps?

Does this still happen if you add another action after getting the TeamCity artifact? Maybe add a Sleep action with a delay of 5 seconds, just to see if you still get this behavior. I suspect it may be a SQL deadlock issue when an execution completes, but we are still looking into this, and we only have one server we can reproduce this on.

When you say, "TFS build gets the Source and builds all in one step" ---- do you mean there's a single action (like an MSBuild script) that gets source and builds? If so, then you'll need to make a parameter to this script, and have that update the build/release number with the approraite buildmaster variables.

Thanks Tod, that's exactly what I needed. Works like a charm. -Tim

This error means that the TFS URL has not been set; you'll need to configure this on the Admin > Extensions > TFS page.

Well, hmm, I'm not sure how that would happen... unless there's multiple services running? You edit it directly in the database (Servers table); if it flips back, that means something really strange is happening (such as the two services).

I know it's a little late. I had the same problem today and solved it by installing Microsoft Sysinternals SubInCal (https://www.microsoft.com/en-us/download/details.aspx?id=23510). Set the permissions with: cd "C:\Program Files (x86)\Windows Resource Kits\Tools\)" subinacl.exe /service INEDOBMSVC /grant=domain\user=PTOS

Yes, just inherit from PredicateBase in the SDK. If you don't already have a custom extension, check out the Creating an Auto-Deploying Custom Extension Application tutorial to create one - it will also have a Sample Predicate within it.

The best solution is to assign a domain account that does have the privileges to start/stop the service. There are some other solutions detailed here: http://serverfault.com/questions/187302/how-do-i-grant-start-stop-restart-permissions-on-a-service-to-an-arbitrary-user

When run in parallel, there is no guarantee with the ordering the value is set (and the change would be observed in different groups), so you'd have to create separate variables in each group if you have multiple action groups using different server groups.

The agent does not initiate any traffic back to the BuildMaster server, so no rule needed. The agent installer has the option to auto-register the agent against the BuildMaster server, but that's done under the account of whatever user is installing it, and it only happens once. It's also easy to register a server in BuildMaster too.

Thanks for the report - there is a new version available from the Extension Gallery (v4.1) that should resolve this.

IN Database connections, the "Server" field is where the connection will originate from. If your BuildMaster server can talk to database (i.e. has both network access, permission, and drivers), then it's usually simpler to enter the connection string and not worry about installing an agent. It's not a problem to install the agent, it's just not always necessary. Of course, if you need to do other things such as transfer files, then an agent will come in handy.

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

We've fixed the delete issue for the next maintenance release (v4.4.5), and we'll look into adding something to show the applications that consume the workflow - not sure if that will make that version or not.

Yes, this is a bug. We've been able to reproduce and fix it. The fix will be included in the next BuildMaster release, but if you would like a SQL patch to run sooner, you can email support at inedo.com and we'll send it to you.