Merge branch 'main' into multiple-service-deployers

Author: bhapas

.buildkite/hooks/post-checkout

@@ -47,7 +47,7 @@ MERGE_BRANCH="pr_merge_${PR_ID}"
 checkout_merge "${TARGET_BRANCH}" "${PR_COMMIT}" "${MERGE_BRANCH}"
 
 echo "Commit information"
-git log --format=%B -n 1
+git --no-pager log --format=%B -n 1
 
 # Ensure buildkite groups are rendered
 echo ""

.buildkite/pipeline.yml

@@ -2,6 +2,7 @@ env:
   SETUP_GVM_VERSION: 'v0.5.0' # https://github.com/andrewkroh/gvm/issues/44#issuecomment-1013231151
   DOCKER_COMPOSE_VERSION: "v2.17.2"
   ELASTIC_PACKAGE_COMPOSE_DISABLE_ANSI: "true"
+  ELASTIC_PACKAGE_COMPOSE_DISABLE_PULL_PROGRESS_INFORMATION: "true"
   KIND_VERSION: 'v0.17.0'
   K8S_VERSION: 'v1.26.0'
 

.buildkite/scripts/install_deps.sh

@@ -6,7 +6,7 @@ source .buildkite/scripts/tooling.sh
 
 add_bin_path(){
     mkdir -p ${WORKSPACE}/bin
-    export PATH="${PATH}:${WORKSPACE}/bin"
+    export PATH="${WORKSPACE}/bin:${PATH}"
 }
 
 with_kubernetes() {

Makefile

@@ -65,7 +65,7 @@ test-stack-command-86:
 	./scripts/test-stack-command.sh 8.6.2
 
 test-stack-command-8x:
-	./scripts/test-stack-command.sh 8.8.0-SNAPSHOT
+	./scripts/test-stack-command.sh 8.9.0-SNAPSHOT
 
 test-stack-command: test-stack-command-default test-stack-command-7x test-stack-command-800 test-stack-command-8x
 
@@ -89,15 +89,11 @@ test-check-packages-with-custom-agent:
 test-build-zip:
 	./scripts/test-build-zip.sh
 
-# TODO remove version once default one is 8.7.0 or higher
-# Setting environment variables manually
 test-install-zip:
-	./scripts/test-install-zip.sh -v 8.7.0-SNAPSHOT
+	./scripts/test-install-zip.sh
 
-# TODO remove version once default one is 8.7.0 or higher
-# Using elastic-package stack shellinit to populate environment variables
 test-install-zip-shellinit:
-	./scripts/test-install-zip.sh -v 8.7.0-SNAPSHOT -s
+	./scripts/test-install-zip.sh -s
 
 test-profiles-command:
 	./scripts/test-profiles-command.sh

README.md

@@ -100,6 +100,12 @@ These benchmarks allow you to benchmark any Ingest Node Pipelines defined by you
 
 For details on how to configure pipeline benchmarks for a package, review the [HOWTO guide](./docs/howto/pipeline_benchmarking.md).
 
+#### System Benchmarks
+
+These benchmarks allow you to benchmark an integration end to end.
+
+For details on how to configure system benchmarks for a package, review the [HOWTO guide](./docs/howto/system_benchmarking.md).
+
 ### `elastic-package benchmark generate-corpus`
 
 _Context: package_
@@ -116,6 +122,12 @@ _Context: package_
 
 Run pipeline benchmarks for the package.
 
+### `elastic-package benchmark system`
+
+_Context: package_
+
+Run system benchmarks for the package.
+
 ### `elastic-package build`
 
 _Context: package_
@@ -350,6 +362,8 @@ _Context: global_
 
 Use this command to spin up a Docker-based Elastic Stack consisting of Elasticsearch, Kibana, and the Package Registry. By default the latest released version of the stack is spun up but it is possible to specify a different version, including SNAPSHOT versions by appending --version <version>.
 
+You can run your own custom images for Elasticsearch, Kibana or Elastic Agent, see [this document](./docs/howto/custom_images.md).
+
 Be aware that a common issue while trying to boot up the stack is that your Docker environments settings are too low in terms of memory threshold.
 
 For details on how to connect the service with the Elastic stack, see the [service command](https://github.com/elastic/elastic-package/blob/main/README.md#elastic-package-service).
@@ -386,9 +400,11 @@ Use this command to boot up the stack locally.
 
 By default the latest released version of the stack is spun up but it is possible to specify a different version, including SNAPSHOT versions by appending --version <version>.
 
+You can run your own custom images for Elasticsearch, Kibana or Elastic Agent, see [this document](./docs/howto/custom_images.md).
+
 Be aware that a common issue while trying to boot up the stack is that your Docker environments settings are too low in terms of memory threshold.
 
-To expose local packages in the Package Registry, build them first and boot up the stack from inside of the Git repository containing the package (e.g. elastic/integrations). They will be copied to the development stack (~/.elastic-package/stack/development) and used to build a custom Docker image of the Package Registry.
+To expose local packages in the Package Registry, build them first and boot up the stack from inside of the Git repository containing the package (e.g. elastic/integrations). They will be copied to the development stack (~/.elastic-package/stack/development) and used to build a custom Docker image of the Package Registry. Starting with Elastic stack version >= 8.7.0, it is not mandatory to be available local packages in the Package Registry to run the tests.
 
 For details on how to connect the service with the Elastic stack, see the [service command](https://github.com/elastic/elastic-package/blob/main/README.md#elastic-package-service).