Add CCR integ tests to the test manifest (opensearch-project#2107)

Signed-off-by: Ankit Kala <[email protected]>

Author: ankitkala

DEVELOPER_GUIDE.md

@@ -20,6 +20,7 @@
     - [Run Tests](#run-tests-1)
       - [Regression Tests](#regression-tests)
       - [Testing in Jenkins](#testing-in-jenkins)
+      - [Integ Tests in Jenkins](#integ-tests-in-jenkins)
 
 # Developer Guide
 
@@ -288,3 +289,8 @@ Make your code changes in a branch, e.g. `jenkins-changes`, including to any of
 * Script path: `tests/jenkins/jobs/Build_DryRun_Jenkinsfile`
 
 You can now iterate by running the job in Jenkins, examining outputs, and pushing updates to GitHub.
+
+#### Integ Tests in Jenkins
+- Opensearch bundle build executes the integration tests for the opensearch as well as plugins. 
+- To add integ tests for a new plugin, add the plugin in the latest version [test manifest](manifests/2.0.0/opensearch-2.0.0-test.yml).
+- The test execution is triggered by the [integtest.sh](scripts/default/integtest.sh). In case a custom implementation is required, plugin owner can add that script in their own repo and [script_finder](src/paths/script_finder.py) will pick that up over the default script.

manifests/2.0.0/opensearch-2.0.0-test.yml

@@ -38,6 +38,12 @@ components:
       additional-cluster-configs:
         plugins.destination.host.deny_list: [10.0.0.0/8, 127.0.0.1]
 
+  - name: cross-cluster-replication
+    integ-test:
+      test-configs:
+        - with-security
+        - without-security
+
   - name: notifications
     working-directory: notifications
     integ-test: