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

ensure packaging work is completed

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2.4.0
    • Component/s: None
    • Labels:
      None

      Description

      Problem is that Appveyor isn't picking up the hook on tags from github.  Need to ensure that we at least do the right thing for release, if not fix the automation.

        Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

          Hide
          mike.goldsmith Michael Goldsmith added a comment -

          Any further work can have additional tickets raised.

          Show
          mike.goldsmith Michael Goldsmith added a comment - Any further work can have additional tickets raised.
          Hide
          mike.goldsmith Michael Goldsmith added a comment -

          The work I've already completed will generate the zip file ready to push to S3 for each commit with the push to S3 expected to only be triggered for repository tags. The build version would be something like 2.4.1.1234 where the last point is the AppVeyor build number.

          Show
          mike.goldsmith Michael Goldsmith added a comment - The work I've already completed will generate the zip file ready to push to S3 for each commit with the push to S3 expected to only be triggered for repository tags. The build version would be something like 2.4.1.1234 where the last point is the AppVeyor build number.
          Hide
          ingenthr Matt Ingenthron added a comment -

          Related to this, we used to, and can again, publish snapshots to S3 for every successful build of some SDKs.  This is most often helpful when you want to give a VF to a customer or post something to the forums for someone to try.  Just food for thought-- if you want to get this going, we can get with IT.

          Show
          ingenthr Matt Ingenthron added a comment - Related to this, we used to, and can again, publish snapshots to S3 for every successful build of some SDKs.  This is most often helpful when you want to give a VF to a customer or post something to the forums for someone to try.  Just food for thought-- if you want to get this going, we can get with IT.
          Hide
          mike.goldsmith Michael Goldsmith added a comment -

          I think there may be some tweaking but I should be able to create a PR on GitHub to trigger the builds and verify. A subsequent ticket may follow to apply any changes. We can either push this ticket to 2.4.1 or raise another ticket if we need another commit.

          Show
          mike.goldsmith Michael Goldsmith added a comment - I think there may be some tweaking but I should be able to create a PR on GitHub to trigger the builds and verify. A subsequent ticket may follow to apply any changes. We can either push this ticket to 2.4.1 or raise another ticket if we need another commit.
          Hide
          jmorris Jeff Morris added a comment -

          Can this be closed?

          Show
          jmorris Jeff Morris added a comment - Can this be closed?
          Hide
          mike.goldsmith Michael Goldsmith added a comment -

          I think once the outstanding commits have been reviewed and merged, we should be able to tag the repo and both the nuget package and zip folder will be created. Hard to test end-to-end without actually tagging the repo, which we could trial with a dummy tag and remove afterwards.

          Note: no automatic deployment of the nuget package or zip file are enabled right now. We can turn that on once we're happy with the output.

          Show
          mike.goldsmith Michael Goldsmith added a comment - I think once the outstanding commits have been reviewed and merged, we should be able to tag the repo and both the nuget package and zip folder will be created. Hard to test end-to-end without actually tagging the repo, which we could trial with a dummy tag and remove afterwards. Note: no automatic deployment of the nuget package or zip file are enabled right now. We can turn that on once we're happy with the output.
          Hide
          mike.goldsmith Michael Goldsmith added a comment -

          With Brett's help I was able to find out that the AppVeyor WebHooks had not been created correctly. Probably because I am not an Admin for the repository. However neither AppVeyor nor GitHub informed informed me there was an issue so assumed it was successful.

          The WebHook has now been manually created and configured so hopefully it will trigger with the next commit.

          There will be some tidy up work as they current structure does not understand the new xproj project types that was recently added as part of the .NET Core work.

          Show
          mike.goldsmith Michael Goldsmith added a comment - With Brett's help I was able to find out that the AppVeyor WebHooks had not been created correctly. Probably because I am not an Admin for the repository. However neither AppVeyor nor GitHub informed informed me there was an issue so assumed it was successful. The WebHook has now been manually created and configured so hopefully it will trigger with the next commit. There will be some tidy up work as they current structure does not understand the new xproj project types that was recently added as part of the .NET Core work.

            People

            • Assignee:
              mike.goldsmith Michael Goldsmith
              Reporter:
              ingenthr Matt Ingenthron
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  PagerDuty

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