diff options
| author | William Godbe <wigodbe@microsoft.com> | 2017-10-16 10:59:31 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-10-16 10:59:31 -0700 |
| commit | f2dfe84a6f5f6ba816c99c3e0c60a1c13eb09be9 (patch) | |
| tree | 0e3602724107c67958bc2867a9e5dff558891ec9 /buildpipeline | |
| parent | a78940216170cdf5f9b97ccbf6edaca2ac0758c9 (diff) | |
| download | coreclr-f2dfe84a6f5f6ba816c99c3e0c60a1c13eb09be9.tar.gz coreclr-f2dfe84a6f5f6ba816c99c3e0c60a1c13eb09be9.tar.bz2 coreclr-f2dfe84a6f5f6ba816c99c3e0c60a1c13eb09be9.zip | |
Parameterize PublishFlatContainer in x86 build
This was missed in my last change to parameterize PublishFlatContainer across the board, and is what was causing the failures in today's pipe builds. We only want to publish non-flat for Release builds, but were hardcoding PublishFlatContainer=true for all builds in the x86 definition.
Diffstat (limited to 'buildpipeline')
| -rw-r--r-- | buildpipeline/DotNet-CoreClr-Trusted-Windows-x86.json | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/buildpipeline/DotNet-CoreClr-Trusted-Windows-x86.json b/buildpipeline/DotNet-CoreClr-Trusted-Windows-x86.json index 3902c4bd5c..3b71cf41eb 100644 --- a/buildpipeline/DotNet-CoreClr-Trusted-Windows-x86.json +++ b/buildpipeline/DotNet-CoreClr-Trusted-Windows-x86.json @@ -150,7 +150,7 @@ }, "inputs": { "filename": "publish-packages.cmd", - "arguments": "-AzureAccount=$(CloudDropAccountName) -AzureToken=$(CloudDropAccessToken) -BuildArch=$(Architecture) -BuildType=$(PB_BuildType) -Container=$(PB_ContainerName) -PublishPackages -- /p:RelativePath=$(PB_BlobNamePrefix)$(PB_BuildType)/pkg /p:PublishFlatContainer=false /p:OverwriteOnPublish=true", + "arguments": "-AzureAccount=$(CloudDropAccountName) -AzureToken=$(CloudDropAccessToken) -BuildArch=$(Architecture) -BuildType=$(PB_BuildType) -Container=$(PB_ContainerName) -PublishPackages -- /p:RelativePath=$(PB_BlobNamePrefix)$(PB_BuildType)/pkg /p:PublishFlatContainer=$(PublishFlat) /p:OverwriteOnPublish=true", "workingFolder": "", "failOnStandardError": "false" } |