This is a master tracking issue issue for auditing which E2E test pipelines need to remain enabled.

Beats CI pipelines

Fleet CI pipelines

⚠️ If you are listed as a stakeholder, we would like to know the following:

1. Should the pipeline be removed from the CI or should it remain?
   1.1 If the pipeline remains and is broken, what is the link to an issue tracking a fix?
   1.2 If the pipeline should remain, how is it monitored by the team to ensure that build artifacts are not produced when the tests fail?

Next steps

Proposed pipeline criteria

I am proposing that we remove all pipelines which do not meet any of the following criteria:

1. Necessary for the ongoing health of the E2E test suite itself
2. Used by a product team as a quality gateway. Concretely, this means that a failing test blocks a PR from being merged or a build artifact from being produced.
3. Exist to ensure the quality of a supported product.

Timeline

1. All existing E2E pipelines have stakeholders assigned no later than: October 1, 2022
2. All stakeholder agree upon proposed pipeline criteria no later than: October 20, 2022
3. Non-confirming pipelines will be removed from Jenkins and code will be removed from the E2E test suite beginning on: Nov 1st, 2022

Related efforts

There is a separate effort to try and reduce the scope of E2E testing back to a point where stability can be maintained, but it is limited to tests for the Agent. That effort can be found here: elastic/elastic-agent#1174