Migrate from Build Artifacts to Pipeline Artifacts
- Is this issue blocking (yes/no): no
- Is this issue causing unreasonable pain (yes/no): no
This has been making a lot of noise, filing this issue to track for Arcade. I have https://github.com/dotnet/runtime/issues/1719 open to do some work on low hanging fruit in dotnet/runtime.
@markwilkie @mmitche
Thanks @dagood - we're trying to get an understanding of if we are aven able to. More soon, and thanks for opening this issue.
For sure, opened this issue to have a place to track/discuss issues and motivations for Arcade migration.
Given the fact that a) we're not at feature parity, b) there are no plans for azdo to be at feature parity, and c) we're moving to gh actions, am closing.
As we're not moving to gh actions any time soon and we still use Build Artifacts instead of Pipeline Artifacts for uploading assets as part of publishing, I'm re-opening this issue.