avast/gradle-docker-compose-plugin

stopContainers=true makes buildBeforeUp not build things

Open

#388 opened on Nov 29, 2022

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Groovy (429 stars) (103 forks)batch import
help wanted

Description

currently when stopContainers=true it makes buildBeforeUp ineffective:

> Task :composeUp
Cached services infos loaded while 'stopContainers' is set to 'false'.

What I'm after is fast integration tests run, and I need containers keep running. But be recreated whenever anything changes.

Is anything like that possible now?

Contributor guide

Tech stack
groovydocker
Domain
devopstestingbuild system
Issue type
bug
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
GradleDocker ComposeIntegration testing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Investigate the plugin source code, focusing on the 'composeUp' task and the interaction between 'stopContainers' and 'buildBeforeUp' properties. Look for conditional logic that ignores the build step when stopContainers is true. Check the Gradle task implementation in files like 'DockerComposeTask.groovy' or similar. There are no linked PRs or additional comments to guide further.