CI: enable AWS cloud testing on a PR basis if changes in certain files#29047
CI: enable AWS cloud testing on a PR basis if changes in certain files#29047v1v merged 12 commits intoelastic:masterfrom
Conversation
|
This pull request does not have a backport label. Could you fix it @v1v? 🙏
NOTE: |
|
/test |
|
|
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
…ws-on-file-changes * upstream/master: Fix discovery of Nomad allocations (elastic#28700) Add null (`\u0000`) as a valid line terminator (elastic#28998) Remove `logging.files.suffix` option and always use datetime suffixes (elastic#28927) x-pack/filebeat/module: add note for default var.input (elastic#28324) Fix AccessList & AccessMask processing in security data_stream (elastic#29016) [Metricbeat] Fix wrong mapping on "info" subkey (elastic#28782) ci: daily/weekly jobs (elastic#29050) [mergify] report open backported PRs once a week (elastic#28964)
|
@aspacca , are you familiar with the error: See logs That particular execution theoretically configured the environment variables with the credentials, but just in case it's something that somehow is not correct in terraform. |
|
/test |
|
that's very strange, the terraform file (https://github.com/elastic/beats/blob/master/x-pack/filebeat/input/awss3/_meta/terraform/main.tf) was created 3 months ago and two weeks ago we just added some extra resources. |
|
/test |
|
also I see in the last test run |
It won't as long as there are flaky tests in the pythonIntegTest for metricbeat. :/ |
|
There are genuine test failures in the |
There are genuine test failures for the integ tests therefore the `extended` stage cannot be executed.
…ws-on-file-changes * upstream/master: override host on statsd metricset (elastic#29103) Skip config check in autodiscover for duplicated configurations (elastic#29048) Change "filebeat.config.modules.enabled" to "true" (elastic#28769) Remove deprecated spool queue from Beats (elastic#28869) Add `beat` field back to beat.stats (elastic#29094) Revert "Move labels and annotations under kubernetes.namespace. (elastic#27917)" (elastic#29069) heartbeat: remove w2008 in the CI (elastic#29093) Remove deprecated `--template` and `--index-policy` flags (elastic#28870) Fix parsing of apache trace log levels (elastic#28717) [Elastic-Agent] IUse itnernal port for local fleet server (elastic#28993) [Heartbeat] Log error on dupe monitor ID instead of strict req (elastic#29041) Enable pprof for elastic-agent and beats (elastic#28983)
|
It worked now GitHub checksNew stagesx-pack-filebeat cloud AWSPrerequisites: configure terraform x-pack-metricbeat cloud AWSPrerequisites: configure terraform @aspacca , can you confirm if those logs are reporting the correct output? |
|
@v1v I've checked terraform apply logs and they are correct |
* upstream/master: (577 commits) Remove Journalbeat (elastic#29131) Add note that there is no warranty or support for generator code (elastic#28797) packetbeat: preparation for npcap addition (elastic#29017) Use the generic helper for opening file to read in filestream (elastic#29180) Workflow for macos (elastic#29174) Fix `decode_json_fields` processor to always add error key (elastic#29107) Workflow for macos (elastic#29156) Fix agent download timeout values in yaml files (elastic#29039) Added workflow file for builds with macos (elastic#29148) CI: enable AWS cloud testing on a PR basis if changes in certain files (elastic#29047) Remove links to Journalbeat (elastic#29134) Fix rds metadata in cloudwatch metricset (elastic#29106) [mergify]: notify conflicts in PRs that are still open (elastic#29122) Use NamedWatcher in Agent's k8s provider (elastic#29095) override host on statsd metricset (elastic#29103) Skip config check in autodiscover for duplicated configurations (elastic#29048) Change "filebeat.config.modules.enabled" to "true" (elastic#28769) Remove deprecated spool queue from Beats (elastic#28869) Add `beat` field back to beat.stats (elastic#29094) Revert "Move labels and annotations under kubernetes.namespace. (elastic#27917)" (elastic#29069) ...




What does this PR do?
Enable the AWS stage testing in AWS on a PR basis if certain files changed:
Why is it important?
This was disabled in #23186 since there were some issues with the DB quota and runs on a weekly basis.
Contributors might forget that using
can verified their PRs with AWS Cloud.
So this will ensure it runs automatically when needed.