Relative Path in "Custom install directory" in deploy step

I Upgraded to 3.7 last night, from 3.5.1, and my long standing deploy process no longer works. I have “Custom install directory” set to “…/deployable/src” and am now getting a new error:

The custom install directory ‘…/deployable/src’ is a relative path, please specify the path as an absolute path or a UNC path.
December 6th 2016 10:33:49Error
Running rollback conventions…
December 6th 2016 10:33:49Error
The custom install directory ‘…/deployable/src’ is a relative path, please specify the path as an absolute path or a UNC path.
December 6th 2016 10:33:50Fatal
The remote script failed with exit code 1
December 6th 2016 10:33:50Fatal
Deploy Package to Tentacle on LocalTentacle

I didn’t see anything about this in the release notes, but there’s a lot there.

Hi,

Thanks for reaching out. The Custom Installation Directory was never really meant to support relative paths. We even added that exception you got back in 3.4.1 to make sure nobody tries to use a relative path:

Github issue: https://github.com/OctopusDeploy/Issues/issues/2763
PR: https://github.com/OctopusDeploy/Calamari/commit/b4e4fd2df932ee67cb9ca83b71e1f85aafaa9877

You are trying to deploy to a path relative to which directory exactly? I’d like to help you get your deployment working in the version you are on now.

Thanks,
Dalmiro

It was just a separate place to have to do work, since after the work is done, the entire thing has to be zipped back up and uploaded to Azure via one of their APIs.

Instead, I just appropriated some space from my Azure VM’s temp drive, and voila!