This appears to be a bug with the ProxyRequest property, i.e. if it's true (the default), the response variable is not set. The tracking issue for this is here: https://github.com/Inedo/inedox-inedocore/issues/91

Thanks for the suggestion. We've filed this as PG-1412 for inclusion in a future maintenance release.

Ben, That works. Thank you! TLDR; don't use "MultipartFormDataContent" when making this request.

This has been on the list for a little while, but I finally made a github issue for it. We'll get it soon! https://github.com/Inedo/inedox-inedocore/issues/22

That particular error message is a result of the connection string missing from the configuration file. Please ensure there is a key present in both web.config and in ProGet.Service.exe.config. Most likely, someone had inadvertantly deleted it from the configuration file when attempting to configure the server in IIS. <add key="InedoLib.DbConnectionString" value="Data Source=...;Initial Catalog=ProGet;Integrated Security=SSPI" />

Finally got it working, turns out a single quote at the start and end of TextData is enough for the configs to be fully included without error, while still accepting BuildMaster parameters, Here's the code in case there is a desire to implement Job creation in the Jenkins extension, (anonymized a little): Post-Http http://Jenkins:8080/job/TestNewAPIJob/config.xml ( ContentType: application/xml, TextData: '<?xml version="1.0" encoding="UTF-8"?><project> </project>', LogRequestData: true, LogResponseBody: true, RequestHeaders: %(Authorization: Basic xyz123) ); Thanks for the help getting this going, this was my first time using 5.3 from 4.7, little learning curve with the new Plan editor that is really cool! -Dan

This action has been updated in 4.6.4, which is now available. We've added a more friendly editor for form data and some better documentation in the action. The UI will probably still be refined in a future release, but it should be more intuitive now.

I just installed v 3.4.6 Build 6 and it is now working. I used SQL Express installer this time instead of connecting to a stand alone sql server. Not sure if that made any difference.

ProGet does not support being installed in a virtual directory; it must be at the site root.