Deployment with Octopus Deploy failing globally.

aaronmcintosh's Avatar

aaronmcintosh

02 Dec, 2024 09:43 AM

Over the weekend, all of our AppVeyor builds suddenly stopped working.

Since we don’t perform development activities over the weekend—aside from some QA work—nothing has changed on our end that would affect every project globally.

The error we’re seeing is:
"Command executed with exception: The term 'octo' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again."

For context, we use the custom packaging build arguments as outlined in the documentation:
https://www.appveyor.com/docs/deployment/octopus-deploy/

Given the rollback required on your side last week, could this issue be related? Is there any potential impact on Octopus Deploy integrations?

  1. Support Staff 1 Posted by Owen McDonnell on 02 Dec, 2024 06:46 PM

    Owen McDonnell's Avatar

    Yes, it's related.
    The old octo CLI is deprecated so we're working on transitioning gracefully.
    It should be working now, but if not let us know,

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac