Open millerjn21 opened 2 years ago
This error happens because the version isn't a valid Maven version. See Octopus documentation and Maven documentation .
However, the error message is too abstract to guide the customer to understand the issue properly. In addressing this issue, we need to work on providing more relevant error message to help the customer use the correct Maven format.
Release Note: In addition to SemVer, package retention now also supports other version formats.
This issue is still occurring.
:tada: The fix for this issue has been released in:
Release stream | Release |
---|---|
2022.2 | 2022.2.8476 |
2022.3 | 2022.3.10655 |
2022.4 | 2022.4.5165 |
Team
Severity
1 reported
Version
2022.3.349-hotfix.1272
Latest Version
I could reproduce the problem in the latest build
What happened?
Using a maven package with a version that starts with a letter will fail with Value cannot be null. (Parameter 'version').
For example com.octopus:blah v2022.1.1 works com.octopus:blah vDEV-2022 does not work
Reproduction
Error and Stacktrace
More Information
Source ticket (INTERNAL): https://octopus.zendesk.com/agent/tickets/91115 Cloud reproduction (INTERNAL): https://octopus-operations.octopus.app/app#/Spaces-83/projects/maven-version-starts-with-letter/deployments
This worked locally on 2021.1.2584 and the user who reported it had last succesfully deployed to it in May, when I believe they were on a 2022.2 version.
Workaround
Use a package version that starts with a number.