OctoPack SemVer issue

Legacy Uncategorised
1

Octopus Deploy 3.4.1
TeamCity Octopus Deploy integration plugin 3.4.2

We are using the following convention for versioning:
MAJOR.MINOR.PATCH+REPOSITORY_CHANGESET.BUILD_COUNTER

According to the spec this is valid, but we are receiving an OctoPack error:

[17:22:20][CreateOctoPackPackage] error OCTONUGET: '3.3.2+739.31' is not a valid version string.
[17:22:20][CreateOctoPackPackage] error OCTONUGET: Parameter name: version
[17:22:20][CreateOctoPackPackage] error OCT-1676060969: There was an error calling NuGet. Please see the output above for more details. Command line: 'E:\data\teamcity\BuildAgent\work\packages\OctoPack.3.0.60\tools\NuGet.exe' pack "E:\data\teamcity\BuildAgent\work\ed883c60d88ec7e0\src\MMG.Screeners.MMGDEMO.UI\obj\octopacking\MMG.Screeners.MMGDEMO.UI.nuspec"  -NoPackageAnalysis -BasePath "E:\data\teamcity\BuildAgent\work\ed883c60d88ec7e0\src\MMG.Screeners.MMGDEMO.UI" -OutputDirectory "E:\data\teamcity\BuildAgent\work\ed883c60d88ec7e0\src\MMG.Screeners.MMGDEMO.UI\obj\octopacked" -Version 3.3.2+739.31
[17:22:20]
[CreateOctoPackPackage] error OCT-1676060969: System.Exception: There was an error calling NuGet. Please see the output above for more details. Command line: 'E:\data\teamcity\BuildAgent\work\packages\OctoPack.3.0.60\tools\NuGet.exe' pack "E:\data\teamcity\BuildAgent\work\ed883c60d88ec7e0\src\MMG.Screeners.MMGDEMO.UI\obj\octopacking\MMG.Screeners.MMGDEMO.UI.nuspec"  -NoPackageAnalysis -BasePath "E:\data\teamcity\BuildAgent\work\ed883c60d88ec7e0\src\MMG.Screeners.MMGDEMO.UI" -OutputDirectory "E:\data\teamcity\BuildAgent\work\ed883c60d88ec7e0\src\MMG.Screeners.MMGDEMO.UI\obj\octopacked" -Version 3.3.2+739.31
   at OctoPack.Tasks.CreateOctoPackPackage.RunNuGet(String specFilePath, String octopacking, String octopacked, String projectDirectory) in y:\work\1f6ae101e1fcba62\source\OctoPack.Tasks\CreateOctoPackPackage.cs:line 588
   at OctoPack.Tasks.CreateOctoPackPackage.Execute() in y:\work\1f6ae101e1fcba62\source\OctoPack.Tasks\CreateOctoPackPackage.cs:line 194
2

Hi,

You are correct, that is a valid version, and should be allowed.

The problem is actually in NuGet.exe, which is bundled with OctoPack.
However, we forked NuGet.exe in order to unlock SemVer 2.0.0 versions, so we are in a position to resolve this issue (and hopefully submit a PR back to the NuGet team).

I have created an issue which you can follow. We will resolve it as soon as possible.

We apologize for any inconvenience.

Regards,
Michael

3

Notice:

This issue has been closed due to inactivity. If you encounter the same or a similar issue and require help, please open a new discussion (if we asked for logs or extra details in this thread, consider including them in the new thread). If you are the creator of this thread and believe it should not be closed let us know via our support email.