Closed shirhatti closed 8 years ago
:shipit:
What exactly is this for? What blob feed is this? Who consumes it?
CC @glennc
The idea is to push dnvm
to a storage account sitting behind a CDN for the new acquisition experience (get.asp.net)
When do we intend this to run? After every build of DNVM, or after Coherence-Signed passes?
@Eilon this would run after every successful build of DNVM. We do the same thing when publishing dnvm to the Home repo.
@pranavkm but these builds aren't tested. They're just the latest build no matter what. Who will consume these?
This is the same as it is today for the home repo. We push to the home repo after every build and if you run dnvm upgrade-self you get the latest dnvm.
Putting them on blob storage does give us the potential to change this and have dnvm be in channels the same a the runtimes/installers are. But right now this is an exact copy of what we have right now, but using blob storage instead of github as a vehicle.
I am fine with changing this to push to /dev/dnvm.sh so that we can make channels first class for dnvm as well.
Hmm I guess I'm just wondering what the long term plan is for this.
Upload to blob storage by setting DNVM_DEPLOY_CONTAINER to the desired Azure Blob storage container with Shared Access Signature