-
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
WIP: honor MODULE env var in Filebeat system tests #18690
Conversation
❕ Build Aborted
Expand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
@jsoriano IIRC you did some work recently on this front? So maybe this PR is obsolete now? |
@ycombinator last changes I did were for Metricbeat, I think there is nothing yet for filebeat. Regarding this change, would it be an option to add support for |
++ what you suggest is the better way to go. We might even want to just replace |
@ycombinator I would prefer to support both environment variables at least during a time. But if this complicates things, I would then go for the approach of replacing the environment variable and mentioning that in the developer CHANGELOG. |
Hi! We're labeling this issue as |
Hi! |
What does this PR do?
Makes the Filebeat module system tests honor the
MODULE
environment variable.Why is it important?
In #18592 we introduced the
MODULE
environment variable. The idea was that when tests are run in a CI environment, if the PR being tested only contains changes for a single module, theMODULE
environment variable would be set to the name of that module. This should help speed up the CI build as unrelated tests wouldn't get run.The Filebeat system tests are currently not honoring the
MODULE
environment variable. This PR teaches them to do that.Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksI have added an entry inCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.