-
Notifications
You must be signed in to change notification settings - Fork 98
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
Parallelise the tasks #245
Comments
Thank you for this issue! Could you please provide more details on the I'm asking because the first check of a port is made without any artificial delay, so if all containers are ready, the waiting for open ports should be very fast (e.g. less than one second). That's why I would like to see how it behaves in your case. Thanks! |
Here is a log. Unfortunately gradle doesn't provide timestamps unless they are debug logs but those leak too much information. The relevant bit after the log message The final bit where it probes various containers in sequence for their ports after the message
BUILD SUCCESSFUL in 2m 41s |
Hello,
On our build the composeUp task takes 1 minute and the composeLogs task takes 51 seconds. A significant proportion of that is because we have around 15 containers in the docker-compose.yaml file. So on startup the plugin is checking the ports in serial. On exit it is dumping the logs in serial as well.
It would be great if those were done in parallel. One container operation in a separate gradle worker:
https://guides.gradle.org/using-the-worker-api/
Many thanks,
Nikolay
The text was updated successfully, but these errors were encountered: