Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Done
-
2.3.9
-
None
Description
There are a number of steps required to build, package and deploy the .NET SDK. It's very easy to miss a step, forgetting to sign the assembly for example, while doing this manually. This ticket is for developing/automating the build, package, deploy process so that human errors do not occur impacting users of the SDK.
Attachments
Issue Links
- relates to
-
NCBC-1233 Release 2.3.9 assembly is not strongly named and does not have a publicKeyToken
-
- Resolved
-
| For Gerrit Dashboard: NCBC-1234 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 70565,3 | NCBC-1234: Develop build, package, deploy scripts for .NET SDK | master | couchbase-net-client | Status: MERGED | -1 | +1 |
Activity
There is a pattern for signing asemblies during the build process on AppVeyor here:
(http://help.appveyor.com/discussions/questions/217-signing-net-assemblies-without-exposing-the-snk-file-publicly).
Same for automatically publishing to Nuget:
https://www.appveyor.com/docs/deployment/nuget/
AppVeyor may be able to help automate some of this. I have already set this to build both the ASP.NET and Linq2Couchbase projects.
For example, when a tag is pushed to GH we could trigger a build, set assembly versions, etc and maybe even sign the assembly. I think we could even automate the push to Nuget, but I'm not 100% on that.