From a7a7fb30c24f8d3b85471edf57640c5c2a3635e6 Mon Sep 17 00:00:00 2001 From: Prudhvi Godithi Date: Tue, 22 Mar 2022 14:08:14 -0400 Subject: [PATCH] Fix build.sh 404 error (#1802) Signed-off-by: pgodithi --- ONBOARDING.md | 2 +- src/build_workflow/README.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/ONBOARDING.md b/ONBOARDING.md index bbf4fb5f1c..5d7cac505e 100644 --- a/ONBOARDING.md +++ b/ONBOARDING.md @@ -30,7 +30,7 @@ Add the new plugin to the [opensearch-plugins meta](https://github.com/opensearc 1. Update a [manifest](/manifests) for a particular release to include your plugin. For example to be included in the 1.1.0 release, you would update [opensearch-1.1.0.yml](/manifests/1.1.0/opensearch-1.1.0.yml). We require your plugin name, repository url, and git ref that should be used. For unreleased versions this should be a branch in your repository. Once a release is cut, these refs will be updated to build from a tag or specific commit hash. -2. Create a `scripts/build.sh` if you have specific requirements that are not covered by the [default build.sh script](/scripts/default/build.sh) and commit it to your repository. +2. Create a `scripts/build.sh` if you have specific requirements that are not covered by the [default build.sh script](/scripts/default/opensearch/build.sh) and commit it to your repository. 3. Ensure your `build.sh` reads and passes along both `-Dbuild.snapshot=` and `-Dopensearch.version=` flags. Snapshot builds should produce a -SNAPSHOT tagged artifact for example `opensearch-plugin-1.1.0.0-SNAPSHOT.zip` where a release build of the same component would produce `opensearch-plugin-1.1.0.0.zip`. diff --git a/src/build_workflow/README.md b/src/build_workflow/README.md index 98f0bcd777..5dde4a0af4 100644 --- a/src/build_workflow/README.md +++ b/src/build_workflow/README.md @@ -76,7 +76,7 @@ The following options are available in `build.sh`. ### Custom Build Scripts -Each component build relies on a `build.sh` script that is used to prepare bundle artifacts for a particular bundle version that takes two arguments: version and target architecture. By default the tool will look for a script in [scripts/components](../../scripts/components), then in the checked-out repository in `build/build.sh`, then default to a Gradle build implemented in [scripts/default/build.sh](../../scripts/default/build.sh). +Each component build relies on a `build.sh` script that is used to prepare bundle artifacts for a particular bundle version that takes two arguments: version and target architecture. By default the tool will look for a script in [scripts/components](../../scripts/components), then in the checked-out repository in `build/build.sh`, then default to a Gradle build implemented in [scripts/default/opensearch/build.sh](../../scripts/default/opensearch/build.sh). ### Avoiding Rebuilds