Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release deploy returned error when using latest as input param for version #294

Open
bureku opened this issue Nov 21, 2023 · 1 comment
Open

Comments

@bureku
Copy link

bureku commented Nov 21, 2023

The bug

The command works if we explicitly specify the version, e.g. --version 1.0.0 but failed when using --version latest

Command to reproduce

octopus release deploy --space Default --project SOME_NAME --version latest --environment SOME.ENV --output-format basic --no-prompt

Outcome

 Octopus API error: Object reference not set to an instance of an object. []

Versions

cli: 1.7.1

Octopus Server: 2022.3.10594

Links

@benPearce1
Copy link
Contributor

This is intentional behaviour.

The reason behind changing it was the definition of "latest" is not clear, could mean latest by time or latest by semver definition.

If you are using this in a CI context you would probably know which version you are wanting.

The output you are seeing is actually a bug though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants