push-common-updates pipeline failing with `BUILD_BUILDNUMBER` error

[mthalman]

##[error]TF209010: The build number format $env:BUILD_BUILDNUMBER (Dry run)\"\n        Write-Host \"##vso[build.addbuildtag]dry-run\"\n        \n        if (\"$(officialBranches)\".Split(',').Contains(\"$(Build.SourceBranch)\"))\n        {\n          Write-Host \"##vso[task.logissue type=error]Cannot run a CG dry-run build from an official branch ($(officialBranches)).\"\n          Write-Host \"##vso[task.logissue type=error]Run the pipeline again from a different branch to avoid registering scan results.\"\n          exit 1\n        }\n      displayName: Update Build Number\n    - task: ComponentGovernanceComponentDetection@0\n      displayName: Component Detection (manually injected)\n      inputs:\n        # Running CG with `whatIf: true` or `scanType: LogOnly` outputs a list of detected components, but doesn't show\n        # which components would trigger an alert on a production build.\n        # As long as the build isn't ran on a tracked branch (typically main or nightly), it's OK to submit components\n        # to CG for analysis. Only the results for tracked branches matter.\n        scanType: Register\n        whatIf: false\n        alertWarningLevel: Low\n        failOnAlert: false\n        ignoreDirectories: $(Build.SourcesDirectory)/versions\n        showAlertLink: true\n        timeoutInMinutes: 10\n" contains invalid character(s), is too long, or ends with '.'. The maximum length of a build number is 255 characters. Characters which are not allowed include '"', '/', ':', '<', '>', '\', '|', '?', '@', and '*'.

Example build (internal link)

This is a regression from #1371

[dotnet-issue-labeler[bot]]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[dotnet-issue-labeler[bot]]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[lbussell]

[Triage] We should investigate this to figure out if this is the reason the dotnet-framework-docker repo isn't receiving updates from docker-tools: https://github.com/microsoft/dotnet-framework-docker/pull/1157#discussion_r1712245443

[MichaelSimons]

@lbussell - Can you investigate? the push-common-updates pipeline should get unblocked. TIA