mirror of
https://github.com/digital-asset/daml.git
synced 2024-11-04 00:36:58 +03:00
ca976fe3d7
Because there's no reason not to. The only obstacle to automating the normal release process is that we need an explicit manual validation step for our audit log when creating a release, but split-releases are created in the Assemblty repo, so we can have the audit log over there. The diff is going to be very messy because there's a lot of stuff moving around. The only thing that is not just moving a job to a separate file is the `ci/daily-snapshot.yml` file, which is 100% new and is meant as a new Azure Pipelines entrypoint (which I will create after this gets approved). I have made a reasonable effort to create individual commits that simplify reviewing, but I expect it's still going to be kind of a mess. I'm open to opening separate PRs to ~bump my stats~ move one job at a time if that makes reviewing (and testing) easier. CHANGELOG_BEGIN CHANGELOG_END |
||
|---|---|---|
| .. | ||
| cron | ||
| da-ghc-lib | ||
| docker | ||
| patch_bazel_windows | ||
| assembly-split-release-artifacts.sh | ||
| bash-lib.yml | ||
| BUILD | ||
| build-unix.yml | ||
| build-windows.yml | ||
| build.yml | ||
| check-changelog.sh | ||
| 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 | ||
| job-variables.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 | ||