vmr main fails while building nuget-client (Only one project can be specified.)

[tmds]

Build steps:

./prep-source-build.sh
./build.sh --with-system-libs +brotli++rapidjson++zlib+ --source-only /p:OfficialBuildId=20250526.1 --online /p:PortableBuild=false

Build failure:

  MSBUILD : error MSB1008: Only one project can be specified.
      Full command line: '/home/tester/workdir/dotnet/.dotnet/sdk/10.0.100-preview.6.25272.112/MSBuild.dll -maxcpucount -verbosity:m -tlp:default=auto -v:minimal /home/tester/workdir/dotnet/src/nuget-client/eng/dotnet-build/dotnet-build.proj /bl:/home/tester/workdir/dotnet/src/nuget-client/artifacts/log/Release/Build.binlog /p:DotNetBuild=true /p:DotNetBuildSourceOnly=true /p:DotNetBuildFromVMR=true /p:Configuration=Release /p:RepoRoot=/home/tester/workdir/dotnet/src/nuget-client/ Release /p:TargetRid=fedora.41-x64 /p:DotNetBuildUseMonoRuntime=true /p:OfficialBuildId=20250526.101 /p:DotNetPackageVersionPropsPath=/home/tester/workdir/dotnet/artifacts/obj/PackageVersions/PackageVersions.nuget-client.props /p:SourceBuiltAssetsDir=/home/tester/workdir/dotnet/artifacts/assets/Release/ /p:SourceBuiltAssetManifestsDir=/home/tester/workdir/dotnet/artifacts/obj/manifests/Release/nuget-client/ /p:RepositoryName=nuget-client /p:RepositoryUrl=https://github.com/dotnet/dotnet /p:PreviouslySourceBuiltNupkgCacheDir=/home/tester/workdir/dotnet/prereqs/packages/previously-source-built/ /p:ReferencePackageNupkgCacheDir=/home/tester/workdir/dotnet/prereqs/packages/reference/ /p:TrackPrebuiltUsageReportDir=/home/tester/workdir/dotnet/artifacts/log/Release/nuget-client/ /p:TargetArchitecture=x64 /p:TargetOS=linux /p:SourceBuiltShippingPackagesDir=/home/tester/workdir/dotnet/artifacts/packages/Release/Shipping/nuget-client/ /p:SourceBuiltNonShippingPackagesDir=/home/tester/workdir/dotnet/artifacts/packages/Release/NonShipping/nuget-client/ /p:SourceBuiltPdbArtifactsDir=/home/tester/workdir/dotnet/artifacts/SymStore/Release/nuget-client/ /p:SourceBuiltNonShippingPackagesDir=/home/tester/workdir/dotnet/artifacts/packages/Release/NonShipping/nuget-client/ /p:UsingToolMicrosoftNetCompilers=false /p:PortableBuild=false /p:BaseRid=linux-x64 /p:RepoOriginalSourceRevisionId=1ad595b19f540ede0ea634ff6d0ef815c16698bf /p:GenerateResourceUsePreserializedResources=true -distributedlogger:Microsoft.DotNet.Cli.Commands.MSBuild.MSBuildLogger,/home/tester/workdir/dotnet/.dotnet/sdk/10.0.100-preview.6.25272.112/dotnet.dll*Microsoft.DotNet.Cli.Commands.MSBuild.MSBuildForwardingLogger,/home/tester/workdir/dotnet/.dotnet/sdk/10.0.100-preview.6.25272.112/dotnet.dll'
    Switches appended by response files:
  Switch: Release
  
  For switch syntax, type "MSBuild -help"
  
  'nuget-client' failed during build.

cc @ViktorHofer

[tmds]

47a07f1a14a310c26d6e19eb8f4333bc65322f4c is good, 9d86ce59f05e31b1bccb0cd5604f803416796fe4 is bad.

[tmds]

Formatting the command line:

/home/tester/workdir/dotnet/.dotnet/sdk/10.0.100-preview.6.25272.112/MSBuild.dll
-maxcpucount
-verbosity:m
-tlp:default=auto
-v:minimal
/home/tester/workdir/dotnet/src/nuget-client/eng/dotnet-build/dotnet-build.proj
/bl:/home/tester/workdir/dotnet/src/nuget-client/artifacts/log/Release/Build.binlog
/p:DotNetBuild=true
/p:DotNetBuildSourceOnly=true
/p:DotNetBuildFromVMR=true
/p:Configuration=Release
/p:RepoRoot=/home/tester/workdir/dotnet/src/nuget-client/
Release
/p:TargetRid=fedora.41-x64
/p:OfficialBuildId=20250525.101
/p:DotNetPackageVersionPropsPath=/home/tester/workdir/dotnet/artifacts/obj/PackageVersions/PackageVersions.nuget-client.props
/p:SourceBuiltAssetsDir=/home/tester/workdir/dotnet/artifacts/assets/Release/
/p:SourceBuiltAssetManifestsDir=/home/tester/workdir/dotnet/artifacts/obj/manifests/Release/nuget-client/
/p:RepositoryName=nuget-client
/p:RepositoryUrl=https://github.com/dotnet/dotnet
/p:PreviouslySourceBuiltNupkgCacheDir=/home/tester/workdir/dotnet/prereqs/packages/previously-source-built/
/p:ReferencePackageNupkgCacheDir=/home/tester/workdir/dotnet/prereqs/packages/reference/
/p:TrackPrebuiltUsageReportDir=/home/tester/workdir/dotnet/artifacts/log/Release/nuget-client/
/p:TargetArchitecture=x64
/p:TargetOS=linux
/p:SourceBuiltShippingPackagesDir=/home/tester/workdir/dotnet/artifacts/packages/Release/Shipping/nuget-client/
/p:SourceBuiltNonShippingPackagesDir=/home/tester/workdir/dotnet/artifacts/packages/Release/NonShipping/nuget-client/
/p:SourceBuiltPdbArtifactsDir=/home/tester/workdir/dotnet/artifacts/SymStore/Release/nuget-client/
/p:SourceBuiltNonShippingPackagesDir=/home/tester/workdir/dotnet/artifacts/packages/Release/NonShipping/nuget-client/
/p:UsingToolMicrosoftNetCompilers=false
/p:PortableBuild=false
/p:BaseRid=linux-x64
/p:RepoOriginalSourceRevisionId=1ad595b19f540ede0ea634ff6d0ef815c16698bf
/p:GenerateResourceUsePreserializedResources=true
-distributedlogger:Microsoft.DotNet.Cli.Commands.MSBuild.MSBuildLogger,/home/tester/workdir/dotnet/.dotnet/sdk/10.0.100-preview.6.25272.112/dotnet.dll*Microsoft.DotNet.Cli.Commands.MSBuild.MSBuildForwardingLogger,/home/tester/workdir/dotnet/.dotnet/sdk/10.0.100-preview.6.25272.112/dotnet.dll

The problem seems to be with how Release gets passed.

[ViktorHofer]

My bad. dotnet/dotnet#787 will fix this. I wonder why this doesn't show up on our own CI pipeline.

[ViktorHofer]

OK this doesn't fail for us because we are passing the -ci switch in after fromVMR and before --configuration Release:

./build.sh --ci --clean-while-building --prepareMachine -c Release --online --source-only /p:VerticalName=CentOSStream9_Online_MsftSdk_x64 /p:ArtifactsStagingDir=/__w/1/a -arch x64 /p:ReportSbrpUsage=true

So the --ci flag gets dropped in nuget-client's script parsing but that doesn't matter as it's currently also passed in as an env var to the inner repo.

Thanks for reporting @tmds. Btw, if you build the VMR in CI, you probably also want to pass the --ci switch in.

[tmds]

dotnet/dotnet#787 will fix this.

Thanks!

if you build the VMR in CI, you probably also want to pass the --ci switch in.

Relating to the discussion in dotnet/dotnet#1055. I'm not sure if I should or should not do this.

Upstream is differentiating between some build types to be able to validate different scenarios.
Is my CI use-case the same as upstream's? That is unclear to me.

Preferably, as a downstream builder, when I pass --source-build to build.sh I get a build that behaves as close to a preview/release as possible.

[ViktorHofer]

Right, source-build is special here as the E2E product (from what I understand) is built locally outside of an CI agent. So it probably makes sense to validate that scenario over building the product on an CI server. The CI switch controls the NUGET_PACKAGES cache and the VersionSuffix.