Update output message from localDistro to include full path to OpenSearch installation#20924

Open

cwperks wants to merge 2 commits intoopensearch-project:mainfrom

cwperks:local-distro-path

Member

cwperks commented Mar 19, 2026 •

edited

Loading

Description

This is a small quality of life PR to include the full path to the OpenSearch distribution when running ./gradlew localDistro

Before:

> ./gradlew localDistro

OpenSearch distribution installed to /Users/cwperx/Projects/opensearch/OpenSearch/build/distribution/local.

After

> ./gradlew localDistro -Dbuild.snapshot=true

OpenSearch distribution installed to /Users/cwperx/Projects/opensearch/OpenSearch/build/distribution/local/opensearch-3.6.0-SNAPSHOT

> ./gradlew localDistro -Dbuild.snapshot=false

OpenSearch distribution installed to /Users/cwperx/Projects/opensearch/OpenSearch/build/distribution/local/opensearch-3.6.0

Its a command I run fairly often and would be nice to copy and paste the full directory from the output of the gradle task.

Check List

Functionality includes testing.
API changes companion pull request created, if applicable.
Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.


          Update output message from localDistro to include full path to OpenSe…

10f356c

…arch installation

Signed-off-by: Craig Perkins <cwperx@amazon.com>

cwperks requested a review from a team as a code owner

March 19, 2026 15:14

cwperks added skip-changelog and removed skip-changelog labels

andrross approved these changes

View reviewed changes

Contributor

github-actions bot commented Mar 19, 2026

❌ Gradle check result for 10f356c: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Contributor

github-actions bot commented Mar 19, 2026

❌ Gradle check result for 10f356c: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

This was referenced Mar 19, 2026

[AUTOCUT] Gradle Check Flaky Test Report for IndicesRequestCacheIT #14288

Open

[AUTOCUT] Gradle Check Flaky Test Report for WarmIndexSegmentReplicationIT #18157

Open

Contributor

github-actions bot commented Mar 19, 2026

❌ Gradle check result for 10f356c: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Contributor

github-actions bot commented Mar 20, 2026

❌ Gradle check result for 10f356c: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

opensearch-ci-bot mentioned this pull request

[AUTOCUT] Gradle Check Flaky Test Report for AwarenessAllocationIT #17930

Open

Contributor

github-actions bot commented Mar 20, 2026

❌ Gradle check result for 10f356c: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

reta reviewed

View reviewed changes

gradle/local-distribution.gradle Outdated Show resolved Hide resolved


          Update gradle/local-distribution.gradle

99b2bdb

Co-authored-by: Andriy Redko <andriy.redko@aiven.io>
Signed-off-by: Craig Perkins <craig5008@gmail.com>

reta approved these changes

View reviewed changes

Contributor

github-actions bot commented Mar 20, 2026

❌ Gradle check result for 99b2bdb: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Contributor

github-actions bot commented Mar 20, 2026

❌ Gradle check result for 99b2bdb: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels