Gary Verhaegen 433f484188 stop producing/publishing the Bazel execution logs (#4527) ... They can weigh close to 1GB, and the internal Azure networks are unreliable enough that this adds up significant amounts of time to our already slow CI pipeline (usually around a minute, but I've seen at least one case where it took almost 28 minutes). Given that we pretty much never look a them, 🔥. CHANGELOG_BEGIN CHANGELOG_END		2020-02-14 14:34:01 +01:00
..
azure-cleanup	update copyright notices to 2020 (#3939)	2020-01-02 21:21:13 +01:00
cron	standard change extract script (#4416)	2020-02-07 15:16:03 +01:00
docker/daml-sdk	daml-sdk container improvements (#3902)	2019-12-19 08:31:15 +01:00
build-unix.yml	stop producing/publishing the Bazel execution logs (#4527)	2020-02-14 14:34:01 +01:00
build-windows.yml	stop producing/publishing the Bazel execution logs (#4527)	2020-02-14 14:34:01 +01:00
check-changelog.sh	check for changelog (#3963)	2020-01-07 17:19:50 +01:00
configure-bazel.sh	update copyright notices to 2020 (#3939)	2020-01-02 21:21:13 +01:00
dev-env-install.sh	Update CI nix version (#4443)	2020-02-07 15:05:52 +00:00
dev-env-push.py	update copyright notices to 2020 (#3939)	2020-01-02 21:21:13 +01:00
release.sh	remove jfrog credentials after use (#4522)	2020-02-14 13:54:28 +01:00
report-end.yml	add copyright headers to yml files (#4407)	2020-02-06 12:54:07 +01:00
report-start.yml	add copyright headers to yml files (#4407)	2020-02-06 12:54:07 +01:00
slack_user_ids	Subscribe to CI notifications (#4494)	2020-02-12 17:36:03 +00:00
tell-slack-failed.yml	add copyright headers to yml files (#4407)	2020-02-06 12:54:07 +01:00
windows-diagnostics.ps1	windows: CI agent diagnostics (#1146)	2019-05-15 11:59:56 +02:00