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 (103 forks)batch import
help wanted

Repository metrics

Stars
 (429 stars)
PR merge metrics
 (Avg merge 24d 11h) (2 merged PRs in 30d)

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

Research direction
Investigate the interaction between `stopContainers` and `buildBeforeUp` in the plugin's task configuration and execution logic.
Tech stack
groovy
Domain
build system
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GradleDockerDocker Compose
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60