Skip to content

Consolidate publishing builds to Azure #117891

@joaomoreno

Description

@joaomoreno

Until very recently, each build job was directly publishing builds to Azure Storage and CosmosDB. Recently, we made build jobs publish builds as build artifacts, such that it's straightforward for further jobs to download them and use them (ie test build jobs).

We could further:

  • Move all publishing to the Release job. It can simply download the builds as artifacts and upload them to Azure Storage and Mooncake and update CosmosDB. With this we can shave some seconds off each platform agent, since they wouldn't reach out to Azure Storage or CosmosDB.
  • Remove all CosmosDB stored procedures in use. They were introduced due to issues surrounding concurrent writes to CosmosDB from multiple clients. Since we'd have a single client, this would be straightforward.

cc @lszomoru

Metadata

Metadata

Labels

engineeringVS Code - Build / issue tracking / etc.insiders-releasedPatch has been released in VS Code Insiders

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions