Open riarenas opened 7 months ago
during our "deep dive" meeting, the 1ES team seemed surprised logging commands existed and were unsure whether they could intercept them (somehow). do we know if they're working on something here❔
today's ##vso[artifact.upload]
commands enable easy flattening of a folder tree. we use this feature in PushToBuildStorage
for the AssetManifests
, BlobArtifacts
, and PackageArtifacts
artefacts. we explicitly do not flatten the tree when creating the PdbArtifacts
artifact. need a replacement approach which supports both choices.
separately, this logging command creates or updates a build artefact. I seem to remember it also does retries under the covers and avoids scaling problems. we'll need to stress test a replacement to ensure we don't regress our reliability.
cc @tkapin
Moving this to dotnet/dnceng so we can put it in an epic.
Move makes even more sense now that I've noticed some of our code e.g. in dotnet-helix-machines
(see VstsBuildContextLogger in particular) also uses ##vso[artifact.upload ...]
logging commands.
Also see chat from the "Publishing Artifacts Alternatives" meeting.
Currently, the publishing infrastructure in the Arcade SDK uses the Artifact upload logging commands to publish intermediate artifacts to the
PackageArtifacts
andBlobArtifacts
containers.https://github.com/search?q=repo%3Adotnet%2Farcade+artifact.upload&type=code
Artifacts uploaded via this mechanism skip the scans that the 1ES pipeline templates enforce on each artifact upload.
We should look into alternatives that allow the 1ES templates to scan the artifacts the Arcade SDK produces