-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: pass BEAT_VERSION when running E2E tests #26291
Conversation
💔 Build Failed
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪Log outputExpand to view the last 100 lines of log output
💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if this could be done with the props file feature we added back in the days.
See #22027
In a nutshell:
- beats:Jenkinsfile generates a properties file with (git sha, beats-version...), then the downstream jobs get triggered and read the file if possible (otherwise, use the previous behaviour).
This helps to ensure the git sha and versioning is passed correctly between downstream jobs and we don't use the latest
archived artifacts in the Google Storage but the specific commit id .
This process was put in place for the main-pipeline
-> packaging
-> beats-tester
but IIRC we didn't do it for the e2e-testing
Other than that, It looks ok
I'm not sure if I follow you about that file :S What we are trying to solve is the need to get the real version behind a commit-sha: i.e. the commit |
(cherry picked from commit ea84a3b)
(cherry picked from commit ea84a3b)
* master: (32 commits) [Metricbeat] Change Account ID to Project ID in `gcp.billing` module (elastic#26412) update libbeat fields.ecs.yml file and ecsVersion to 1.10.0 (elastic#26121) [Filebeat] Update AWS ELB ingest pipeline (elastic#26441) [FIlebeat] add strict_date_optional_time_nanos date format to PanOS module (elastic#26158) Fix the irregular and typo on prometheus module. (elastic#25726) [Filebeat] Parse additonal debug data fields for Okta module (elastic#25818) fix: update MSSQL Server linux image's Docker registry (elastic#26440) Update indexing.go godocs (elastic#26408) Do not close filestream harvester if an unexpected error is returned when close.on_state_change.* is enabled (elastic#26411) Add support for copytruncate method when rotating input logs with an external tool in `filestream` input (elastic#23457) Allow fields with ip_range datatype (elastic#26444) Add Anomali ThreatStream support to threatintel module (elastic#26350) fix: use the right param type (elastic#26469) [Automation] Update elastic stack version to 8.0.0-7640093f for testing (elastic#26460) Set SM Filebeat modules as GA (elastic#26226) Fix rfc5464 date parsing in the syslog input (elastic#26419) Add linked account information into billing metricset (elastic#26285) [Filebeat] Update HA Proxy log grok patterns (elastic#25835) disable metricbeat logstash test_node_stats (elastic#26436) chore: pass BEAT_VERSION when running E2E tests (elastic#26291) ...
(cherry picked from commit ea84a3b) Co-authored-by: Manuel de la Peña <[email protected]>
(cherry picked from commit ea84a3b) Co-authored-by: Manuel de la Peña <[email protected]>
@Mergifyio backport 7.14 |
(cherry picked from commit ea84a3b)
Command
|
…6889) * chore: pass BEAT_VERSION when running E2E tests (#26291) (cherry picked from commit ea84a3b) * fix: proper param type Co-authored-by: Jaime Soriano Pastor <[email protected]> Co-authored-by: Manuel de la Peña <[email protected]> Co-authored-by: Jaime Soriano Pastor <[email protected]>
…) (elastic#26889) * chore: pass BEAT_VERSION when running E2E tests (elastic#26291) (cherry picked from commit b35a1bf) * fix: proper param type Co-authored-by: Jaime Soriano Pastor <[email protected]> Co-authored-by: Manuel de la Peña <[email protected]> Co-authored-by: Jaime Soriano Pastor <[email protected]>
What does this PR do?
It passes the BEAT_VERSION to the downstream execution of the E2E tests:
Why is it important?
In elastic/e2e-testing#1256, the e2e are adding the ability of using the expected version for a Beat. We want to adhere to that contract
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist