Octo.exe project name with spaces

Integration
1

Running octo deploy-release --project "Test Website 2018" (with a few more options) throws an error;
“Unrecognized command arguments: Website, 2018”

From what I can see the error is generated when using a project name containing spaces. I’m running octo.exe via docker image.

I’ve tried:

  • –project “Test Website 2018”
  • –project=“Test Website 2018”
  • “–project=Test Website 2018”
  • “–project Test Website 2018”

I must have missed something!

2

Hi Mike,

We had another customer report the same issue (although not running in a docker image) and the cause was that they were using the generic .NET Core package of octo.exe instead of the specific package for the Linux distribution.

image
image.png531×653 30 KB

Can I ask which package you downloaded, it could be that you need to download the package specific to the Linux distribution your docker image is running.

Thank you and best regards,
Henrik

3

Hi @henrik!

It was following the example from the docs… https://octopus.com/docs/api-and-integration/bitbucket-pipelines

Its just using the image, “octopusdeploy/octo:4.37.0-alpine” so no download.

4

Hi Mike,

Thanks for the extra information, that image uses our portable package which (for some reason) has issues with spaces in argument values, it’s not escaping the values correctly.

I will investigate and see if we can either update our Docker image to use the appropriate package or if we can fix the portable package so it can handle spaces in argument values.

My sincere apologies for the inconvenience caused by this issue.

Thank you and best regards,
Henrik

5

Hi again Mike,

I’ve been doing some investigation into this issue and I think it has something to do with character escaping in the .yaml file that is causing this issue as running the same Docker image locally on my Windows machine (and also a MacOS machine) works with project names that have spaces in them.

I’ve raised this GitHub issue that you can watch for updates on the progression of our investigation into this issue.

Again, my sincere apologies for the inconvenience caused by this issue.

Thank you and best regards,
Henrik

6

Thanks @henrik really appreciate the time you have taken with this. :slight_smile:

I’ll keep an eye on the GitHub issue. Thanks again!

7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.