Hi Keith, ProGet is pre-configured with a Connector to NuGet.org -- just go to Admin > Manage Feeds, and then delete the connector.

Thanks, I'll wait until the fix is released. It's not a blocking issue for me.

The discussion for this question is here: http://stackoverflow.com/questions/29254068

All dependency resolution is handled by the NuGet.exe client, here's how you do it: https://docs.nuget.org/create/versioning

I had mistakenly stopped the ProGet service after I switched to IIS hosting mode, so that caused the problem.

Answering my own question using this solution. Hope anyone else who has to do this with Ruby will find this helpful: require 'rubygems' require 'httpclient' #latest, with rubyntlm also installed http_client = HTTPClient.new http_client.set_auth(nil, '<domain>\<username>', '<password>') local_file = File.new("C:\\temp\\<package>.<version>.nupkg", "wb") local_file.write( http_client.get_content("https://<server>/nuget/<feed>/package/<package>/<version>") ) -/- flagellum

Okay, Alana, thanks for your help. We will do just that.

UPDATE: This limitation no longer exists in BuildMaster v5 (OtterScript) Plans. There is no limit to the number of executions that BuildMaster can run in parallel; however, only a single remote action can run on the same remote server/agent at a time. This means that, for example, if you create a build of multiple applications at once, and all of them build on the same build server, only one of those applications will be built at a time. You can improve this behavior by using server pools if you'd like if you have multiple build servers you would like to utilize. In exceptional cases, you could install multiple agents on the same machine (on different ports), and put those in a server pool.

I've figured out what I would like to see and its an approach I've seen other tools take. I think you need a BuildMaster plugin for Jenkins that I can add as a build step in Jenkins to: Import ReleaseNumber as a variable Trigger a BuildMaster Job and a) send selected artifacts to BuildMaster, b) set the BM build number to the Jenkins build number (I just like to keep things in sync for traceability) Workflow SVN Commit -> Jenkins Build -> BuildMaster: Import Sent Files I'd then deploy to first environment (using the BM post build step action) which would do the deployment and then call test job in Jenkins to verify deployment and/or perform regression testing. I've got most of this working using groovy scripts, but it would certainly improve things if wrapped in a plugin.

The latest release of the Jenkins plugin that fixed a bug with the url parameter encoding also fixed the authentication issues.

Thanks for the pointers, Dean!

We need to add that.. but to back-up ProGet, you just need to Back-up the Database and the Packages directory (the path is listed on each feed, and is in the All Settings under Admin). Then restore the database, and the files on a new server.

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!