avast/gradle-docker-compose-plugin

Feature Reqest: add an option to skip Health-Check

Open

#496 opened on Oct 13, 2025

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

Description

Looking around the code in ComposeUp.groovy#waitForHealthyContainers the compose up task is hardwired to wait until all containers are healthy. I had an idea for an Regression test where i would like to test using a unhealthy ontainer

Contributor guide

Tech stack
javadocker
Domain
testingdevops
Issue type
feature
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.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
GradleDocker Compose
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Start by examining the ComposeUp.groovy file, especially the waitForHealthyContainers method. Understand how health checks are currently enforced and identify where a configuration option to skip them could be added. Look for existing patterns in the codebase for optional behavior (e.g., flags or closures) and consider adding a property like skipHealthCheck. Review the plugin's test suite to see how similar features are tested.