Barani

@reta can you please help us understand the scope of packaging / distro test? We are planning to create automated validation pipelines for RPM builds as part of https://github.com/opensearch-project/opensearch-build/issues/1244 but...

As mentioned by @gaiksaya, we would focus more on executing tests at distribution level and not at repo level. Having said that, we dont have plans to add additional distribution...

@reta @owaiskazi19 Can you track this issue as part of your gradle check improvements plan?

@peterzhuamazon and @rishabh6788 are working on moving the gradle check to public Jenkins. @reta @owaiskazi19 Please make the required changes to support your requirements once the migration is complete

@reta @saratvemulapalli Before we include this as part of Gradle check, we need to fix the existing flaky tests. Do you have any plans to improve the current gradle check...

@kavilla @tianleh Is this still an open issue?

@seanneumann @kavilla This needs to be prioritized to improve the build generation velocity. Can you please prioritize this as soon as possible?

@kavilla As far as I know, this is needed for granular build generation process work that is described [here](https://github.com/opensearch-project/opensearch-build/issues/1906). @peterzhuamazon, you mentioned that we can overcome this blocker by Bootstrapping...

The bootstrapping also causes the core [build](https://build.ci.opensearch.org/job/distribution-build-opensearch-dashboards/5360/consoleFull) to fail if any of the plugins fail to build as well ``` ERROR [bootstrap] failed: ERROR Error: Command failed with exit code...

Some additional requirements to consider: - Ability to view cluster / node / memory level stats during benchmarking - Support for distributed workloads for large clusters on multiple machines. -...