mirrors/dotnet-installer
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
dotnet-installer/eng/Publishing.props

148 lines
9.4 KiB
Text
Raw Normal View History

Initial changes to use the publishing infra from arcade to publish our assets.
2018-12-19 20:53:08 +00:00
<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (c) .NET Foundation and contributors. All rights reserved. Licensed under the MIT license. See License.txt in the project root for full license information. -->
<Project>
V3 publishing (#8598) * v3
2020-09-17 17:05:22 +00:00
<PropertyGroup>
<PublishingVersion>3</PublishingVersion>
</PropertyGroup>
Initial changes to use the publishing infra from arcade to publish our assets.
2018-12-19 20:53:08 +00:00
<PropertyGroup>
<Product>Sdk</Product>
<BlobStoragePartialRelativePath>$(Product)</BlobStoragePartialRelativePath>
Producing and publishing checksums. Also, publishing sdk assets ourselves, so that we can add metadata regarding where to push nupkgs.
2018-12-21 22:58:11 +00:00
<ChecksumsFeedUrl>$(DotnetPublishChecksumsBlobFeedUrl)</ChecksumsFeedUrl>
<SdkAssetsFeedUrl>$(DotnetPublishSdkAssetsBlobFeedUrl)</SdkAssetsFeedUrl>
<PublishSdkAssetsAndChecksumsToBlob>false</PublishSdkAssetsAndChecksumsToBlob>
<PublishSdkAssetsAndChecksumsToBlob Condition=" '$(ChecksumsFeedUrl)' != '' and '$(SdkAssetsFeedUrl)' != '' ">true</PublishSdkAssetsAndChecksumsToBlob>
Fixing the publishing of deb and rpm files. Also added a property to turn off publishing binaries, as we need to prevent the linux-x64 binaries from being published multiple times.
2018-12-22 05:43:17 +00:00
Prevent attempting to publish duplicate badge and checksum files.
2018-12-26 19:42:24 +00:00
<PublishBinariesAndBadge Condition=" '$(PublishBinariesAndBadge)' == '' ">true</PublishBinariesAndBadge>
Initial changes to use the publishing infra from arcade to publish our assets.
2018-12-19 20:53:08 +00:00
</PropertyGroup>
Use more consistent manifest attributes (#7991) Create manifest attributes that are consistent with arcade's usage. This also means they will be consistent between manifests, which is important.
2020-07-15 20:32:28 +00:00
<!-- Pulled from arcade's publish.proj see https://github.com/dotnet/arcade/issues/5790 for
issue on making this common in arcade so it doesn't have to be duplicated here -->
<PropertyGroup>
<CollectionUri>$(SYSTEM_TEAMFOUNDATIONCOLLECTIONURI)</CollectionUri>
<!-- When we have dev.azure.com/<account>/ -->
<AzureDevOpsAccount Condition="$(CollectionUri.IndexOf('dev.azure.com')) >= 0">$(CollectionUri.Split('/')[3])</AzureDevOpsAccount>
<!-- When we have <account>.visualstudio.com -->
<AzureDevOpsAccount Condition="$(CollectionUri.IndexOf('visualstudio.com')) >= 0">$(CollectionUri.Split('.')[0].Split('/')[2])</AzureDevOpsAccount>
</PropertyGroup>
<!--
The new Maestro/BAR build model keeps separate Azure DevOps and GitHub build information.
The GitHub information will be extracted based on the Azure DevOps repository.
-->
<ItemGroup>
<ManifestBuildData Include="InitialAssetsLocation=$(SYSTEM_TEAMFOUNDATIONCOLLECTIONURI)$(SYSTEM_TEAMPROJECT)/_apis/build/builds/$(BUILD_BUILDID)/artifacts" />
<ManifestBuildData Include="AzureDevOpsBuildId=$(BUILD_BUILDID)" />
<ManifestBuildData Include="AzureDevOpsBuildDefinitionId=$(SYSTEM_DEFINITIONID)" />
<ManifestBuildData Include="AzureDevOpsAccount=$(AzureDevOpsAccount)" />
<ManifestBuildData Include="AzureDevOpsProject=$(SYSTEM_TEAMPROJECT)" />
<ManifestBuildData Include="AzureDevOpsBuildNumber=$(BUILD_BUILDNUMBER)" />
<ManifestBuildData Include="AzureDevOpsRepository=$(BUILD_REPOSITORY_URI)" />
<ManifestBuildData Include="AzureDevOpsBranch=$(BUILD_SOURCEBRANCH)" />
</ItemGroup>
Move property group after import
2019-01-24 21:12:57 +00:00
<PropertyGroup>
<!-- Because we may be building in a container, we should use an asset manifest file path
Fix asset manifest file names. Set the asset manifest OS and change the name of the installers manifests. Currently arcade defaults to using OS-Platform as the asset manifest file name. Installer does a ton of building in docker containers, which ends up generating many overlapping names. This is a symptom and also likely hiding some non-determinsm. To fix, change the name of the blob asset manifest name to include a "-installers" suffix. Then alter the property names around a bit so that AssetManifestOS is set prior to publish.proj's publish target being run.
2020-08-03 19:18:09 +00:00
that exists in the container. Disambiguate the manifests via available properties.
AGENT_OS and AGENT_JOBNAME are present on Azure DevOps agents. AssetManifestOS will also
be used by arcade to generate the name of the manifest file name for the built in publishing. -->
<AssetManifestOS Condition="'$(AGENT_OS)' != ''">$(AGENT_OS)</AssetManifestOS>
<AssetManifestOS Condition="'$(AGENT_OS)' == ''">$(OS)</AssetManifestOS>
<AssetManifestOS Condition="'$(AGENT_JOBNAME)' != ''">$(AssetManifestOS)-$(AGENT_JOBNAME)</AssetManifestOS>
<BaseAssetManifestFileName>$(AssetManifestOS)</BaseAssetManifestFileName>
<BaseAssetManifestFileName Condition="'$(AGENT_JOBNAME)' == '' and '$(Architecture)' != ''">$(AssetManifestOS)-$(Architecture)</BaseAssetManifestFileName>
<InstallersAssetManifestFileName>$(BaseAssetManifestFileName)-installers</InstallersAssetManifestFileName>
<!-- Property AssetManifestFilePath would be reassigned by the Arcade SDK, so use a different name (InstallersAssetManifestFilePath) -->
<InstallersAssetManifestFilePath>$(ArtifactsLogDir)AssetManifest\$(InstallersAssetManifestFileName).xml</InstallersAssetManifestFilePath>
Changes for core-sdk to move to yaml stages
2019-09-10 19:33:20 +00:00
<DotnetTempWorkingDirectory>$(ArtifactsDir)..\DotnetAssetsTmpDir\$([System.Guid]::NewGuid())</DotnetTempWorkingDirectory>
<ChecksumTempWorkingDirectory>$(ArtifactsDir)..\ChecksumAssetsTmpDir\$([System.Guid]::NewGuid())</ChecksumTempWorkingDirectory>
Move property group after import
2019-01-24 21:12:57 +00:00
</PropertyGroup>
Fixing debs generation. The issue was that we were losing the exec permission on the apphost in the sdk folder. This caused it to not be picked up by dh_shlibsdeps. This happened because the order of the apphost acquisition was changed to be after crossgen, where we change permissions of all files under the SDK folder to 644. The fix here was to make the apphost acquisition to happen after crossgen.
2018-12-24 18:12:23 +00:00
Initial changes to use the publishing infra from arcade to publish our assets.
2018-12-19 20:53:08 +00:00
<ItemGroup>
Prevent attempting to publish duplicate badge and checksum files.
2018-12-26 19:42:24 +00:00
<SdkAssetsToPublish Include="$(ArtifactsShippingPackagesDir)*.zip" Condition=" '$(PublishBinariesAndBadge)' == 'true' " />
<SdkAssetsToPublish Include="$(ArtifactsShippingPackagesDir)*.tar.gz" Condition=" '$(PublishBinariesAndBadge)' == 'true' " />
Initial changes to use the publishing infra from arcade to publish our assets.
2018-12-19 20:53:08 +00:00
<SdkAssetsToPublish Include="$(ArtifactsShippingPackagesDir)*.pkg" />
<SdkAssetsToPublish Include="$(ArtifactsShippingPackagesDir)*.exe" />
<SdkAssetsToPublish Include="$(ArtifactsShippingPackagesDir)*.deb" />
<SdkAssetsToPublish Include="$(ArtifactsShippingPackagesDir)*.rpm" />
<SdkAssetsToPublish Include="$(ArtifactsShippingPackagesDir)*.msi" />
Producing and publishing checksums. Also, publishing sdk assets ourselves, so that we can add metadata regarding where to push nupkgs.
2018-12-21 22:58:11 +00:00
<SdkAssetsToPublish Include="$(ArtifactsShippingPackagesDir)*.nupkg" />
Resolve named CAB collision and drop the CABs (#1976) * Resolve named CAB collision; drop the CABs. * Resolving naming convention warning: 8 chars plus {0} are allowed. * Update src/redist/targets/packaging/windows/clisdk/dotnet.wxs Co-Authored-By: Peter Huene <pehuene@microsoft.com>
2019-05-16 23:33:29 +00:00
<SdkAssetsToPublish Include="$(ArtifactsShippingPackagesDir)*.cab" />
Changes for core-sdk to move to yaml stages
2019-09-10 19:33:20 +00:00
<SdkAssetsToPublish Include="$(ArtifactsShippingPackagesDir)*.svg" Condition=" '$(PublishBinariesAndBadge)' == 'true' " />
[release/5.0.1xx-preview4] Generate versions sparsely (#7290) * Publish productVersion sparsely Do not publish the productVersion file in every leg. Publish only in win-x64, so that we don't end up uploading it for every manifest. Publishing breaks in this scenario today. This is a real bug in publishing, but we will probably tighten the restrictions in the Publish to BAR step so that multi-publishign the same asset is an error. Also remove the productCommit-* in cases where we have overlapping rids, which would cause the same problem
2020-04-24 21:02:27 +00:00
<!-- Only publish this file from windows x64 so that we don't end up with duplicates -->
<SdkAssetsToPublish Include="$(ArtifactsShippingPackagesDir)productVersion.txt"
Condition=" '$(PublishBinariesAndBadge)' == 'true' and '$(OS)' == 'Windows_NT' and '$(Architecture)' == 'x64'" />
Duplicate productVersion.txt with repo-specific name (#9666) (#9709) In our efforts to unify the build access story using aka.ms links, we have found that there are certain files that share the same name in multiple different repositories, most importantly, productVersion.txt. As part of the work to move to aka.ms links, we will be flattening the short link paths, so rather than having a runtime-specific, aspnetcore-specific, etc. full path to the files generated by each of the repos, they will all go to the same short link location. This means that the path to productVersion.txt will collide in the aka.ms links (the backing locations are not changing and will be unaffected). To combat this, we will add a duplicate of each of the product repos productVersion.txt, renamed to indicate which product repo it came from, in this case installer-productVersion.txt. The original will remane so that we do not break existing scenarios that do not use the aka.ms links.
2021-02-16 17:22:48 +00:00
<SdkAssetsToPublish Include="$(ArtifactsShippingPackagesDir)sdk-productVersion.txt"
Condition=" '$(PublishBinariesAndBadge)' == 'true' and '$(OS)' == 'Windows_NT' and '$(Architecture)' == 'x64'" />
Generating a productCommit for each rid
2020-03-27 12:49:29 +00:00
<SdkAssetsToPublish Include="$(ArtifactsShippingPackagesDir)productCommit-*.txt" Condition=" '$(PublishBinariesAndBadge)' == 'true' " />
Publish non-shipping VS.* packages to blob storage
2019-01-25 22:36:14 +00:00
<SdkNonShippingAssetsToPublish Include="$(ArtifactsNonShippingPackagesDir)*.nupkg" />
Adding the swr as a file to be published.
2019-07-24 20:17:25 +00:00
<SdkNonShippingAssetsToPublish Include="$(ArtifactsNonShippingPackagesDir)*.swr" />
Make some artifacts non-shipping (#7857) Makes the following artifacts non-shipping: - template msis - sdkplaceholders - sdk-internal archives For now these have been preserved as non-shipping rather than not published at all. They all get packaged up in the VS insertion nupkgs, so I think in reality we don't need them at all.
2020-06-25 18:36:38 +00:00
<SdkNonShippingAssetsToPublish Include="$(ArtifactsNonShippingPackagesDir)*.msi" />
Only publishing nonshipping binaries when PublishBinariesAndBadge is not false
2020-06-30 16:13:04 +00:00
<SdkNonShippingAssetsToPublish Condition="'$(PublishBinariesAndBadge)' != 'false'" Include="$(ArtifactsNonShippingPackagesDir)*.tar.gz" />
<SdkNonShippingAssetsToPublish Condition="'$(PublishBinariesAndBadge)' != 'false'" Include="$(ArtifactsNonShippingPackagesDir)*.zip" />
Make some artifacts non-shipping (#7857) Makes the following artifacts non-shipping: - template msis - sdkplaceholders - sdk-internal archives For now these have been preserved as non-shipping rather than not published at all. They all get packaged up in the VS insertion nupkgs, so I think in reality we don't need them at all.
2020-06-25 18:36:38 +00:00
<SdkNonShippingAssetsToPublish Include="$(ArtifactsNonShippingPackagesDir)*.pkg" />
Producing and publishing checksums. Also, publishing sdk assets ourselves, so that we can add metadata regarding where to push nupkgs.
2018-12-21 22:58:11 +00:00
<CheckSumsToPublish Include="$(ArtifactsShippingPackagesDir)*.sha" />
[release/5.0.1xx-preview4] Generate versions sparsely (#7290) * Publish productVersion sparsely Do not publish the productVersion file in every leg. Publish only in win-x64, so that we don't end up uploading it for every manifest. Publishing breaks in this scenario today. This is a real bug in publishing, but we will probably tighten the restrictions in the Publish to BAR step so that multi-publishign the same asset is an error. Also remove the productCommit-* in cases where we have overlapping rids, which would cause the same problem
2020-04-24 21:02:27 +00:00
<CheckSumsToPublish Remove="$(ArtifactsShippingPackagesDir)productCommit-*.txt.sha" Condition=" '$(PublishBinariesAndBadge)' == 'false'" />
<CheckSumsToPublish Remove="$(ArtifactsShippingPackagesDir)productVersion.txt.sha" Condition=" '$(OS)' != 'Windows_NT' or '$(Architecture)' != 'x64'" />
Duplicate productVersion.txt with repo-specific name (#9666) (#9709) In our efforts to unify the build access story using aka.ms links, we have found that there are certain files that share the same name in multiple different repositories, most importantly, productVersion.txt. As part of the work to move to aka.ms links, we will be flattening the short link paths, so rather than having a runtime-specific, aspnetcore-specific, etc. full path to the files generated by each of the repos, they will all go to the same short link location. This means that the path to productVersion.txt will collide in the aka.ms links (the backing locations are not changing and will be unaffected). To combat this, we will add a duplicate of each of the product repos productVersion.txt, renamed to indicate which product repo it came from, in this case installer-productVersion.txt. The original will remane so that we do not break existing scenarios that do not use the aka.ms links.
2021-02-16 17:22:48 +00:00
<CheckSumsToPublish Remove="$(ArtifactsShippingPackagesDir)sdk-productVersion.txt.sha" Condition=" '$(OS)' != 'Windows_NT' or '$(Architecture)' != 'x64'" />
Prevent attempting to publish duplicate badge and checksum files.
2018-12-26 19:42:24 +00:00
<CheckSumsToPublish Remove="$(ArtifactsShippingPackagesDir)*.zip.sha" Condition=" '$(PublishBinariesAndBadge)' == 'false' "/>
<CheckSumsToPublish Remove="$(ArtifactsShippingPackagesDir)*.tar.gz.sha" Condition=" '$(PublishBinariesAndBadge)' == 'false' "/>
Initial changes to use the publishing infra from arcade to publish our assets.
2018-12-19 20:53:08 +00:00
</ItemGroup>
Producing and publishing checksums. Also, publishing sdk assets ourselves, so that we can add metadata regarding where to push nupkgs.
2018-12-21 22:58:11 +00:00
<Target Name="PublishSdkAssetsAndChecksums"
BeforeTargets="Publish"
Condition=" '$(PublishSdkAssetsAndChecksumsToBlob)' == 'true' ">
[release/3.0.1xx] Publish SDK bits to a suffixed location (#5078) * Publish SDK bits to a suffixed location Also, when DropSuffix==true, copy all files that contain the stable sdk version to a file containing the non-stable file name
2019-10-07 20:11:06 +00:00
Did a hack where we are writing the version to a file during build to be read during publish, as these are two separate builds by arcade and also passed the BuildNumberId so that the id is calculated properly during copy to latest.
2020-01-10 05:13:46 +00:00
<ReadLinesFromFile File="$(ArtifactsTmpDir)FullNugetVersion.version">
<Output
TaskParameter="Lines"
PropertyName="FullNugetVersion"/>
</ReadLinesFromFile>
Publishes the binaries and native installers.
2018-12-20 00:08:49 +00:00
<ItemGroup>
[release/3.0.1xx] Publish SDK bits to a suffixed location (#5078) * Publish SDK bits to a suffixed location Also, when DropSuffix==true, copy all files that contain the stable sdk version to a file containing the non-stable file name
2019-10-07 20:11:06 +00:00
<!-- Always publish blobs to a suffixed directory. -->
Provide NonShipping metadata
2019-06-26 20:55:25 +00:00
<SdkAssetsToPushToBlobFeed Include="@(SdkAssetsToPublish)">
[release/3.0.1xx] Publish SDK bits to a suffixed location (#5078) * Publish SDK bits to a suffixed location Also, when DropSuffix==true, copy all files that contain the stable sdk version to a file containing the non-stable file name
2019-10-07 20:11:06 +00:00
<RelativeBlobPath>$(BlobStoragePartialRelativePath)/$(FullNugetVersion)/$([System.String]::Copy('%(Filename)%(Extension)'))</RelativeBlobPath>
Producing and publishing checksums. Also, publishing sdk assets ourselves, so that we can add metadata regarding where to push nupkgs.
2018-12-21 22:58:11 +00:00
</SdkAssetsToPushToBlobFeed>
Provide NonShipping metadata
2019-06-26 20:55:25 +00:00
<SdkAssetsToPushToBlobFeed Include="@(SdkNonShippingAssetsToPublish)">
[release/3.0.1xx] Publish SDK bits to a suffixed location (#5078) * Publish SDK bits to a suffixed location Also, when DropSuffix==true, copy all files that contain the stable sdk version to a file containing the non-stable file name
2019-10-07 20:11:06 +00:00
<RelativeBlobPath>$(BlobStoragePartialRelativePath)/$(FullNugetVersion)/$([System.String]::Copy('%(Filename)%(Extension)'))</RelativeBlobPath>
Provide NonShipping metadata
2019-06-26 20:55:25 +00:00
<ManifestArtifactData>NonShipping=true</ManifestArtifactData>
Producing and publishing checksums. Also, publishing sdk assets ourselves, so that we can add metadata regarding where to push nupkgs.
2018-12-21 22:58:11 +00:00
</SdkAssetsToPushToBlobFeed>
Provide NonShipping metadata
2019-06-26 20:55:25 +00:00
<ChecksumsToPushToBlobFeed Include="@(CheckSumsToPublish)">
[release/3.0.1xx] Publish SDK bits to a suffixed location (#5078) * Publish SDK bits to a suffixed location Also, when DropSuffix==true, copy all files that contain the stable sdk version to a file containing the non-stable file name
2019-10-07 20:11:06 +00:00
<RelativeBlobPath>$(BlobStoragePartialRelativePath)/$(FullNugetVersion)/$([System.String]::Copy('%(Filename)%(Extension)'))</RelativeBlobPath>
Producing and publishing checksums. Also, publishing sdk assets ourselves, so that we can add metadata regarding where to push nupkgs.
2018-12-21 22:58:11 +00:00
</ChecksumsToPushToBlobFeed>
Publishes the binaries and native installers.
2018-12-20 00:08:49 +00:00
</ItemGroup>
[release/5.0.1xx] Enable post build signing (#8764) * Enable post build signing Enables post build signing of installer by including the items that need to be signed post build in an ItemsToSignPostBuild item group and moving the file signing information into the Signing.props files. Changes to in-build signing have been verified by taking a drop with the current in-build structure and comparing the the signatures and strong name keys between files in equivalent builds. * Enable post build signing Enables post build signing of installer by including the items that need to be signed post build in an ItemsToSignPostBuild item group and moving the file signing information into the Signing.props files. Changes to in-build signing have been verified by taking a drop with the current in-build structure and comparing the the signatures and strong name keys between files in equivalent builds. Co-authored-by: dotnet-bot <dotnet-bot@dotnetfoundation.org> Co-authored-by: Christopher Costa <chcosta@microsoft.com>
2020-10-14 21:55:38 +00:00
<PropertyGroup>
<IsStableBuild>false</IsStableBuild>
<IsStableBuild Condition="'$(DotNetFinalVersionKind)' == 'release'">true</IsStableBuild>
</PropertyGroup>
Changes for core-sdk to move to yaml stages
2019-09-10 19:33:20 +00:00
<PushToAzureDevOpsArtifacts
[release/5.0.1xx] Enable post build signing (#8764) * Enable post build signing Enables post build signing of installer by including the items that need to be signed post build in an ItemsToSignPostBuild item group and moving the file signing information into the Signing.props files. Changes to in-build signing have been verified by taking a drop with the current in-build structure and comparing the the signatures and strong name keys between files in equivalent builds. * Enable post build signing Enables post build signing of installer by including the items that need to be signed post build in an ItemsToSignPostBuild item group and moving the file signing information into the Signing.props files. Changes to in-build signing have been verified by taking a drop with the current in-build structure and comparing the the signatures and strong name keys between files in equivalent builds. Co-authored-by: dotnet-bot <dotnet-bot@dotnetfoundation.org> Co-authored-by: Christopher Costa <chcosta@microsoft.com>
2020-10-14 21:55:38 +00:00
AzureDevOpsCollectionUri="$(SYSTEM_TEAMFOUNDATIONCOLLECTIONURI)"
AzureDevOpsProject="$(SYSTEM_TEAMPROJECT)"
AzureDevOpsBuildId="$(BUILD_BUILDID)"
ItemsToPush="@(SdkAssetsToPushToBlobFeed);@(ChecksumsToPushToBlobFeed)"
ItemsToSign="@(ItemsToSignPostBuild)"
CertificatesSignInfo="@(CertificatesSignInfo)"
StrongNameSignInfo="@(StrongNameSignInfo)"
FileSignInfo="@(FileSignInfo)"
FileExtensionSignInfo="@(FileExtensionSignInfo)"
Use more consistent manifest attributes (#7991) Create manifest attributes that are consistent with arcade's usage. This also means they will be consistent between manifests, which is important.
2020-07-15 20:32:28 +00:00
ManifestBuildData="@(ManifestBuildData)"
[release/5.0.1xx] Enable post build signing (#8764) * Enable post build signing Enables post build signing of installer by including the items that need to be signed post build in an ItemsToSignPostBuild item group and moving the file signing information into the Signing.props files. Changes to in-build signing have been verified by taking a drop with the current in-build structure and comparing the the signatures and strong name keys between files in equivalent builds. * Enable post build signing Enables post build signing of installer by including the items that need to be signed post build in an ItemsToSignPostBuild item group and moving the file signing information into the Signing.props files. Changes to in-build signing have been verified by taking a drop with the current in-build structure and comparing the the signatures and strong name keys between files in equivalent builds. Co-authored-by: dotnet-bot <dotnet-bot@dotnetfoundation.org> Co-authored-by: Christopher Costa <chcosta@microsoft.com>
2020-10-14 21:55:38 +00:00
ManifestRepoName="$(BUILD_REPOSITORY_NAME)"
Producing and publishing checksums. Also, publishing sdk assets ourselves, so that we can add metadata regarding where to push nupkgs.
2018-12-21 22:58:11 +00:00
ManifestBranch="$(BUILD_SOURCEBRANCH)"
ManifestBuildId="$(BUILD_BUILDNUMBER)"
ManifestCommit="$(BUILD_SOURCEVERSION)"
Fix asset manifest file names. Set the asset manifest OS and change the name of the installers manifests. Currently arcade defaults to using OS-Platform as the asset manifest file name. Installer does a ton of building in docker containers, which ends up generating many overlapping names. This is a symptom and also likely hiding some non-determinsm. To fix, change the name of the blob asset manifest name to include a "-installers" suffix. Then alter the property names around a bit so that AssetManifestOS is set prior to publish.proj's publish target being run.
2020-08-03 19:18:09 +00:00
AssetManifestPath="$(InstallersAssetManifestFilePath)"
V3 publishing (#8598) * v3
2020-09-17 17:05:22 +00:00
PublishFlatContainer="true"
[release/5.0.1xx] Enable post build signing (#8764) * Enable post build signing Enables post build signing of installer by including the items that need to be signed post build in an ItemsToSignPostBuild item group and moving the file signing information into the Signing.props files. Changes to in-build signing have been verified by taking a drop with the current in-build structure and comparing the the signatures and strong name keys between files in equivalent builds. * Enable post build signing Enables post build signing of installer by including the items that need to be signed post build in an ItemsToSignPostBuild item group and moving the file signing information into the Signing.props files. Changes to in-build signing have been verified by taking a drop with the current in-build structure and comparing the the signatures and strong name keys between files in equivalent builds. Co-authored-by: dotnet-bot <dotnet-bot@dotnetfoundation.org> Co-authored-by: Christopher Costa <chcosta@microsoft.com>
2020-10-14 21:55:38 +00:00
IsStableBuild="$(IsStableBuild)"
PublishingVersion="3" />
Producing and publishing checksums. Also, publishing sdk assets ourselves, so that we can add metadata regarding where to push nupkgs.
2018-12-21 22:58:11 +00:00
</Target>
Initial changes to use the publishing infra from arcade to publish our assets.
2018-12-19 20:53:08 +00:00
</Project>
Reference in a new issue Copy permalink