Octopus CLI breaks in Github Actions, seemingly because https://raw.githubusercontent.com/OctopusDeploy/cli/main/releases.json doesn't contain a version field (anymore?)

[philipkaare]

Describe the bug
Octopus CLI is not able to install in GHA.

To Reproduce
Steps to reproduce the behavior:
Try to install octopus cli in GHA.

Expected behavior
It should install.

Screenshots

Desktop (please complete the following information):

• OS: Windows
• Browser Edge

Additional context
I think the problem is at: https://github.com/OctopusDeploy/install-octopus-cli-action/blob/main/src/octopus-cli.ts#L60 where the file is downloaded and parsed. It looks like a version field is expected which seems to be missing from the file.

[pvancoeverden]

We've found a workaround by downgrading the CLI action to v1.1.10 (v1.2.x breaks)

      - name: Install Octopus CLI
        uses: OctopusDeploy/install-octopus-cli-action@v1.1.10
        with:
          version: 9.1.7

Of course it would be better to upgrade to v3, but this requires more pipeline changes.

[philipkaare]

Our workaround was to switch to OctopusDeploy/create-nuget-package-action@v3

[Clare-Octopus]

Good afternoon all,

I work at Octopus Support and am sorry you are seeing issues with one of our GitHub Actions steps. Thank you for posting this GitHub issue up and for letting other customers know there is a workaround available.

I have sent this to our engineers, who will take a look at this, and hopefully, we can try and get it rectified. We did have a recent certificate changeover for our https://g.octopushq.com/ website where the CLI lives. Which did affect some customer's build pipelines when trying to use older create release steps as those try and go to our website to download the CLI version for that step. The error message for that is slightly different but I am unsure where we go to get the CLI for GitHub actions so this may be related.

We have seen success with most customers for re-trying their pipeline and that seems to have fixed the issue but I imagine most people on here would have done that already before downgrading.

Hopefully we can get this resolved for you all soon.

Kind Regards,
Clare

Engineers discussion (internal) - https://octopusdeploy.slack.com/archives/CNHBHV2BX/p1709211764189129

[Clare-Octopus]

We have done a bit of initial digging around this, and it looks like GitHub had a recent outage with webhooks and actions, which may be related to this issue as it looks like our GitHub Actions step grabs the CLI from GitHub itself (https://github.com/OctopusDeploy/cli/releases), not our website (https://g.octopushq.com/).

https://www.githubstatus.com/incidents/5lc3f39mjcq8

It looks like Github had a slight outage for actions -

We're seeing issues related to background jobs, which are causing delays for webhook delivery and search indexing, and other updates.

The issue looks to be resolved now so if anyone has the time to try and upgrade again back to their previous version to see if this has been resolved that would be appreciated.

Kind Regards,
Clare

[kbrouder7]

@Clare-Octopus - We are still seeing the issue over here, it started with a certificate expired error, but now getting the unable to get versions error:

Error: ✕ Unable to get versions...
Error: Error: ✕ Unable to get versions...

This is happening targeting v1.2.1

[mlapaglia]

anything? still seeing errors.

[castiel-ho-cko]

For fellow v1.x users, we managed to use the workaround by @pvancoeverden of downgrading to v1.1.10 and unblock our pipelines.

It's worth noting that if version: latest is provided, this version of the action will only resolve CLI version to 7.4.3663; instead you can provide version: 9.1.7 directly and it will install the CLI successfully

[Clare-Octopus]

It does look like this is not down to the GitHub downtime issues, so I have communicated that to our engineers, and they will take a look at version v1.2.x of the step and see if they can work out why this is happening.

In the meantime one of our users via email reported 3.x versions do work so if you are able to upgrade that would be a better option than to downgrade but we do realise that may take some extra work to get v3.x working with your pipelines so in that case a downgrade would be your only options here.

Our engineers will hopefully update this issue once they have had a chance to take a look at it; they are based in Sunny, Australia, so they work in AUS time zones.

If you are really struggling with this, please don't hesitate to email us at support@octopus.com as long as you have a valid paid or trial license with us, and we will do our best to help.

Kind Regards,
Clare

[mlapaglia]

For fellow v1.x users, we managed to use the workaround by @pvancoeverden of downgrading to v1.1.10 and unblock our pipelines.

It's worth noting that if version: latest is provided, this version of the action will only resolve CLI version to 7.4.3663; instead you can provide version: 9.1.7 directly and it will install the CLI successfully

thank you that fixed it for us.

[mfalconi-perle]

We have done a bit of initial digging around this, and it looks like GitHub had a recent outage with webhooks and actions, which may be related to this issue as it looks like our GitHub Actions step grabs the CLI from GitHub itself (https://github.com/OctopusDeploy/cli/releases), not our website (https://g.octopushq.com/).

https://www.githubstatus.com/incidents/5lc3f39mjcq8

It looks like Github had a slight outage for actions -

We're seeing issues related to background jobs, which are causing delays for webhook delivery and search indexing, and other updates.

The issue looks to be resolved now so if anyone has the time to try and upgrade again back to their previous version to see if this has been resolved that would be appreciated.

Kind Regards, Clare

Not resolved. Currently 4 hrs after github outage has been fixed and I still get errors on every run.

[Clare-Octopus]

Hey @mfalconi-perle I posted an updated comment on this issue (which is my last comment before this one) and noted this is probably not down to the GitHub downtime issue. We will update you when our engineers have had a chance to look into this.

Kind Regards,
Clare

[mfalconi-perle]

@Clare-Octopus yeah I saw after just wanted to note it was still occurring. thx. Best of luck with the fix!

[paraicoceallaigh]

Hi all, Octopus support here..we have marked this one successfully resolved. RCA: As part of a migration of our backend redirect tooling the DNS redirects used by the GH action broke due to a misconfiguration in the new redirect tooling. We have fixed and tested this. Retrying now should get you unstuck. Apologies for the inconvenience folks.

[mfalconi-perle]

@paraicoceallaigh Hi thanks for resolving the issue. Going forward, if possible does it make more sense to upgrade to the newer V3 version? if the rest of my pipeline with octopus is using @V3 actions i assume there should be minimal changes to use the newer cli actions. TY

[Clare-Octopus]

@mfalconi-perle We would always recommend customers upgrade to our latest versions of plugins and software to take advantage of feature updates and security patches but not all customers are able to upgrade straight away and each will need to checkout our comparison tools we offer and note any breaking changes between versions to ensure the new version is compatible with your own project setups, infrastructure and integrations.

For this specific GitHub actions step (Install the Octopus CLI) we have this page which links the changes between versions, hope this helps!

https://github.com/OctopusDeploy/install-octopus-cli-action/blob/v3.1.1/migration-guide.md

Because V1 and V3 are so different we did make a blog post on the changes which includes other steps so I would take a look at that as that contains a lot more information than the migration guide:

https://octopus.com/blog/github-actions-for-octopus-deploy-v3

Reach out at support@octopus.com if you hold a paid or valid trail license if you have any questions as we can do our best to help answer them but this GitHub issue will no longer be monitored by Octopus official support members as it is now closed.

Kind Regards,
Clare