rpcs3/.ci/deploy-windows.sh

#!/bin/sh -ex

# BUILD_blablabla is Azure specific, so we wrap it for portability
ARTIFACT_DIR="$BUILD_ARTIFACTSTAGINGDIRECTORY"

# Remove unecessary files
rm -f ./bin/rpcs3.exp ./bin/rpcs3.lib ./bin/rpcs3.pdb

# Prepare compatibility database for packaging, as well as
# certificate for ssl (auto-updater)
curl -sL 'https://rpcs3.net/compatibility?api=v1&export' | iconv -t UTF-8 > ./bin/GuiConfigs/compat_database.dat
curl -sL 'https://curl.haxx.se/ca/cacert.pem' > ./bin/cacert.pem

# Package artifacts
7z a -m0=LZMA2 -mx9 "$BUILD" ./bin/*

# Generate sha256 hashes
# Write to file for GitHub releases
sha256sum "$BUILD" | awk '{ print $1 }' | tee "$BUILD.sha256"
echo "$(cat "$BUILD.sha256");$(stat -c %s "$BUILD")B" > GitHubReleaseMessage.txt

# Move files to publishing directory
mv -- "$BUILD" "$ARTIFACT_DIR"
mv -- "$BUILD.sha256" "$ARTIFACT_DIR"
CI: Port Windows build to Azure Pipelines (#7757) * CI: Port Windows build to Azure Pipelines from Appveyor * CI: Split Windows build into scripts * CI: Remove Appveyor * CI: Add GitHub Release deployment to Azure Windows Build * VCS: Add full branch name function to rpcs3_version The STRINGIZE macro was a little awkward, and difficult to control at configure time. Since other version information is already included, the full branch name is now added as a function. It's runtime instead of compile-time checking, but it seems worth it. * CI: Overhaul Windows setup script Previously, there was no way of forcing a re-download of cached dependencies when they were replaced by new ones. In addition, there was really no verification of downloads or cache. Now, changing a few lines at the top of the file will automagically force a cache update. 2020-03-27 13:37:27 +00:00			`#!/bin/sh -ex`

			`# BUILD_blablabla is Azure specific, so we wrap it for portability`
			`ARTIFACT_DIR="$BUILD_ARTIFACTSTAGINGDIRECTORY"`

			`# Remove unecessary files`
			`rm -f ./bin/rpcs3.exp ./bin/rpcs3.lib ./bin/rpcs3.pdb`

CI: Add workaround for exporting variables in Azure Using '-x' to echo commands in the shell causes the Azure process commands to be processed twice 2020-03-28 00:19:44 +00:00			`# Prepare compatibility database for packaging, as well as`
CI: Port Windows build to Azure Pipelines (#7757) * CI: Port Windows build to Azure Pipelines from Appveyor * CI: Split Windows build into scripts * CI: Remove Appveyor * CI: Add GitHub Release deployment to Azure Windows Build * VCS: Add full branch name function to rpcs3_version The STRINGIZE macro was a little awkward, and difficult to control at configure time. Since other version information is already included, the full branch name is now added as a function. It's runtime instead of compile-time checking, but it seems worth it. * CI: Overhaul Windows setup script Previously, there was no way of forcing a re-download of cached dependencies when they were replaced by new ones. In addition, there was really no verification of downloads or cache. Now, changing a few lines at the top of the file will automagically force a cache update. 2020-03-27 13:37:27 +00:00			`# certificate for ssl (auto-updater)`
			`curl -sL 'https://rpcs3.net/compatibility?api=v1&export' \| iconv -t UTF-8 > ./bin/GuiConfigs/compat_database.dat`
			`curl -sL 'https://curl.haxx.se/ca/cacert.pem' > ./bin/cacert.pem`

			`# Package artifacts`
			`7z a -m0=LZMA2 -mx9 "$BUILD" ./bin/*`

			`# Generate sha256 hashes`
			`# Write to file for GitHub releases`
			`sha256sum "$BUILD" \| awk '{ print $1 }' \| tee "$BUILD.sha256"`
			`echo "$(cat "$BUILD.sha256");$(stat -c %s "$BUILD")B" > GitHubReleaseMessage.txt`

			`# Move files to publishing directory`
			`mv -- "$BUILD" "$ARTIFACT_DIR"`
			`mv -- "$BUILD.sha256" "$ARTIFACT_DIR"`