Automating packaging to nuget

[AnthonySteele]

We want packaging and uploading the api wrapper to https://nuget.org/packages/SevenDigital.Api.Wrapper/ to be a one-click operation in Teamcity.

Currently I do the following steps

• decide a new version number. e.g. last version was 2.0.2, next is 2.0.3
• put that version number in buildpackage\SevenDigital.Api.Wrapper.nuspec in the <version> tag.
• edit the "NuGet Push" step of the buildpackage.bat as it references an output .nupkg file that also contains this version number.
• run buildpackage.bat, which issues the nuget pack to generate the package and then nuget push to upload it.

Thoughts on how to automate this - ruby? Powershell? Use a version number from teamCity?

Also, the nuget commandline and the 7digital account nuget api key will need to be on the machines that run this task.

[AnthonySteele]

I have made a powershell scrip that does this https://github.com/AnthonySteele/SevenDigital.Api.Wrapper/commit/31e4b5bb744b94a0c64a62cc626cfe9e69adb9e5

Unless someone else has some better code, can we go with this?

[AnthonySteele]

This is done and working. in the buildpackage folder, the script buildPackage.ps1 does the following:

• read the last version number from lastVersion.txt
  • increment and prefix it to make the the next version number
• make a SevenDigital.Api.Wrapper.nuspec file fromSevenDigital.Api.Wrapper.nuspec.template and the version number
• nuget pack
• nuget push (NB, you will need the right nuget api key installed in order to do this)
• delete the build artefacts
• write the incremented version number back to lastVersion.txt
• git add, commit and push lastVersion.txt