What it sounds like you're talking about is a "Build Importer"? We have one built for TFS - https://github.com/Inedo/bmx-tfs/tree/master/BuildImporter - and the basic idea is that you import your build's artifacts using that. As for chaging the status on VSOnline, that hopefully is just an HTTP Post, or it may require a custom action.

I hadn't thought of using BuildMaster like that. What I have implemented and seems to work well is a groovy script that make use of the BuildMaster and Artifactory json api's: Get List of all envrionment for this Application using GetEnvironments api For each environment get a list of the last 'X' builds and add to a list of of versions to keep using GetExecutions. As a build may get reapplied to the same envrionment several times to repair a failed deployment I get more than I need and only keep the to X unqiue versions for that environment. Get a list of folders from Artifactory for our application (each build is stored in seperate folder) using FolderInfo api For each folder returned, check its in our keep list, if not delete it using DeleteItem api

In 3.3.4 no; it is set to 1 minute and cannot be changed. We of course could make this configurable if 1 minute isn't quick enough.

This is a known issue having to do with the application & application group filtering of event listeners and was resolved in v4.5.4 (under issue # BM-1675), which was released yesterday - an upgrade will resolve it.

Reboot fixed the issues. Thanks for your reply.

Looks like there was an additional issue being caused by the feed metadata being slightly off. We've published another fix (v3.3.4).

Thank you, REPLACE works as intended.

This should be done on the Workflow page - you can add a Post-Deployment step "Auto-Promote Build to Next Environment" to any workflow step.

This appears to be the same bug as reported in this question. We'll have the fix available today. Thanks for the bug report!

We've reproduced this and implemented a fix- we'll have v3.3.3 available today to resolve this issue. Thanks for the bug report!

There are 3 possible statuses: the build status, the promotion status, and the execution status. I assume you want to get the build's execution status? If so, Builds_GetExecutions will do that (the only param you might not know to that is Execution_Count, which is just the number of executions to return, which you'd only want 1 since it orders by latest DESC).

Make sure the ExecutionStart_Date is passed in as UTC.

Glad to hear it! Thanks for letting us know.

Just an oversight. It's pretty trivial to change so we can get it in 4.5.3 today.

Have you looked at ProGet's deploy features? We switched to using those from Octopus, sooo much simpler for our configuration (no agents... plus we could just do a choco install if we needed to), and you could add w/e pshell scripts you wanted.

Panic over, ntlm authentication rather than basic authentication required.

Within a few days or so we are planning to release a new version of ProGet that has a new indexing system, which should no longer lock files like this. It will require a new feed type, but it should resolve these issues, and be much more performant than the current implementation.

I figured it out. Forgot to add ASP.NET 3.5 as a feature. DOH!

This error is coming from nuget.exe; depending on the version of nuget.exe you're using, AD / integrated authentication simply will not work. It's supposedly fixed in 2.8.2, but some users say it doesn't work in 2.8.3. It's pretty broken in 2.8.1 and 2.8.0. Although it sometimes works in 2.7. The 2.6's seem to be fine, for the most part. ProGet.exe, from the now-defunct client tools, of course will work fine, or a simple HTTP PUT operation.

Using a \ character is correct for escaping in JSON; that should work. We will try to reproduce this, but in the meantime are you able to use single quotes instead in the XML? Assembly='BuildMasterExtensions' should also parse as valid XML if I'm not mistaken.