Warn will still automatically advance. I was able to utilize the Set-ReleaseVariable as you suggested. Thanks!

It does not exist yet, I've filed BM-3326 to add it in v6.1.2

Here is a working PowerShell example (v6.1+): Invoke-RestMethod -Method POST -Uri "http://{bmserver:port}/api/releases/builds/deploy?applicationName=ApiTest&releaseNumber=1.2.3&buildNumber=1&key=<api-key>" For pre-v6.1 versions, the equivalent is: Invoke-RestMethod -Method POST -Uri "http://{bmserver:port}/api/releases/packages/deploy?applicationName=ApiTest&releaseNumber=1.2.3&packageNumber=1&key=<api-key>" I have also put in a doc change request to clarify the endpoint names. Additional note: -UseDefaultCredentials would be required if Integrated Authentication were enabled.

Hi Tod, Thank you! I'm never sure if I'm being helpful or just getting in the way. Just can't sit still long enough :).

Thanks for the quick response. Yes, sooner would be great. I will start using the new feature as soon as you can release it, with or without documentation.

Well be releasing BuildMaster 5.1 in just a bit (later today), which will have these operations.

You can perform any action on the BuildMaster (local) server, or on a remote (agent) server. It's quite common to use a dedicated build server (via an agent) to compile source, etc).

Executed with output of: (1 row(s) affected) (1 row(s) affected) Will let you know if I see any more problems like this, Thanks for the incredibly fast turn around time!

For the time being, you've done it correctly! We may modify the build importer to support importing multiple at some point though since this is a fairly typical use case.

Turns out that a default Win7 install (chosen to keep parity with our dev environment) has power saving enabled. Disabling sleep seems to have solved the problem. I am not a smart man...

The 0.0 release is merely a setup release, the number for that cannot be set. However, you can cancel that release and simply create a new one and enter in 1.0 for its release number.

When iam using USB to unlock build master showing error server is not started How can I solve this problem

Can you try to use the "Build .NET Project" without checking "this is a web application"? Then, capture the artifact from _PublishedWebsites\project.name instead? This is how we solve this problem when we build proget (see http://inedo.com/specifics/proget), and we'll soon be adding another option for this action.

Nevermind, the Build was already rejected.

Once created, a Build Release may not be deleted from the UI; this is an important part of the auditing/workflow pieces. There are three options: Clone application - http://inedo.com/support/tutorials/cloning-an-application-with-the-sql-api - this is least risk, but will not copy histories Undocumented Releases_PurgeRelease method; this is generally used for accidently created releases, and will cascade to all builds/promotions/executions/database changes/etc Delete from database tables directly more risky The first is preferred.

I could certainly try this if you can tell me how. Also would it be easy for me to unistall and go back to the previous functionality, if required? Please let me know what i need to do to test this.

Yes,I would think the same. Thanks for clarifying. Please plan to release this fix at the earliest possible and would be glad if you can keep us informed on the same. For now, building .NET projects is really turning out to be a painful task just because of this one issue. Fortunately, there are some tedious workarounds.

I think the problem may have to do with your project/solution configuration (i.e. .sln and .vbproj/.csproj files). In the action's execution log, you can see the exact command run by the Action. I would suggest to run that command at your desktop, and then try to see what specific project is missing the output path... and then tweak the project files.

Thanks look forward to it

My fault, I had forgotten about the shared TMP directory and was focused on the WRK and SRC ones. It appears then that building the same app but different workflows at the same time is not currently supported, but there are workarounds. As an example, you could use a different environment (e.g. Integration2) for the patch workflow, then link/share all the action groups from Integration. If you were to then install a BuildMaster agent on the BuildMaster server (and add it via the Servers page), that agent would have its own set of temporary directories. All you'd have to do is update the "default server" setting for each action group in Integration2 to point to the agent server.