This one looks fishy:

Unable to process command ' ##vso[artifact.upload containerfolder=AssetManifests;artifactname=AssetManifests]/__w/1/s/src/aspnetcore/artifacts/log/Release/AssetManifest/Ubuntu2404_Ubuntu_BuildTests_x64.xml' successfully. Please reference documentation (http://go.microsoft.com/fwlink/?LinkId=817296)

@wtgodbe @mmitche PTAL

I'm not sure:

Writing build manifest file '/__w/1/s/src/aspnetcore/artifacts/log/Release/AssetManifest/Ubuntu2404_Ubuntu_BuildTests_x64.xml'...

And then right after, when it tries to upload it:

##[error]Path does not exist: /mnt/vss/_work/1/s/src/aspnetcore/artifacts/log/Release/AssetManifest/Ubuntu2404_Ubuntu_BuildTests_x64.xml

is __w an alias for /mnt/vss/_work?

The path on Ubuntu is displayed differently because it's running inside a container there and AzDO probably leaks the real path. I don't think that's related as the Windows jobs also fail and they don't run inside a container and the paths are all the same:

Writing build manifest file 'D:\a_work\1\s\src\aspnetcore\artifacts\log\Release\AssetManifest\Windows_x64.xml'...

##[error]Unable to process command ' ##vso[artifact.upload containerfolder=AssetManifests;artifactname=AssetManifests]D:\a_work\1\s\src\aspnetcore\artifacts\log\Release\AssetManifest\Windows_x64.xml' successfully. Please reference documentation (http://go.microsoft.com/fwlink/?LinkId=817296)

##[error]Path does not exist: D:\a_work\1\s\src\aspnetcore\artifacts\log\Release\AssetManifest\Windows_x64.xml

OK looks like this regressed with @ellahathaway's commit: dotnet/aspnetcore@92bc896

@ellahathaway I fixed this with the latest commit by only setting the properties if the args are explicitly provided. I think that's the right thing to do anyway.