We actually aren't familiar with that particular tool. We do have Axosoft OnTime integration, so if the API is the same, then it should already work :) If not however, issue tracking integration is extensible, and can be developed by your team or by us as part of extended support. Does this help?

Which aspect of insecurity are you referring to? Those credentials (as long as they are sent over SSL) are encrypted before they are transmitted. If you mean storing them in the BuildMaster database, of course that does leave them available to anyone who has access to them, but you can configure permissions to hide debug logs and access to the configuration for that provider. Anyway, you should configure your git client to use key-based authentication if the username/password combo can't be done.

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!

Are you sure you're on v4.5.5? This should have been fixed in that version (BM-1685)... it can only happen if you don't have any deployables set up for an application.

That should be all that's necessary, perhaps restarting the server where ODAC is installed might help?

There's supposed to be a [...] button next to that text box that allows you to browse to the path in source control, but there was a small bug that prevented its display. We have just released a new version of the Windows SDK extension; if you update that within BuildMaster, then that [...] button will return and you will be able to select the path.

Re: WARN: Error initializing server .NET 4.5 (ID: 11): System.Net.Sockets.SocketException A SocketException is thrown by the Socket and Dns classes when an error occurs with the network. Most of the time these are connectivity issues due to different IP protocols (IPV4/IPV6) between the two server/computers trying to communicate or extra authentication rules setup on one of the computers for in/out connectivity. Ways to troubleshoot the issue are, check you have proper internet connection is there on your machine or not, and you are able to ping the remote server or not. Possible causes for the error: You are using the wrong IP address. You are using the wrong port. Firewall blocking the connection.

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.

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

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.

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.

These days, the general workflow has really evolved to assembling artifacts into "packages" and then pushing to a package manager; basically Build > Package > Deploy I think the reason is that it's much easier to deploy known packages (then assemble them from artifacts). In this case, ProGet serves as the Package manager step.

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

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

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.

Panic over, ntlm authentication rather than basic authentication required.

The fake step is the way to go here since you can't force past the "deployables with dependencies" warning anyway. The only reason it's there is because it is almost certainly an error to build against a specific dependency (such as an SDK) and then release the dependent software using the SDK, but then do another build of the same release of said SDK which could break compatibility.

Never mind, I discovered that I just need to append '&variable=value' to url