Case solved. It seems I incorrectly assumed that passing content-type
application/json and json encoded repository information will work.
Anyway, once I passed url encoded repository it worked flawlessy (well
it does read that payload needs to be multi-part form data in the
documentation).
--
After upgrading to 1.5.5 I still have problems adding repositories
remotely. The request body is as follows (content-type is set to
application/json):
{path: http://10.10.16.117/scm/git/wifi.git;, tool: Git, name: wifi}
While the response is 400 Bad Request with data:
{fields: {path: [This field
What version are you using, and are you logged into the API as an
administrator?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Jul 13, 2011 at 9:54 AM, maciek borzecki
maciek.borze...@gmail.comwrote:
Uhh, my bad. I'm using 1.5, just noticed that adding repositories
through web API came in 1.5.4.
--
Maciek Borzecki
On Wed, Jul 13, 2011 at 8:10 PM, Christian Hammond chip...@chipx86.com wrote:
What version are you using, and are you logged into the API as an
administrator?
Christian
--
