Octopus 3.3

Using the Octopus Command line I am trying to run the following command, and receive the below error.

PS D:\Dev\octo33> .\Octo.exe create-release --project MCM4 --version 2.0.1 --server http://deploy/ --apiKey [redacted] --deployto CCI --progress --waitfordeployment --deploymenttimeout=00:00:30

Handshaking with Octopus server: http://deploy
Handshake successful. Octopus version: 3.3.0-beta0002; API version: 3.0.0
Authenticated as: [redacted]
Finding project: MCM4
Finding deployment process for project: MCM4
Error from Octopus server (HTTP 200): Unable to process response from server: Error reading string. Unexpected token: St
artObject. Path ‘Steps[1].Actions[1].Properties.SQLReleaseTargetPassword’, line 244, position 42… Response content: {
“Id”: “deploymentprocess-Projects-25”,
“ProjectId”: “Projects-25”,
“Steps”: [

Exit code: -7

If I run this plan (which was migrated to 2.6) manually, it works fine.

This is due to the fact that the RedGate Step Template sets Properties.SQLReleaseTargetPassword as a “Sensitive” Field.

A workaround is to set the password as a single line field, however I think this is a bug in the Octo.exe command line tool, as it can’t parse the breaking change noted here:

I’m hoping for some guidance if it isn’t the command line tool, as I believe that is the aspect failing at parse.


Thank you for bringing this to our attention.

You are correct, octo.exe is unable to parse the password field because of the noted breaking change. I have made a ticket to get this resolved: https://github.com/OctopusDeploy/Issues/issues/2397