We are separating nightly builds by test suite (fleet, k8s-autodiscover, helm) but the k8s one include scenarios for the elastic-agent.

As confirmed with the team, the nightly builds for fleet test suite should include the k8s-autodiscover scenarios for the elastic-agent.

Implementation

We are controlling which test suite to run on Jenkins, using the runTestSuites parameter https://github.com/elastic/e2e-testing/blob/main/.ci/Jenkinsfile#L44, as a comma-separated list of suites.

Each test suite is driven by this file: https://github.com/elastic/e2e-testing/blob/main/.ci/.e2e-tests.yaml, which defines a test suite and its parallel stages using scenarios and tags (See https://github.com/elastic/e2e-testing/blob/main/.ci/.e2e-tests.yaml#L73-L77)

At this moment, the Jenkinsfile processes that YAML file here: https://github.com/elastic/e2e-testing/blob/main/.ci/Jenkinsfile#L247-L263

I think we would need a way to also pass specific scenarios (i.e. k8-autodiscover:elastic-agent)

cc/ @adam-stokes