CODEWITHSUNDEEP
nugetteamcityazure-worker-rolesoctopus-deploy
Андрій Назарук
Андрій Назарук

Reputation: 3

After creation NuGet package from package.nuspec issue with name of .nupkg

NuGet command: 

E:\plugins\nuget-agent\bin\JetBrains.TeamCity.NuGetRunner.exe
E:\tools\NuGet.CommandLine.DEFAULT\tools\NuGet.exe pack
E:\work\341fd6e3e508cc03\ETL\FgCloudServiceHost\package.nuspec -OutputDirectory
E:\work\341fd6e3e508cc03\ETL\FgCloudService\obj\octopacked -Version 17.02.18.1914-development -Properties Configuration=Release

and I have got

Successfully created package 'E:\work\341fd6e3e508cc03\ETL\JmineopsCloudService\obj\octopacked\fg.17.2.18.1914-development.nupkg'.

pay attention please on 17.02.18.1914-..... -Version 17.02.18.1914-development -Properties Configuration=Release but after creation 17.2.18.1914-.... where is 0 ?

Upvotes: 0

Views: 116

Answers (1)

Daniel Brixen
Daniel Brixen

Reputation: 1663

The version numbers used by NuGet follows Semantic Versioning. The 'SemVer' specification includes the following:

A normal version number MUST take the form X.Y.Z where X, Y, and Z are non-negative integers, and MUST NOT contain leading zeroes.

So in other words the version number 17.02.18.1914-development is normalized by NuGet.exe to 17.2.18.1914-development (stripping the leading zero).

You have 'octopacked' (from OctoPack) in the path, so perhaps you would be interested in seeing a reply to a similar question in the Octopus Deploy support system.

Upvotes: 1

Related Questions