Open pierrehilbert opened 3 weeks ago
@pierrehilbert will these EA versions be available as SNAPSHOTS on ESS so we can incorporate them into our automated smoke tests that we conduct for every version? We can schedule a brief manual test for our next iteration (Sep 9th-Sept 29th), but I'm eager to have this incorporated in automated testing, as my assumption is that there are not tests run by the EA team that concern APM Server functionality?
Unfortunately for now the Staging API is not reflecting the Independent Agent Release there but this is a topic we are working with the Release team as we currently only have it if we are start the process up to production. We currently have an opened issue to do it for our Agent upgrade tests and once it will be done, you could probably do something similar for APM.
Issue
Validate that the Independent Agent Release binary is not having side effect on running APM.
Context
To be able to fix critical issue faster, we worked on a new process allowing us to release a new Agent version without being coupled to Elastic Stack releases: this process is called Independent Agent Release.
In the context of the Independent Agent Release, we are packaging a new Elastic Agent for an existing patch version. This package contains opt-in and opt-out artifacts: APM is an opt-out artifact.
Being opt-out means that we are taking the last released version of the artifact for this patch version and not the last build version. In the example bellow, 8.14.3 artifacts are the opt-out artifacts:
How to test
http://staging.elastic.co/independent-agent/8.14.3+build202408141002/downloads/
as the source URL.8.14.3+build202408141002
version in Fleet UI.