mirror of
https://github.com/digital-asset/daml.git
synced 2024-09-20 01:07:18 +03:00
dba114a283
* Merge Maven uploads for different Scala versions It turns out Maven will abort an existing staging operation if you create a new one. This means our jobs race against each other. We could try to fix that by either sequencing the jobs in a clever way (annoying and can break things like rerunning if only parts failed), or by creating more profiles (unclear if you can even have two profiles for the same group id, even if you do, it’s annoying to merge). So in this PR I (grudgingly) merged both uploads into the Haskell script. This isn’t all bad: 1. It moves some logic from bash embedded in yaml string literals into Haskell code. 2. It duplicates some versions but it removes duplication in other places so overall not too much worse. 3. It does however, make things slower. We don’t run this stuff in parallel. That said, the release step is relatively small (< 5min) and it only runs on Linux. We could add CLI arguments to make the Scala versions configurable for local development. Given that this is blocking releases, I wanted to get something in that works first and then see what we need in that regard. changelog_begin changelog_end * . changelog_begin changelog_end * . changelog_begin changelog_end * . changelog_begin changelog_end |
||
|---|---|---|
| .. | ||
| cron | ||
| da-ghc-lib | ||
| docker | ||
| patch_bazel_windows | ||
| bash-lib.yml | ||
| build-unix.yml | ||
| build-windows.yml | ||
| build.yml | ||
| check-changelog.sh | ||
| clean-up.yml | ||
| clear-shared-segments-macos.yml | ||
| compatibility_ts_libs.yml | ||
| compatibility-windows.yml | ||
| compatibility.yml | ||
| configure-bazel.sh | ||
| daily_tell_slack.yml | ||
| dev-env-install.sh | ||
| dev-env-push.py | ||
| postgresql.conf | ||
| prs.yml | ||
| report-end.yml | ||
| report-start.yml | ||
| slack_user_ids | ||
| tell-slack-failed.yml | ||
| windows-diagnostics.ps1 | ||