Add instructions about using jenkins auth (#5429)

Signed-off-by: Sayali Gaikawad <gaiksaya@amazon.com>

Author: gaiksaya

docs/Building-an-OpenSearch-and-OpenSearch-Dashboards-Distribution.md

@@ -12,12 +12,18 @@ Manifests are the single source of truth for building and testing the distributi
 
 ### Building from Source
 
-Input manifests are the source of building the distributions. Each input manifest also contains the docker image that can be used to build these distributions and avoid installing bunch of packages. See [CI image details](https://github.com/opensearch-project/opensearch-build/blob/main/manifests/3.0.0/opensearch-3.0.0.yml#L8-L9) in the manifest.
+Input manifests are the source of building the distributions. Each input manifest also contains the docker image that can be used to build these distributions and avoid installing bunch of packages. See [CI image details](https://github.com/opensearch-project/opensearch-build/blob/main/manifests/3.0.0/opensearch-3.0.0.yml#L8-L9) in the manifest along with java version used to build the distribution.
 
 To run locally:
 ```bash
-  docker run -it -d --entrypoint bash opensearchstaging/ci-runner:ci-runner-centos7-opensearch-build-v2 -e JAVA_HOME=/opt/java/openjdk-20
+  docker run -it --entrypoint bash opensearchstaging/ci-runner:ci-runner-al2-opensearch-build-v1
 ```
+Once you are inside the container set JAVA_HOME as stated in the [manifest](https://github.com/opensearch-project/opensearch-build/blob/main/manifests/3.0.0-alpha1/opensearch-3.0.0-alpha1.yml#L10):
+```
+export JAVA_HOME=/opt/java/openjdk-21
+git clone https://github.com/opensearch-project/opensearch-build.git
+```
+
 Then build from source:
 
 ```bash
@@ -67,7 +73,8 @@ OpenSearch is often released with changes in `opensearch-min`, and no changes to
 
 #### CI/CD Environment
 
-We use Jenkins as our CI/CD infrastructure to build, test and release OpenSearch and OpenSearch Dashboards. Access it [here](https://build.ci.opensearch.org/)
+We use Jenkins as our CI/CD infrastructure to build, test and release OpenSearch and OpenSearch Dashboards.
+[OpenSearch CI/CD system](https://build.ci.opensearch.org/) now requires authentication for readOnly access as well. Please proceed to login using your GitHub.
 
 We build, assemble, and test our artifacts on docker containers. We provide docker files in [docker/ci](https://github.com/opensearch-project/opensearch-build/tree/main/docker/ci) folder, and images on [staging docker hub repositories](https://hub.docker.com/r/opensearchstaging/ci-runner/). All Jenkins pipelines can be found in [jenkins](https://github.com/opensearch-project/opensearch-build/tree/main/jenkins). The Jenkins is deployed using infrastructure as a Code and can be found in [opensearch-ci](https://github.com/opensearch-project/opensearch-ci) repository.
 

docs/OpenSearch-Project-Build-System-Quick-Overview.md

@@ -22,6 +22,8 @@ The **Standalone Component Release**, on the other hand, primarily utilizes GitH
 
 This group consists of workflows that clone, build, assemble, and store OpenSearch/OpenSearch-Dashboards and its related plugin artifacts in one take.
 
+__Note: [OpenSearch CI/CD system](https://build.ci.opensearch.org/) now requires authentication for readOnly access as well. Please proceed to login using your GitHub.__
+
 ##### **2.1.1.1 Check-for-build**
 The "[check-for-build](https://build.ci.opensearch.org/job/check-for-build/)" workflow is used to periodically check out the latest change in opensearch-project repositories and is usually set to trigger every 60 minutes. It compares the head commit of the given branch in all component repositories with the stored caches on the staging S3 bucket. If any discrepancies are identified, it would then trigger the build/assemble workflows, specifically the "[distribution-build-opensearch](https://build.ci.opensearch.org/job/distribution-build-opensearch/)" and "[distribution-build-opensearch-dashboards](https://build.ci.opensearch.org/job/distribution-build-opensearch-dashboards/)" workflows. 
 

docs/Releasing-the-Distribution.md

@@ -58,6 +58,8 @@ These are the issues created by automation with the distribution build and integ
 
 #### Build Workflows
 
+__Note: [OpenSearch CI/CD system](https://build.ci.opensearch.org/) now requires authentication for readOnly access as well. Please proceed to login using your GitHub.__
+
 | Workflow                                                                                                                      | Description         |
 | ----------------------------------------------------------------------------------------------------------------------------- | ------------------- |
 | [Check for Build](https://build.ci.opensearch.org/job/check-for-build/)                                                       | Workflow that periodically triggers the distribution workflows using parameterized cron. |

docs/Testing-the-Distribution.md

@@ -151,6 +151,8 @@ The `build` workflow automates the process to generate all OpenSearch and OpenSe
 
 ### Integration tests
 
+__Note: [OpenSearch CI/CD system](https://build.ci.opensearch.org/) now requires authentication for readOnly access as well. Please proceed to login using your GitHub account.__
+
 The integration tests for OpenSearch are run via [integ-test](https://build.ci.opensearch.org/view/Test/job/integ-test/) job and for OpenSearch-Dashboards via [integ-test-opensearch-dashboards](https://build.ci.opensearch.org/view/Test/job/integ-test-opensearch-dashboards/) job. These jobs are mainly triggered via distribution build jobs after a distribution is created successfully. They are also triggered manually when required such as during releases or via cronjobs.
 The job reads the build artifact composition from the associated manifest files and spins up parallel, independent integrationTest runs for each component built inside the artifact. For instance, if the artifact is a full distribution, which has all OpenSearch plugins, the job will kick off integration test suite for each individual plugin. Each plugin is run on an independent cluster and in independent container. After the test runs are complete, a test-report is generated using [report-workflow](https://github.com/opensearch-project/opensearch-build/tree/main/src/report_workflow).