Sayali Gaikawad

Adding @prudhvigodithi to add more. Thanks!

[Triage] Needs discussion and proposal to move forward.

Hey @nknize , We have been brainstorming about this a bit. Adding thoughts here. There are multiple changes that can be categorized as refactoring such as package level changes (example...

Looks like `./gradlew assemble` is the right task to run from plugins point of view as it is light weight compared to `./gradlew build`. Tried below: 1. Publish opensearch to...

> Can we avoid using the timestamp? If we can always use your.group:your.artifact:1.0.0-latest, that can save effort for all plugin teams to coordinate versions and bumping snapshot versions by changing...

See POC for above approach here: https://github.com/opensearch-project/OpenSearch/pull/7899/files Clone the fork and checkout the branch. ``` git clone https://github.com/gaiksaya/OpenSearch.git cd OpenSearch && git checkout comp-check ``` Run below for specific plugins...

We have opened a GitHub issues in all plugin repositories to ensure they are ready for checking compatibility. See the linked issues above. This is to reduce false positives and...

Will let @nknize take the call. Notifying the failing/incompatible components is the next step. However, it can be tracked as a separate effort.

Hi @Flyingliuhub @seraphjiang , Thank you for creating the request. 1. The nightly playground is only responsible for deploying an already built tarballs onto the cluster. This set up does...

Closing this issue. Please see [README](https://github.com/opensearch-project/opensearch-devops/tree/main/nightly-playground#opensearch-nightly-playground) for other FAQs. Thanks!