Sorry yes, I meant ProGet (though the implementations are actually the same :)) Anyway, the way that it's currently implemented does require the machine to be a part of the domain. We are aware that this is not ideal and will likely change the way LDAP is queried to make more settings configurable in a future version.

Because Chocolatey uses nuget.exe behind the scenes, you can just specify your authentication in the same manner., in the configuration file.

It's not a deployment action anymore (it used to be though). Now it's a "Post-Build Step" (which is essentially an Event Listener), and can be set on the Workflow Overview page.

Yes, http://localhost:81/bower/bower/packages/croc.webClient returns a good json: {"name":"croc.webClient","url":"http://myrepo/webclient-dist.git","hits":0}

I think I see why this is happening... it appears the extension is escaping all data in the URI (which would include the equals sign and ampersand): https://github.com/Inedo/bmx-jenkins/blob/956f738173f0cde0ffff4cdef1e6a19ae5e5de66/JenkinsClient.cs#L107 We should be able to fix this and release a new version.

Yes - that worked for me. Thank you.

As written now, that promotion requirement is a very simple text-based match - anything more complicated would require a custom predicate.

We've published the BuildMasterBeta extension v4.5 which contains a fix for this. You can install this extension from the Admin->Manage Extensions page. This fix will also be included in the next maintenance release of BuildMaster, which will be 4.6.3. Thanks for the bug report!

This could be caused by a dropped named-pipes connection between the web application and the BuildMaster service. Can you try restarting the BuildMaster service to see if that re-initiates the connection? You can also try running the service interactively to diagnose (http://inedo.com/support/kb/1015/running-the-buildmaster-services-interactively). Also, it could be a server initialization error that happens before anything gets run - make sure you're looking at the Execution Details page for errors related to that instead of the "in-progress" page.

We don't have any plans for this at this time.

Regarding the first error – that sort of thing should only happen if the connector returns invalid data. What is the URL of the bower connector? For the registration, it looks like it’s just an HTTP 401. See this article for info about Bower & authentication in ProGet: http://inedo.com/support/kb/1095/introducing-bower-support-for-proget

i will try to submit this to avira. maybe it would be nice to report it to them too since it is your product that gets blocked! this could lead to misunderstandings.

Thanks a lot! That was exactly the port that was set (and I was probably notified by the installer, but I couldn't find it afterwards)

Thanks- we'll try to expose these properties in the next release.

Do you have any connector filters? If so, try removing those to see if it works. Also, try using the non-SSL URL, i.e. http://www.nuget.org/api/v2 and see if that works. I would also double-check the proxy configuration if you have one set up. If so, see what the message when “Test Proxy Connection” is clicked.

@Tod,@Calvin I've tested it in 3.5.3 and it works now. Thanks!

I can see how to add named groups, but "Domain Users", "Everyone", "Authentication Users" don't seem to be recognized by the add users window. I think we are just going to use a large organizational group that covers most everyone so true anonymous access isn't needed anymore. Thanks!

Activation invalidates when the MachineUUID (MAC Address + CPU-ID) changes; in some virtual hosts (VM Ware), we've seen the MAC change randomly... but it's a setting that you can control.

Upgrading isn't a practical nor helpful suggestion. I guess I'll be looking elsewhere for a feed server.

Looks great. Thanks!