Why does execute-sdl.yml download all artifacts? Fails in Core-Setup due to disk space

https://github.com/dotnet/arcade/blob/ab99af9da2605b56f8720278a889bb0d2d711645/eng/common/templates/job/execute-sdl.yml#L21-L27

Why does this download everything, rather than the set of “final” artifacts Arcade uses in other situations? (PackageArtifacts/BlobArtifacts?)

The above along with the (I think relatively small) hosted agent that’s it’s hard-coded to use causes failures for Core-Setup:

https://github.com/dotnet/arcade/blob/ab99af9da2605b56f8720278a889bb0d2d711645/eng/common/templates/job/execute-sdl.yml#L16-L17

Core-Setup publishes a lot of artifacts to the pipeline that aren’t signed yet and/or won’t be published, so that other stages in the pipeline can work with them. This creates a large enough download that the SDL job fails due to lack of disk space in this prototype build:

https://dev.azure.com/dnceng/internal/_build/results?buildId=402553

@sunandabalu @dotnet/dnceng

[michellemcdaniel]

Sure thing

[sunandabalu]

I don’t see why not, @adiaaida could you send out a PR to merge this in 3.x branch for approval?