It should work exactly as if you were running the command yourself as the user configured in the SSH agent in the working directory supplied in the Execute Command Line Action. What BuildMaster version are you running? We have just released 4.0.6 as a beta, but it's very close to becoming our official 4.0 release if you're interested in upgrading to it. Could you try to fully qualify the path to "asadmin" in the build script?

We managed to resolve this - it turns out that the proget feeds were being ignored because the version of proget was not compatible with NuGet 2.7.1. An update to the latest version of ProGet resolved the issue. Thanks for the response though! :)

If you look in the Service subdirectory of the BuildMaster installation, you'll find BuildMaster.Configuration.AdminTool.exe which can clear the set of licensed users. Since licensed users are added back as soon as they log in, that should be all you need.

See Q&A 947. This will be fixed in 3.7.1; but a patch is available. Just email support - at- inedo - dot - com, and we'll send it over. In the mean time, I've emailed you the patch.

I'm sorry, I'm an idiot. I had chosen a long name for the application, so the "succeeded" or "failed" part of the subject line was cutting off in my email client. Sorry to waste your time.

I think I'm getting a handle on this now. Pretty cool stuff. Thanks so much for your help!

This message is coming from an IIS-hosted agent, and means that the agent is misconfigured in IIS - perhaps this is pointing to a different host name, has proxy issues, etc. Perhaps try the self-hosted agent instead.

Could you check if the "gallio-report" file is under C:\BuildMaster_SVCTMP_A1004_S0\TMP and paste its contents here or email it to support@inedo.com? If you're familiar with C# you can see the code for the Gallio extension here: https://github.com/Inedo/bmx-gallio/blob/master/GallioUnitTestAction.cs - it's almost certainly caused by one of the DateTime.Parse() or Double.Parse() calls.

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

You can try this method with the BuildMaster service (INEDOBMSVC) or agent (INEDOBMAGT) if it's running on a remote server: http://www.codeproject.com/Articles/4891/Interact-With-Desktop-when-Installing-Windows-Serv

The editors/extensions are sealed, so unfortunately the only pattern available at this time is the "Inherits by Clipboard" pattern. In this case it shouldn't be so bad, since it's a couple-line action+editor.

I was able to resolve this issue using this format: DATA Source=<value from tnsnames.ora>;USER ID=<myusername>;PASSWORD=<mypassword>; I restarted my system to restart Oracle. Then Test Connection was successful after that.

Your best bet would probably be to use the Clone method via the API: http://inedo.com/support/tutorials/cloning-an-application-with-the-sql-api

One thing we could do is modify the "Execution Complete Notifier" to send a notification out when a warning occurs. There is currently an option to send the notification only on failure. Would that be helpful?

Thanks Peijen! In this case, you would use the Set Variable Values action to set the TargetDatabaseUsername variable name to %DatabaseUsername%. When the action is run, the TargetDatabaseUsername variable will be set to whatever the value of DatabaseUsername is at the time.

I would just move it to an application group called "Inactive".

Every .NET project that consumes NuGet packages has a packages.config file, and that should be in source control. Unless I'm missing something, the deployment plan actions should be as simple as "Getting Latest" from TFS, then an "Install NuGet Packages" action followed by "Create NuGet Package".

The root cause of this is that an undeclared execution variable is being created to override a declared non-execution variable. For example, if you create TESTVAR as a Release Variable but not as an Execution Variable, then use Set Variable Value to override TESTVAR value for the execution, it will exhibit this behavior. This will be fixed in a future version 3.7.1; either with a more helpful error or supporting the behavior.

This will be fixed in 3.7.1; but a patch is available for those on 3.7.0. Just email support - at- inedo - dot - com, and we'll send it over.

Yes it would, but the editor UI may attempt to validate the credential. The way to get around this would be to edit the Action XML directly and replace the principal name with %VARNAME%. We'll add a fix in a future version of BuildMaster (likely 4.x) to bypass this validation if %[A-Z]% or something is matched.