Filebeat: Change compatibility test stage to test against previous minor instead of 7.11 #28274
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This changes the compatibility test for Filebeat modules to test with the previous released minor. Relates elastic#26629
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
botelastic
bot
added
needs_team
|
This pull request does not have a backport label. Could you fix it @adriansr? 🙏
NOTE: |
mergify
bot
added
the
backport-skip
💚 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:
|
andrewkroh
reviewed
Oct 6, 2021
testing/environments/prev-minor.yml
Outdated
| kibana: | ||
| image: docker.elastic.co/kibana/kibana:7.15.0 | ||
| healthcheck: | ||
| test: ["CMD-SHELL", "curl -s http://localhost:5601/api/status | grep -q 'Looking good'"] |
There was a problem hiding this comment.
"Looking good" isn't so good anymore because the status format will change in 7.16. I recommend
beats/testing/environments/snapshot.yml
Line 39 in 3c1731d
There was a problem hiding this comment.
done, also fixed snapshot-oss.yml
adriansr
changed the title
|
So for master, once 7.16.0 is released this will change to that? And for the 7.x (and 7.16) branch, this will remain as 7.15.0? |
|
@andrewkroh, yes, this file will be automatically updated by the release scripts (that's a work in progress) |
adriansr
added
backport-v7.15.0
mergify
bot
removed
the
backport-skip
adriansr
added a commit
that referenced
this pull request
Oct 8, 2021
…nor instead of 7.11 (#28274) (#28307) This changes the compatibility test for Filebeat modules to test with the previous released minor. Relates #26629 (cherry picked from commit 9806f91) Co-authored-by: Adrian Serrano <[email protected]>
v1v
added a commit
to v1v/beats
that referenced
this pull request
Oct 11, 2021
* upstream/master: (73 commits) Remove GCP support from Functionbeat (elastic#28253) Move labels and annotations under kubernetes.namespace. (elastic#27917) Update go release version 1.17.1 (elastic#27543) Osquerybeat: Runner and Fetcher unit tests (elastic#28290) Osquerybeat: Improve handling of osquery.autoload file, allow customizations (elastic#28289) seccomp: allow clone3 syscall for x86 (elastic#28117) packetbeat/protos/dns: don't render missing A and AAAA addresses from truncated records (elastic#28297) [7.x] [DOCS] Update api_key example on elasticsearch output (elastic#28288) [cloud][docker] use the private docker namespace (elastic#28286) Update aws-lambda-go library version to 1.13.3 (elastic#28236) Deprecate common.Float (elastic#28280) Filebeat: Change compatibility test stage to test against previous minor instead of 7.11 (elastic#28274) x-pack/filebeat/module/threatintel/misp: add support for secondary object attribute handling (elastic#28124) Explicitly pass http config to doppler consumer (elastic#28277) processors/actions/add_fields: Do not panic if event.Fields is nil map (elastic#28219) Resolved timestamp for defender atp (elastic#28272) [Winlogbeat] Tolerate faults when Windows Event Log session is interrupted (elastic#28191) [elastic-agent] proxy requests to subprocesses to their metrics endpoints (elastic#28165) Build cloud docker images for elastic-agent (elastic#28134) Upgrade k8s go-client library (elastic#28228) ...
Icedroid
pushed a commit
to Icedroid/beats
that referenced
this pull request
Nov 1, 2021
…nor instead of 7.11 (elastic#28274) This changes the compatibility test for Filebeat modules to test with the previous released minor. Relates elastic#26629
ruflin
added a commit
to ruflin/beats
that referenced
this pull request
Mar 21, 2022
In elastic#26629 the issue around running Filebeat against older version of Elasticsearch was discussed and in elastic#28274 testing against the previous minor was introduced. But since 8.0, Filebeat can only ship data to equal or newer versions of Elasticsearch. Because of this, in the tests `TESTING_FILEBEAT_ALLOW_OLDER=1` had to be introduced. I'm opening this PR to remove this testing as it is not something we support anymore.
ruflin
added a commit
that referenced
this pull request
Mar 24, 2022
In #26629 the issue around running Filebeat against older version of Elasticsearch was discussed and in #28274 testing against the previous minor was introduced. But since 8.0, Filebeat can only ship data to equal or newer versions of Elasticsearch. Because of this, in the tests `TESTING_FILEBEAT_ALLOW_OLDER=1` had to be introduced. I'm opening this PR to remove this testing as it is not something we support anymore.
kush-elastic
pushed a commit
to kush-elastic/beats
that referenced
this pull request
May 2, 2022
In elastic#26629 the issue around running Filebeat against older version of Elasticsearch was discussed and in elastic#28274 testing against the previous minor was introduced. But since 8.0, Filebeat can only ship data to equal or newer versions of Elasticsearch. Because of this, in the tests `TESTING_FILEBEAT_ALLOW_OLDER=1` had to be introduced. I'm opening this PR to remove this testing as it is not something we support anymore.
chrisberkhout
pushed a commit
that referenced
this pull request
Jun 1, 2023
In #26629 the issue around running Filebeat against older version of Elasticsearch was discussed and in #28274 testing against the previous minor was introduced. But since 8.0, Filebeat can only ship data to equal or newer versions of Elasticsearch. Because of this, in the tests `TESTING_FILEBEAT_ALLOW_OLDER=1` had to be introduced. I'm opening this PR to remove this testing as it is not something we support anymore.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This changes the compatibility test for Filebeat modules to test with the previous released minor.
Why is it important?
To ensure backwards compatibility with the latest supported version
Related issues