Fix link to development NuGet feed

[dustinsoftware]

As a part of consolidating the CI services in #791 to use just Azure Pipelines, I missed that we are still linking to the Appveyor package server. This issue discusses bringing that functionality back.

A few possibilities

• Publish alpha packages automatically to the main nuget feed any time there is a version bump in build.proj
• Push nuget packages to appveyor's nuget feed via a custom build step from azure pipelines (docs)
• Write some custom scripts to work around the msbuild issues in Appveyor

[dustinsoftware]

I managed to get package publishing working from Azure pipelines, although it is still a manual process to promote a build. That way several commits can land into master without resulting in a package publish for each CI build.

Under Azure Pipelines > Releases, click Create Release and pick the build to be published. We still need to bump the major/minor/patch parts of the version in build.proj before creating a release. I'd like to see if Azure pipelines can detect the change in version number and automatically publish a new release, which would remove an extra step...

Eg a bump from 5.0.0-alpha5 to 5.0.0-alpha6 should automatically publish a new package.

[Daniel15]

Really cool, thanks for looking into it 😄

[dustinsoftware]

Planning on moving to the Github package registry, but ran into a few blockers:

• Package publishing appears to be rate limited. Trying to use the nuget CLI to push all packages only results in the first few succeeding. Not sure how to get past this one without putting a sleep in the build, waiting to hear back from support on this one
• My personal access token allows pushing packages to my fork, but not the reactjs repo. This is a problem because the package source is specified at build time via the projectUrl or repository element in the generated nuspec from the build. We will likely need to just wait for the beta to be more widely opened.

The Azure pipelines deploy is here and is all ready to go once the blockers are resolved.

[Daniel15]

We could try asking Github support about the rate limiting. Sent from my phone.

…

On Sun, Jun 23, 2019, 1:09 PM Dustin Masters ***@***.***> wrote: Planning on moving to the Github package registry, but ran into a few blockers: - Package publishing appears to be rate limited. Trying to use the nuget CLI to push all packages only results in the first few succeeding. Not sure how to get past this one without putting a sleep in the build, waiting to hear back from support on this one - My personal access token allows pushing packages to my fork, but not the reactjs repo. This is a problem because the package source is specified at build time via the projectUrl or repository element in the generated nuspec from the build. We will likely need to just wait for the beta to be more widely opened. The Azure pipelines deploy is here <https://dev.azure.com/reactnet/ReactJS.NET/_releaseProgress?_a=release-environment-logs&releaseId=12&environmentId=12> and is all ready to go once the blockers are resolved. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#825?email_source=notifications&email_token=AAAWOHK3KV7G43RAKHVTC2DP37J6PA5CNFSM4HTMHA4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYLGABA#issuecomment-504782852>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAWOHI64M4WO7THVR2H2VDP37J6PANCNFSM4HTMHA4A> .

[dustinsoftware]

Yep, I sent them a support email about five minutes ago :) will see what they say

[Daniel15]

Did you hear back from GitHub about the rate limiting?

[dustinsoftware]

Yeah, when publishing from azure pipelines it isn’t a problem. So now we just need the reactjs org to be enabled in the beta.

…

On Sun, Jul 21, 2019 at 01:00, Daniel Lo Nigro ***@***.***> wrote: Did you hear back from GitHub about the rate limiting? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#825?email_source=notifications&email_token=AAHGCFQ4RE3CCTSLBI2QNCDQAQJP7A5CNFSM4HTMHA4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2N6E2Y#issuecomment-513532523>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAHGCFUK3CQLFMERUUZZY5DQAQJP7ANCNFSM4HTMHA4A> .