Description
The release CI task encountered the same problem as #6832 multiple times. Namely the CI task was terminating abruptly at a random point, without an error message or apparent reason to do so. One time it happened on test_java11 task. Another time it happened on publish_release task which wrote some artefacts (but not all) to Sonatype. When I tried to re-run the task, it now terminated with a proper error once it tried to publish artefacts that were already published.
This diff shows which artefacts were not published (to the left, an example of a correct publish of 0.17.0-RC1, to the right, the broken publish of 0.16.0; versions replaced with a placeholder for clear diff). Precisely, the following artefacts were not published:
dotty-sbt-bridge to https://oss.sonatype.org/service/local/staging/deploy/maven2/ch/epfl/lamp/dotty-sbt-bridge/version-number/dotty-sbt-bridge-version-number-javadoc.jar
dotty-sbt-bridge to https://oss.sonatype.org/service/local/staging/deploy/maven2/ch/epfl/lamp/dotty-sbt-bridge/version-number/dotty-sbt-bridge-version-number-sources.jar
dotty-sbt-bridge to https://oss.sonatype.org/service/local/staging/deploy/maven2/ch/epfl/lamp/dotty-sbt-bridge/version-number/dotty-sbt-bridge-version-number.jar
dotty-sbt-bridge to https://oss.sonatype.org/service/local/staging/deploy/maven2/ch/epfl/lamp/dotty-sbt-bridge/version-number/dotty-sbt-bridge-version-number.jar.asc
dotty-sbt-bridge to https://oss.sonatype.org/service/local/staging/deploy/maven2/ch/epfl/lamp/dotty-sbt-bridge/version-number/dotty-sbt-bridge-version-number.pom
dotty-sbt-bridge to https://oss.sonatype.org/service/local/staging/deploy/maven2/ch/epfl/lamp/dotty-sbt-bridge/version-number/dotty-sbt-bridge-version-number.pom.asc
Hence, here, the 0.16.0
folder is absent at all.
So we need to manually publish the missing artefacts, and to investigate these CI failures. Unfortunately, I can't do it since I don't have access to the CI machine.