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
Support per-module docker compose files for metricbeat tests #13186
Support per-module docker compose files for metricbeat tests #13186
Conversation
jenkins, test this again please |
b0b2896
to
7587650
Compare
7587650
to
3b9f0fc
Compare
jenkins, test this again please |
jenkins, test this again |
This is really cool. Looking forward to give a review 👍 |
@sayden thanks! go for it, I have just opened this for review 🙂 |
project.up( | ||
strategy=ConvergenceStrategy.always, | ||
service_names=cls.COMPOSE_SERVICES, | ||
do_build=BuildAction.force, | ||
do_build=BuildAction.skip, |
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.
Are you sure about this change?
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.
Yes, after adding a explicit project.build
it is not needed to build also in project.up
. The reason to add an explicit project.build
is that project.up
doesn't allow to pass build arguments.
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.
Just one comment. But looks ok
Modify docker compose helpers so they can start scenarios
using different docker compose files, what will allow to define
docker compose scenarios per module.
Apache service definition is moved to its own docker compose
file.
Related to #12909