gradle-dockerized-test-plugin icon indicating copy to clipboard operation
gradle-dockerized-test-plugin copied to clipboard

Running tests inside a docker image

Results 7 gradle-dockerized-test-plugin issues
Sort by recently updated
recently updated
newest added

I hate to ask but how much does this plugin support Windows? I've worked around a few things but I've now hit an issue with the `gradle-worker-classpath` file that gradle...

I'm trying to create a client with the following closure (as the docs suggest): ``` client = { DockerClient temp = DockerClientBuilder .getInstance(DefaultDockerClientConfig .createDefaultConfigBuilder() .withDockerHost("tcp://10.0.0.1:2376")) .withDockerCmdExecFactory(new NettyDockerCmdExecFactory()) .build() return temp...

We are trying to use this plugin with Gradle 4.5 but without success. ``` > Cannot cast object 'com.pedjak.gradle.plugins.dockerizedtest.TestExecuter@1f5c114c' with class 'com.pedjak.gradle.plugins.dockerizedtest.TestExecuter' to class 'org.gradle.api.internal.tasks.testing.TestExecuter' * Try: Run with --debug...

It doesn't seem that the plugin pulls down the docker image and builds if the docker image does not exist.

Running this with gradle 4.0 does not work well. ``` Caused by: groovy.lang.MissingPropertyException: No such property: workerFactory for class: org.gradle.process.internal.worker.DefaultWorkerProcessFactory at com.pedjak.gradle.plugins.dockerizedtest.DockerizedTestPlugin.newProcessBuilderFactory(DockerizedTestPlugin.groovy:101) at com.pedjak.gradle.plugins.dockerizedtest.DockerizedTestPlugin$_configureTest_closure1.doCall(DockerizedTestPlugin.groovy:70) at org.gradle.api.internal.AbstractTask$ClosureTaskAction.execute(AbstractTask.java:670) at org.gradle.api.internal.AbstractTask$ClosureTaskAction.execute(AbstractTask.java:651) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$1.run(ExecuteActionsTaskExecuter.java:122)...

This change enables the user to configure the timeout used when the Gradle worker process is started to execute the Docker commands. This is needed in my use case because...

I have a gradle multi project and trying to run test target from one of the subprojects using this plugin. My tests fail because they don't see classes from dependent...