Octo.exe out of date

reliability
(Colin Ferguson) #1

Using OctoDeploy and Azure Devops. I get the error
##[error]Error: The Octo command line tool is too old to run this task. Please use version 6.10.0 or newer, or downgrade the task to version 3..
##[error]Failed to push package. The Octo command line tool is too old to run this task. Please use version 6.10.0 or newer, or downgrade the task to version 3.
.

I am using the task to install Octo exe at the start of the pipeline “embedded”
when using an on premis build server (again through dev ops) I had to manually copy the .exe (which was 6.12.0) onto the server. Why is it using 6.7.0 (even though its installing it into a 6.12.0 folder structure?)

(David Young) #5

Hi Colin,

Thanks for getting in touch about this, and sorry for the inconvenience caused. We didn’t intend to embed Octo 6.7.0. We have now shipped version 4.0.385 of the extension, containing Octo 6.13.1.

If you proceed with the new version, specifying embedded in the Tools Installer task should start working again.

Please let me know if I can assist further.

Regards,
David.

(Colin Ferguson) #6

Daft Question,

Will the extension auto update on my Azure Devops or do I need ti install again?

Colin Ferguson

Computershare

BI Technical Specialist > Data, Reporting & Analytics

Skipton:


+44 3448 922596 Ext. 419
6097

Gateway House, Gargrave Road, Skipton, United Kingdom, BD23 1UD

www.computershare.com

CERTAINTY | INGENUITY

ADVANTAGE

SAVE PAPER - THINK BEFORE YOU PRINT!

(David Young) #7

Hi Colin,

Extensions normally auto-update if they were installed directly via the Marketplace. If you uploaded the .vsix file via a browser, that might need to be done again.

You can check what version is in use by editing your build pipeline and clicking the info icon next to the task title:

Regards,
David Young.