digital-asset/daml
1
1
Fork 0
mirror of https://github.com/digital-asset/daml.git synced 2024-11-09 15:37:05 +03:00
Code Issues Projects Releases Wiki Activity
d2e2c21684
daml/ci/copy-windows-release-artifacts.sh

40 lines
1.5 KiB
Bash
Raw Normal View History

Move artifact publishing out of yaml files (#9071) * Move artifact publishing out of yaml files The current publishing process pretty much hardcodes the set of artifacts we publish in the yaml config. This is a problem because we always release from `main` so the yaml files are always identical. However, we will add new artifacts over time and this starts falling apart. This PR changes this such that the process described in the yaml files is very generic and just uploads and downloads everything in a directory whereas the details are handled in bash scripts that will come from the respective release branch and are therefore version-dependent. As usual for these type of changes, I don’t have a great way to test this. I did do some due diligence to test that at least the artifacts are published correctly and I can download them but I can’t test the actual publishing. changelog_begin changelog_end * Update ci/copy-unix-release-artifacts.sh Co-authored-by: Gary Verhaegen <gary.verhaegen@digitalasset.com> * Update ci/copy-windows-release-artifacts.sh Co-authored-by: Gary Verhaegen <gary.verhaegen@digitalasset.com> * Update ci/publish-artifactory.sh Co-authored-by: Gary Verhaegen <gary.verhaegen@digitalasset.com> Co-authored-by: Gary Verhaegen <gary.verhaegen@digitalasset.com>
2021-03-11 13:44:02 +03:00
#!/usr/bin/env bash
update copyright headers (#12240) New year, new copyright, new expected unknown issues with various files that won't be covered by the script and/or will be but shouldn't change. I'll do the details on Jan 1, but would appreciate this being preapproved so I can actually get it merged by then. CHANGELOG_BEGIN CHANGELOG_END
2022-01-03 19:36:51 +03:00
# Copyright (c) 2022 Digital Asset (Switzerland) GmbH and/or its affiliates. All rights reserved.
Move artifact publishing out of yaml files (#9071) * Move artifact publishing out of yaml files The current publishing process pretty much hardcodes the set of artifacts we publish in the yaml config. This is a problem because we always release from `main` so the yaml files are always identical. However, we will add new artifacts over time and this starts falling apart. This PR changes this such that the process described in the yaml files is very generic and just uploads and downloads everything in a directory whereas the details are handled in bash scripts that will come from the respective release branch and are therefore version-dependent. As usual for these type of changes, I don’t have a great way to test this. I did do some due diligence to test that at least the artifacts are published correctly and I can download them but I can’t test the actual publishing. changelog_begin changelog_end * Update ci/copy-unix-release-artifacts.sh Co-authored-by: Gary Verhaegen <gary.verhaegen@digitalasset.com> * Update ci/copy-windows-release-artifacts.sh Co-authored-by: Gary Verhaegen <gary.verhaegen@digitalasset.com> * Update ci/publish-artifactory.sh Co-authored-by: Gary Verhaegen <gary.verhaegen@digitalasset.com> Co-authored-by: Gary Verhaegen <gary.verhaegen@digitalasset.com>
2021-03-11 13:44:02 +03:00
# SPDX-License-Identifier: Apache-2.0
set -eou pipefail
RELEASE_TAG=$1
OUTPUT_DIR=$2
mkdir -p $OUTPUT_DIR/github
ci/windows: add missing mkdir (#9103) CHANGELOG_BEGIN CHANGELOG_END
2021-03-11 21:16:19 +03:00
mkdir -p $OUTPUT_DIR/artifactory
new windows signing (#9786) CHANGELOG_BEGIN CHANGELOG_END
2021-05-25 17:23:17 +03:00
INSTALLER="$OUTPUT_DIR/github/daml-sdk-$RELEASE_TAG-windows.exe"
EE_INSTALLER="$OUTPUT_DIR/artifactory/daml-sdk-$RELEASE_TAG-windows-ee.exe"
mv "bazel-bin/release/windows-installer/daml-sdk-installer-ce.exe" "$INSTALLER"
mv "bazel-bin/release/windows-installer/daml-sdk-installer-ee.exe" "$EE_INSTALLER"
chmod +wx "$INSTALLER"
chmod +wx "$EE_INSTALLER"
if ! [ -f /C/Users/u/.dotnet/tools/azuresigntool.exe ]; then
bump dotnet (#10979) This bumps dotnet to the version required by the latest azuresigntool, and pins azuresigntool for the future. As usual for live CI upgrades, this will be rolled out using the blue/green approach. I'll keep each deployed commit in this PR. For future reference, this is PR [#10979]. [#10979]: https://github.com/digital-asset/daml/pull/10979 CHANGELOG_BEGIN CHANGELOG_END
2021-09-22 19:39:40 +03:00
"/C/Program Files/dotnet/dotnet.exe" tool install --global AzureSignTool --version 3.0.0
new windows signing (#9786) CHANGELOG_BEGIN CHANGELOG_END
2021-05-25 17:23:17 +03:00
fi
/C/Users/u/.dotnet/tools/azuresigntool.exe sign \
--azure-key-vault-url "$AZURE_KEY_VAULT_URL" \
--azure-key-vault-client-id "$AZURE_CLIENT_ID" \
bump dotnet (#10979) This bumps dotnet to the version required by the latest azuresigntool, and pins azuresigntool for the future. As usual for live CI upgrades, this will be rolled out using the blue/green approach. I'll keep each deployed commit in this PR. For future reference, this is PR [#10979]. [#10979]: https://github.com/digital-asset/daml/pull/10979 CHANGELOG_BEGIN CHANGELOG_END
2021-09-22 19:39:40 +03:00
--azure-key-vault-tenant-id "$AZURE_TENANT_ID" \
new windows signing (#9786) CHANGELOG_BEGIN CHANGELOG_END
2021-05-25 17:23:17 +03:00
--azure-key-vault-client-secret "$AZURE_CLIENT_SECRET" \
--azure-key-vault-certificate "$AZURE_KEY_VAULT_CERTIFICATE" \
--description "Daml SDK installer" \
--description-url "https://daml.com" \
--timestamp-rfc3161 "http://timestamp.digicert.com" \
--file-digest sha384 \
--verbose \
"$INSTALLER" \
"$EE_INSTALLER"
Move artifact publishing out of yaml files (#9071) * Move artifact publishing out of yaml files The current publishing process pretty much hardcodes the set of artifacts we publish in the yaml config. This is a problem because we always release from `main` so the yaml files are always identical. However, we will add new artifacts over time and this starts falling apart. This PR changes this such that the process described in the yaml files is very generic and just uploads and downloads everything in a directory whereas the details are handled in bash scripts that will come from the respective release branch and are therefore version-dependent. As usual for these type of changes, I don’t have a great way to test this. I did do some due diligence to test that at least the artifacts are published correctly and I can download them but I can’t test the actual publishing. changelog_begin changelog_end * Update ci/copy-unix-release-artifacts.sh Co-authored-by: Gary Verhaegen <gary.verhaegen@digitalasset.com> * Update ci/copy-windows-release-artifacts.sh Co-authored-by: Gary Verhaegen <gary.verhaegen@digitalasset.com> * Update ci/publish-artifactory.sh Co-authored-by: Gary Verhaegen <gary.verhaegen@digitalasset.com> Co-authored-by: Gary Verhaegen <gary.verhaegen@digitalasset.com>
2021-03-11 13:44:02 +03:00
TARBALL=daml-sdk-$RELEASE_TAG-windows.tar.gz
Release EE SDK tarballs and installer (#9086) * Release EE SDK tarballs and installer As before, no way of testing this. I’ll do a snapshot afterwards. changelog_begin changelog_end * . changelog_begin changelog_end * . changelog_begin changelog_end * Rename EE artifacts changelog_begin changelog_end
2021-03-11 16:49:48 +03:00
EE_TARBALL=daml-sdk-$RELEASE_TAG-windows-ee.tar.gz
cp bazel-bin/release/sdk-release-tarball-ce.tar.gz "$OUTPUT_DIR/github/$TARBALL"
cp bazel-bin/release/sdk-release-tarball-ee.tar.gz "$OUTPUT_DIR/artifactory/$EE_TARBALL"
Reference in New Issue Copy Permalink