Eric, thank you! That was the issue, I didn't know about that issue.

It's certainly possible in BuildMaster, but it's not a common workflow anymore. We have considered extending support, but the market generally is moving towards "many single-purpose tools" than "multi-function tools". The general flow these days looks like this: Source >> CI >> Package >> Deploy In this case, ProGet is the Package repository and BuildMaster is the deploy tool. The advantage to this workflow is that, the CI tool need only "create a validated package", instead of trying to deploy. By the way, I also recommend you to look at GitLab; we switched to it after extensive evaluations of similar "simple" tools (GitHub, BitBucket), as well as the enteprrise tools (Perforce, etc).

See: http://inedo.com/support/tutorials/performing-a-deployment-rollback-with-buildmaster

Sorry - I did mean .org in my previous response :) Still however, I am not able to reproduce this behavior that sets the Remote Repository to something other than what was typed in unless I edit an existing repository and do not save the edited values. If you could detail the exact steps you did (e.g. 1. Click Create New Provider button, 2. Input values abc and xyz, 3. click Test Connection, etc.) that would help tremendously.

Issue tracking would require a custom extension. It's a pretty simple web api, and if you'd be interested at taking a crack at it, we could help you build the extension (and support it going forward).