Ensure compatibility check readiness

[gaiksaya]

Coming from opensearch-project/opensearch-devops#114 (comment)

Overview

In order to detect the breaking changes between OpenSearch (core/min) and plugins, we recently onboarded a compatibility check gradle task with OpenSearch. See the pull request.
The task is dependent on publishToMavenLocal task (that publishes the core engine artifacts to maven local). It then clones the plugins' repository in temporary directory and runs ./gradlew assemble.

Action Items

In order to avoid false positives and false negatives, we need to make sure the tasks in below checklist are complete:

• The build.gradle file in this repository uses mavenLocal() as the first entry in repositories() section. This will ensure that when core/min dependencies are published to maven local, gradle looks at maven local first and gets the required core/min dependencies rather than fetching from snapshots or maven central resulting in false checks.
• ./gradlew assemble task passes for the plugin build. If the task itself is broken, checking compatitibility is irrelevant as it will always fail.

Please close this issue once the above checklist is complete.

Thanks!

[bbarani]

@vamshin can you please provide an update?

[vamshin]

@bbarani Heemin will take look and provide update. Thanks

[heemin32]

1. Verified mavenLocal() is first entry in repositories() in both main and 2.x branch.
2. ./gradlew assemble succeeded in main branch. It failed in 2.x branch but it is because build is failing which we need to fix before 2.9 release.

[heemin32]

./gradlew assemble succeeded in 2.x branch after merging #315