avast/gradle-docker-compose-plugin

Parallelise the tasks

Open

#245 opened on Jun 24, 2020

View on GitHub
 (2 comments) (1 reaction) (0 assignees)Groovy (429 stars) (103 forks)batch import
enhancementhelp wanted

Description

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

Contributor guide

Tech stack
groovy
Domain
build systemdeveloper experience
Issue type
performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Gradle plugin developmentGradle Worker API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
The issue suggests parallelizing port checks and log dumping for multiple containers in the gradle docker compose plugin using Gradle's Worker API (https://guides.gradle.org/using the worker api/). The specific tasks to modify are `composeUp` and `composeLogs`. No linked PRs exist, so the research should focus on understanding the current serial implementation and planning the parallelization.