[BUG] Gradle dependencies for 1.3.6 build tools are missing

[dbason]

What is the bug?

Plugins depending on 1.3.6 are failing to build

How can one reproduce the bug?

Try and build a plugin

What is the expected behavior?

Plugin should successfully build

What is your host/environment?

Github actions runner using actions/setup-java@v1

Do you have any additional context?

> Could not resolve all artifacts for configuration ':classpath'.
   > Could not find com.avast.gradle:gradle-docker-compose-plugin:0.12.1.
     Searched in the following locations:
       - file:/home/runner/.m2/repository/com/avast/gradle/gradle-docker-compose-plugin/0.12.1/gradle-docker-compose-plugin-0.12.1.pom
       - https://aws.oss.sonatype.org/content/repositories/snapshots/com/avast/gradle/gradle-docker-compose-plugin/0.12.1/gradle-docker-compose-plugin-0.12.1.pom
       - https://repo.maven.apache.org/maven2/com/avast/gradle/gradle-docker-compose-plugin/0.12.1/gradle-docker-compose-plugin-0.12.1.pom
       - https://plugins.gradle.org/m2/com/avast/gradle/gradle-docker-compose-plugin/0.12.1/gradle-docker-compose-plugin-0.12.1.pom
     Required by:
         project : > org.opensearch.gradle:build-tools:1.3.6
   > Could not find com.netflix.nebula:nebula-core:3.0.0.
     Searched in the following locations:
       - file:/home/runner/.m2/repository/com/netflix/nebula/nebula-core/3.0.0/nebula-core-3.0.0.pom
       - https://aws.oss.sonatype.org/content/repositories/snapshots/com/netflix/nebula/nebula-core/3.0.0/nebula-core-3.0.0.pom
       - https://repo.maven.apache.org/maven2/com/netflix/nebula/nebula-core/3.0.0/nebula-core-3.0.0.pom
       - https://plugins.gradle.org/m2/com/netflix/nebula/nebula-core/3.0.0/nebula-core-3.0.0.pom
     Required by:
         project : > org.opensearch.gradle:build-tools:1.3.6 > com.netflix.nebula:nebula-publishing-plugin:4.4.4

[reta]

Should be fixed by https://github.com/opensearch-project/OpenSearch/commit/7bbf0d11a0151078c6a3e478c1d2020a586b3e3e, it seems like there in an incident with Gradle Plugins portal:

Unfortunately, this means artifacts that were only available on JCenter/Bintray and were never migrated to Maven Central will not be available from the Plugin Portal. If you are using dependency verification, you may also notice different artifact checksums for libraries that were re-uploaded to Maven Central.

https://status.gradle.com/

[dblock]

I believe this is fixed, closing.