We are trying to promote an application build to a particular environment using API, but we can't seem to get it working. We created full (unrestricted) access key for this.
Tried 2 type of calls:

1. This one returns 404:

http://bmserver:port/api/releases/builds/deploy?buildNumber=3&releaseId=722&applicationId=123&toStage=Development&key=<APIKey>

2. This one returns 500 server error:

http://bmserver:port/api/json/Builds_PromoteBuild?Application_Id=123&Release_Number=0.0.4&Build_Number=3&Comments_Text=SomeText&ForcePromotion_Indicator=N&PromoteTo_PipelineStage_Name=Development&SetFurthestStage_Indicator=N&key=<APIKey>

3. Calling another method with the same API key works fine:

http://bmserver:port/api/json/Builds_GetExecution?Execution_Id=25537&key=<APIKey>

Tried switching between releaseId/releaseNumber didn't help much. Can you provide a complete sample call to promote/deploy a build?

Thanks

Product: BuildMaster
Version: 5.8.2

What is the best way to verify that the variable exists? I.e. if variable can't be resolved the execution fails, but most of the time we don't want to fail it, we just need to continue with some default value provided in that plan.
So far the only workaround I found is to run the check in try-catch block and assign the default this way, but it still produces a warning in the plan execution. Ideally we just need to assign the default value if the variable can't be resolved, without any errors or warnings.

set $BuildTestsFlag = "";
    try
    {
        set $BuildTestsFlag = $BuildTests;
        Log-Information BuildTests variable is set to $BuildTestsFlag;
    }
    catch
    {
        Log-Information BuildTests variable is not defined so we will not build tests;
    }

Product: BuildMaster
Version: 5.8.2

Buildmaster engine can't find label when searching in TFS root.
Here is the scenario:

1. I create a label in TFS manually and add multiple files from multiple projects, I.e from multiple subfolders under root.
2. I then try to retrieve the files in execution plan using either Get-Labeled-Source or Tfs-GetSource, specifying Label name.
   As for SourcePath if I provide TFS root ($/) I get an error "TF14064: Could not find label". If I provide one of the Project level subfolders - BM does find label and pulls the files for it correctly, but only for this project folder.

When I search for label in TFS manually from the root level I'm able to find it. Shouldn't Buildmaster also be able to find the label when SourcePath is root? What am I doing wrong?
Any advice?

Product: BuildMaster
Version: 5.8.2

Hi, 2 questions regarding event logging.

1. Our security team needs more descriptive logging, i.e. if a security role changed it would help to see the role name (not just id#) and what was changed. Any plans to extend logging to include more info?
2. Can event logs be exported/imported in any way? As it is now search, sort, filter and general work with event logs is very hard to perform considering it's only available on the web page.

Product: BuildMaster
Version: 5.8.2

Hi,
I'm trying to apply a label in TFS during Dev deployment Execution and getting the error below. Agent is installed, appears to be running ok and this dll exists in BuildMasterAgent_AGTTMP\ExtTemp\TFS folder. This same setup works on other servers, but not on this one for some reason. Any idea why this error comes up?

DEBUG: Server: ServerName2 (Id: 24)

DEBUG: Initializing action...

DEBUG: Initialization complete. Executing...

INFO: Executing Apply Label...

INFO: Applying label "ConfigLoader-0.0.1.1" to path "$/Applications/src/" ...

ERROR: An unhandled exception occurred while executing this action: System.Web.Services.Protocols.SoapException: Could not load file or assembly 'Microsoft.TeamFoundation.Client, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
at Inedo.BuildMaster.Extensibility.Agents.Tcp.TcpAgent.Inedo.BuildMaster.Extensibility.Agents.IRemoteCommandExecuter.ExecuteCommand(RemoteActionBase action, String commandName, String[] commandArgs)

Product: BuildMaster
Version: 4.9.7

Thanks for response.

I created a new API Key. My environment IDs are as follows:
Development = 1,
Testing = 2,
Production = 3,
Build = 5

If I run the API call you provided above for Build environment, doesn't it mean I will need to resequence the rest of the environments too?

Buildmaster version 4.9.7.5 has been successfully upgraded to 5.6.11.2
However during the upgrade Build Environment was not created, so I had to create it manually and it is now the last Environment in Environments list. I ran some test builds after the upgrade, and they went through fine. The problem is that Build Environment is now showing up as final environment for all apps when clicking Applications, even though it's not the case for any of them, and legacy plans and pipelines seem to be working correctly.

Any ideas how to fix this?
Thanks

Product: BuildMaster
Version: 5.6.11

Here is an example path to a .pdb file, the same folder contains .dll:

C:\Users\nsitnikov.dnx\packages\JA.AppCentral.Logging\0.1.7-Build1\lib\dnx451\JA.AppCentral.Logging.pdb

Package folder also contains the source in C:\Users\nsitnikov.dnx\packages\JA.AppCentral.Logging\0.1.7-Build1\src folder

Trying to setup symbols to be able to debug nuget package as described here:
http://inedo.com/support/kb/1036/using-progets-symbol-server

Package gets built and pushed to Proget using BuildMaster. I setup VS options as described and I do see the .pdb files when I open package page in Proget and click on the View for "Symbols and source files are available", meaning they exist and are indexed. I configured the feed to not strip the symbols when downloading the package. Then I install the package via Nuget Package Manager UI or Package Manager Console with -Source option.

When debugging through the code that uses this package VS tries to open the source file on the Buildmaster server, where it was built from, as local file (D:\Buildmaster_SVCTMP...) and sure enough the file is not on my local drive, it's on BM server.

What am I missing?
Thanks,
Nik

Product: ProGet
Version: 4.0.9

I'm trying to use variables defined in Admin->Environments or Admin->Servers. When the variable is defined in one of these sections and then I'm trying to use it in one of the powershell scripts as Ambient Variable - script doesn't recognize it.

E.g. I defined a variable for one of the Environments as EnvCode = DEV1. Then in one of the scripts in Script Repository I define Ambient Variable and for its value I use $EnvCode, similar how I would use built-in variable like $ReleaseNumber. When script is running instead of actual $EnvCode value "DEV1" it just sees it as literal "$EnvCode".

What would be the correct usage of Environment or Server variables? Can I use them in scripts at all? If not - where and how can they be used?

Thanks

Product: BuildMaster
Version: 4.9.7