Hi,
due to the bug introduced to the 7.x (and 7.12) branch, the latest snapshot is failing. The bug has been fixed in #24163 and #24161 , but the Docker image hasn't been released due to other issues in the unified release process.
With this problem in SNAPSHOT the package development is blocked for few days in elastic/integration, elastic/elastic-package (all statuses are red). We can hardcode the correct Docker image in both repos, but it means for us a lot of operational work - start a day by reviewing all Beats branches and check if there might be a blocker (failed build), then update a map of hardcoded image references in elastic-package (for 7.13, 7.12, 7.11).
The goal of this issue is to figure out and implement a way of publishing Agent's images independently from other potentially problematic parties.
cc @andresrc @ph @ruflin @ycombinator
Hi,
due to the bug introduced to the 7.x (and 7.12) branch, the latest snapshot is failing. The bug has been fixed in #24163 and #24161 , but the Docker image hasn't been released due to other issues in the unified release process.
With this problem in SNAPSHOT the package development is blocked for few days in elastic/integration, elastic/elastic-package (all statuses are red). We can hardcode the correct Docker image in both repos, but it means for us a lot of operational work - start a day by reviewing all Beats branches and check if there might be a blocker (failed build), then update a map of hardcoded image references in elastic-package (for 7.13, 7.12, 7.11).
The goal of this issue is to figure out and implement a way of publishing Agent's images independently from other potentially problematic parties.
cc @andresrc @ph @ruflin @ycombinator