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

octo.exe fails with The 'versionRange' parameter was not a valid NuGet version-range when specifying the --channel=Default argument #2160

Closed
michaelnoonan opened this issue Nov 19, 2015 · 4 comments
Assignees
Labels
kind/bug This issue represents a verified problem we are committed to solving
Milestone

Comments

@michaelnoonan
Copy link
Contributor

I've been able to work around this by omitting the --channel=Default argument.

Source: http://help.octopusdeploy.com/discussions/problems/42449-unable-to-create-release-using-a-specific-channel

@michaelnoonan michaelnoonan added the kind/bug This issue represents a verified problem we are committed to solving label Nov 19, 2015
@michaelnoonan michaelnoonan self-assigned this Nov 19, 2015
@octoreleasebot octoreleasebot added this to the 3.2.4 milestone Nov 19, 2015
@octoreleasebot
Copy link

Release Note: octo.exe no longer fails when specifying the --channel argument for a Channel that has any Version Rules with a blank/empty Version Range.

@JarrodJ83
Copy link

Just an FYI, Octo.exe Documentation is missing the --channel arguement:

http://docs.octopusdeploy.com/display/OD/Creating+releases

@michaelnoonan
Copy link
Contributor Author

Thanks @JarrodJ83. I updated those docs just yesterday - thanks for letting us know!

@lock
Copy link

lock bot commented Nov 26, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 26, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

No branches or pull requests

3 participants