Open zhazi0101 opened 1 year ago
The workaround is to specify nestedName
:
dockerCompose {
nestedName = "test"
}
Hey @augi as it seen here can it be more of a compose V1 - V2 issue? 162ee0778db45c04b4ff6e6c2a46c5c8_functional-tests_-web
it is using combined naming pattern.
Hey @augi as it seen here can it be more of a compose V1 - V2 issue?
162ee0778db45c04b4ff6e6c2a46c5c8_functional-tests_-web
it is using combined naming pattern.
Ultimately, it's just an issue that "_-" is colocated; I think the plugin could be updated to choose a better naming pattern by default. I think this is a duplicate of https://github.com/avast/gradle-docker-compose-plugin/issues/393.
Hi folks,
I have a project with two sub-modules - application and functional-tests. Here is two use cases to run my functional tests:
docker compose up
to boot the application. Then, run functional tests once application is up to run.In one words, my goal is checking if application is booted, if no, boot it automatically. Once application is running, start the integration tests.
To achieve this, I add the gradle-docker-compose-plugin into my functional tests build.gradle.kts (I have have a root one and a application one. BTW, the docker-compose.yml is under the root directory also). The fucntional-test build.gradle.kts is as below:
However, I got the error below. The reason I think it somehow relates to the
dockerCompose.isRequiredBy(project.tasks.named("test"))
, because if I removed it, the functinal tests is running. If keep it, I will get the error below:The commands I ran are
./gradlew -p application clean bootJar
docker build
./gradlew :functional-tests:test
Here is the gradlew version info:
Please advise. Thanks in advance.