Investigate way of tying github releases to nuget

[gregsochanik]

Here's what I want to achieve:

• Administrator creates release / release notes on github as the starting point.
• Build on Teamcity checks out using that releases tag (based on manually changing tag ref)
• Build run in teamcity to publish nuget package with that same tag number.

In order to:

• Have a consistent and efficient package release mechanism.
• Allow an easy way for developers to track changes in github
• Give developers more info so they can make better choices about which version they can use.

Note - this is of course all open to comment. For example, should we use release notes that are tied to github? Is there a way of publishing the same release notes to nuget so we're not repeating ourselves? etc etc

[gregsochanik]

TC supports the concept of tags as branches so specific tags can be targeted Can specify current tag/release as build parameter specified as %ReleaseVersion% Can use out of the box nuget pack/publish to release to nuget

Once I've built a working prototype, I will add details accepted release instructions to the wiki

[gregsochanik]

Right, this works in principle and is very simple to use:

• I have a Team City build that pulls in a specified release version and uses the built-in Nuget Pack to create a Nuget package
• There is a Publish build that takes this package as a dependency (with the correct version number) and publishes it to public Nuget.

BUT

I have come across a couple of issues:

• We have custom parameters in our nuspec template which I have yet to find a way to add via teamcity
• Therefore, it may be preferable to use the powershell script included with the project to build the nuget package and output as an Artifact, but when I run this script within TC it does not output the file anywhere

So actions to work on:

1. Find out how to add custom properties to nuspec when building using TC Nuget Pack plugin
2. Inspect powershell script to see why it's not outputting the "dry run" nupkg

[gregsochanik]

Right, this is proving a little tricky and taking too long so am going to stop. I may come back to it, but for now I'm going to just write step by step instructions on how to release to nuget within the wiki, by

• creating the release
• locally checking out the tag with the correct version name
• using the buildpackage powershell script to publish as normal

[gregsochanik]

Instructions added here:

https://github.com/7digital/SevenDigital.Api.Wrapper/wiki/Releasing-to-nuget