Build artifacts not available in Azure Pipeline

[dantler]

It is nice that you have your Azure Pipeline visible, but it would be even nicer to be able to download build artifacts.

Bounty: I will post one smiley face emoji upon completion of this task.

[enricogior]

Hi @dantler
we decided not to publish the artifacts in order to avoid confusion in this early stage of the project.
As you might have seen, we have several issues we need to fix and it's better to have one specific release that all users are using to simplify the error reporting.
So for now we prefer to avoid publishing the artifact but we will reconsider this when we reach a more stable code base.
Does that sound like a plan?
Thank you.

[dantler]

Hi @enricogior , I did see, and agree you are making the right decision. The smiley face will have to wait.

[crutkas]

lets get this hooked up as we are doing a lot of more harder merges and would be good to validate. I do want the file name / Build # to be tracked back to a CI build w/ maybe the hash. I would also have it be 0.0.Date or something, i don't want it confused with a real build.

[crutkas]

If we do a CI where public can grab the bits, it may have to be signed. I don't think the CI currently will enable that.

[crutkas]

I don't think we'll be doing this off CI builds. We've seen a hard enough time trying to get version #'s and support for mainstream builds, i don't think we'll want this for CI builds. I'd rather setup a proper nightly style that can be force updated. And anything we ship from any channel, should be signed by MSFT which means our proper pipeline