mirror of
https://github.com/digital-asset/daml.git
synced 2024-09-17 07:47:14 +03:00
89f0dad016
I _believe_ this is what has been tripping up the check-releses job for the past few days: while updating the signing key, I did not update the key fingerprint to match, and therefore trying to check any signature fails. The failure mode of the existing script is still pretty bad, regadless: looping on the same release until the hard drive is full is definitely not expected. Our retry policies are supposed to have time bounds, and failure should result in cleaning up the workdir. run-full-compat: true |
||
---|---|---|
.. | ||
cron | ||
docker | ||
assembly-split-release-artifacts.sh | ||
bash-lib.yml | ||
BUILD | ||
build-unix.yml | ||
build-windows.yml | ||
build.yml | ||
check-for-release-job.yml | ||
check-protobuf-stability.sh | ||
clean-up.yml | ||
clear-shared-segments-macos.yml | ||
compatibility_ts_libs.yml | ||
compatibility-windows.yml | ||
compatibility.yml | ||
configure-bazel.sh | ||
copy-unix-release-artifacts.sh | ||
copy-windows-release-artifacts.sh | ||
daily-snapshot.yml | ||
dev-env-install.sh | ||
dev-env-push.py | ||
fix-bazel-cache.yml | ||
job-variables.yml | ||
macOS.yml | ||
oracle_image | ||
postgresql.conf | ||
prs.yml | ||
publish-artifactory.sh | ||
publish-platform-independence-dar.yml | ||
remap-scala-test-short-names.ps1 | ||
report-end.yml | ||
report-start.yml | ||
slack_user_ids | ||
split-release-job.yml | ||
tell-slack-failed.yml | ||
upload-bazel-metrics.yml | ||
windows-diagnostics.ps1 |