Couchbase .NET client libraryIcon indicating the project type

Couchbase .NET client library

Uploaded image for project: 'Couchbase .NET client library'
  1. Couchbase .NET client library
  2. NCBC-1234

Develop build, package, deploy scripts for .NET SDK

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 2.3.9
    • Fix Version/s: 2.4.0, backlog-2.0
    • Component/s: library
    • Labels:
      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

          Bug - A problem which impairs or prevents the functions of the product. NCBC-1233 Release 2.3.9 assembly is not strongly named and does not have a publicKeyToken

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            mike.goldsmith Michael Goldsmith added a comment -

            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.

            Show
            mike.goldsmith Michael Goldsmith added a comment - 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.
            Hide
            Permalink
            mike.goldsmith Michael Goldsmith added a comment - - edited

            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).

            Show
            mike.goldsmith Michael Goldsmith added a comment - - edited 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 ).
            Hide
            Permalink
            mike.goldsmith Michael Goldsmith added a comment -

            Same for automatically publishing to Nuget:
            https://www.appveyor.com/docs/deployment/nuget/

            Show
            mike.goldsmith Michael Goldsmith added a comment - Same for automatically publishing to Nuget: https://www.appveyor.com/docs/deployment/nuget/

              People

              • Assignee:
                mike.goldsmith Michael Goldsmith
                Reporter:
                jmorris Jeff Morris
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Gerrit Reviews

                  There are no open Gerrit changes

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.