changes to serverless pipelines (#2909)

* changes to serverless pipelines

* Update .buildkite/pipeline.tests-staging.yaml

* Update .buildkite/pipeline.fleet-server-tests.yaml

* updated catalog-info

* updated team name

* rename to fleet-smoke-tests

---------

Co-authored-by: Ramon Butter <[email protected]>

.buildkite/pipeline.fleet-server-tests.yaml

@@ -0,0 +1,25 @@
+# This pipeline serves as the entry point for your service's quality gates definitions. When
+# properly configured, it will be invoked automatically as part of the automated
+# promotion process once a new version was rolled out in one of the various cloud stages.
+#
+# The updated environment is provided via ENVIRONMENT variable. The seedling
+# step will branch and execute pipeline snippets at the following location:
+# .buildkite/pipeline.tests-qa.yaml
+# .buildkite/pipeline.tests-staging.yaml
+# .buildkite/pipeline.tests-production.yaml
+#
+# Docs: https://docs.elastic.dev/serverless/qualitygates
+
+env:
+  ENVIRONMENT: ${ENVIRONMENT?}
+  TEAM_CHANNEL: "#fleet-cloud-services"
+
+steps:
+  - label: ":pipeline::grey_question::seedling: Trigger service tests for ${ENVIRONMENT}"
+    command: "make -C /agent run-environment-tests"
+    agents:
+      image: "docker.elastic.co/ci-agent-images/quality-gate-seedling:0.0.2"
+
+notify:
+  - slack: "${TEAM_CHANNEL}"
+    if: build.branch == "main" && build.state == "failed"

.buildkite/pipeline.tests-qa.yaml

@@ -0,0 +1,12 @@
+# These pipeline steps constitute the quality gate for your service within the QA environment.
+# Incorporate any necessary additional logic to validate the service's integrity. A failure in
+# this pipeline build will prevent further progression to the subsequent stage.
+
+steps:
+  - label: ":rocket: Run Smoke tests"
+    trigger: "fleet-smoke-tests"
+    build:
+      message: "${BUILDKITE_MESSAGE}"
+      env:
+        ENVIRONMENT: ${ENVIRONMENT}
+

.buildkite/pipeline.tests-staging.yaml

@@ -0,0 +1,11 @@
+# These pipeline steps constitute the quality gate for your service within the Staging environment.
+# Incorporate any necessary additional logic to validate the service's integrity. A failure in
+# this pipeline build will prevent further progression to the subsequent stage.
+
+steps:
+  - label: ":rocket: Run Smoke tests"
+    trigger: "fleet-smoke-tests"
+    build:
+      message: "${BUILDKITE_MESSAGE}"
+      env:
+        ENVIRONMENT: ${ENVIRONMENT}

catalog-info.yaml

@@ -115,7 +115,7 @@ metadata:
   description: Pipeline tests the service integration in a specific environment
   links:
     - title: Pipeline
-      url: https://buildkite.com/elastic/fleet-server
+      url: https://buildkite.com/elastic/fleet-server-tests
 spec:
   type: buildkite-pipeline
   owner: group:fleet
@@ -128,12 +128,13 @@ spec:
       description: fleet-server environment tests
     spec:
       repository: elastic/fleet-server
-      pipeline_file: .buildkite/pipeline.service-tests.yml
+      pipeline_file: .buildkite/pipeline.service-tests.yaml
       branch_configuration: "main"
       provider_settings:
         build_pull_requests: false
+        trigger_mode: none
       teams:
-        cloud-k8s-region:
+        ingest-fp:
           access_level: MANAGE_BUILD_AND_READ
         cloud-tooling:
           access_level: MANAGE_BUILD_AND_READ