Octopack and SimVer

Legacy Uncategorised
1

Is OctoPack enforcing SimVer 3 part names? E.g., MAJOR.MINOR.PATCH We use a fourth digit for offcycle efixes, that used to work, and now suddently OctoPack is generating packages with a similar name to the one we are attempting to build, but not failing, or telling me that it’s changing the package name.

Command executed

"C:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe" /m /p:RunOctoPack=true /p:OctoPackEnforceAddingFiles=true /p:OctoPackPackageVersion=1.0.0.0-build12 /p:OctoPackPublishPackageToHttp=http://octo/nuget/packages /p:OctoPackPublishApiKey=API-APIKEY.....APIKEY  /p:OctoPackReleaseNotesFile=n01sr3v.txt FaceBookTargeting.Web.sln

OctoPack Output

         OctoPack: Attempting to build package from 'FaceBookTargeting.Web.nuspec'.
         OctoPack: Setting version to 1.0.0-build12
         OctoPack: Successfully created package 'D:\Program Files (x86)\Jenkins\workspace\MA-FacebookTargeting-OctoDeploy\FaceBookTargeting.Web\obj\octopacked\Match.FacebookTargeting.1.0.0-build12.nupkg'.
         OctoPack: Copy file: D:\Program Files (x86)\Jenkins\workspace\MA-FacebookTargeting-OctoDeploy\FaceBookTargeting.Web\obj\octopacked\Match.FacebookTargeting.1.0.0-build12.nupkg
         OctoPack: OctoPack successful
         Publish to repository: http://octo/nuget/packages
         "D:\Program Files (x86)\Jenkins\workspace\MA-FacebookTargeting-OctoDeploy\packages\OctoPack.3.4.2\tools\NuGet.exe" push "D:\Program Files (x86)\Jenkins\workspace\MA-FacebookTargeting-OctoDeploy\FaceBookTargeting.Web\obj\octopacked\Match.FacebookTargeting.1.0.0-build12.nupkg" API-API-APIKEY.....APIKEY -Source http://octo/nuget/packages 
         Pushing Match.FacebookTargeting.1.0.0-build12.nupkg to 'http://octo/nuget/packages'...
           PUT http://octo/nuget/packages/
           Created http://octo/nuget/packages/ 1545ms
         Your package was pushed.
2

Hi Casey,

OctoPack uses NuGet.exe internally, and recent versions of NuGet truncate the 4th part of the version if it is zero. e.g. 1.0.0.0 -> 1.0.0 (see this issue).

We realize this is undesirable in many situations, and we plan to resolve this.

You can watch the issue above to follow our progress.

We apologize for any inconvenience.

Regards,
Michael

3

Thank you for the quick, and detailed, explanation.