Skip to content
This repository has been archived by the owner on Sep 17, 2024. It is now read-only.

[k8s Autodiscover] SUpport running test suite agains Beats PRs or local filesystem #1106

Closed
mdelapenya opened this issue Apr 28, 2021 · 2 comments · Fixed by #1115
Closed

[k8s Autodiscover] SUpport running test suite agains Beats PRs or local filesystem #1106

mdelapenya opened this issue Apr 28, 2021 · 2 comments · Fixed by #1115
Assignees
@mdelapenya
Labels
area:test Anything related to the Test automation priority:blocker Work is on-hold for a product team, business is at risk until resolution of issue size:M 1-5 days Team:Automation Label for the Observability productivity team Team:Integrations Label for the Integrations team triaged Triaged issues will end up in Backlog column in Robots GH Project

Comments

@mdelapenya
Copy link
Contributor

mdelapenya commented Apr 28, 2021 •
edited
Loading

The same way we do for other test suites (fleet and metricbeat) we'd like to test beats' PRs/branches or binaries created from the local build in Beats.

For that reason, we'd need to detect if the build was triggered by a PR/branch from Beats, or using local file system, and load the Docker image for:

  • metricbeat
  • filebeat
  • heartbeat
    in Kind's runtime, using kind load image-archive $theFile.tar

cc/ @jsoriano
@mdelapenya mdelapenya added Team:Automation Label for the Observability productivity team area:test Anything related to the Test automation priority:blocker Work is on-hold for a product team, business is at risk until resolution of issue size:M 1-5 days triaged Triaged issues will end up in Backlog column in Robots GH Project Team:Integrations Label for the Integrations team labels Apr 28, 2021
@mdelapenya mdelapenya self-assigned this Apr 28, 2021
@mdelapenya
Copy link
Contributor Author

This is currently impacting Beats PRs/branches

@jsoriano
Copy link
Member

Related to elastic/beats#25307

@mdelapenya mdelapenya mentioned this issue Apr 30, 2021
Merged
8 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@mdelapenya mdelapenya

Labels
area:test Anything related to the Test automation priority:blocker Work is on-hold for a product team, business is at risk until resolution of issue size:M 1-5 days Team:Automation Label for the Observability productivity team Team:Integrations Label for the Integrations team triaged Triaged issues will end up in Backlog column in Robots GH Project
Projects
None yet
Milestone
No milestone
2 participants
@jsoriano @mdelapenya