We use testcontainers in JCasC with great success and we are able to run
those tests on Windows (if only they weren't so unstable)
We use assumeTrue to disable tests when docker is not available.
See
here:
(replies inline)
On Thu, 16 May 2019, Chris Kilding wrote:
> I was able to substitute in the fabric8 Docker Maven Plugin to run Moto. It
> seems to work fine on the Linux build agent, but the Windows agent doesn’t
> like
> it (no Docker host or docker.sock available.)
>
> Is there another
I was able to substitute in the fabric8 Docker Maven Plugin to run Moto. It
seems to work fine on the Linux build agent, but the Windows agent doesn’t like
it (no Docker host or docker.sock available.)
Is there another way to get Docker support on the Windows agent, or is this ‘in
the works’
(replies inline)
On Wed, 15 May 2019, Chris Kilding wrote:
> Yep, that sounds reasonable. (I had suspected as much - there would be no end
> to the possible system packages that plugin developers might want.)
>
> Do the ‘docker’-labelled Jenkins agents support the usual ‘dockerfile’
>
Yep, that sounds reasonable. (I had suspected as much - there would be no end
to the possible system packages that plugin developers might want.)
Do the ‘docker’-labelled Jenkins agents support the usual ‘dockerfile’
directive to let the build define a Docker image ad-hoc? Or do all images have
(replies inline)
On Wed, 15 May 2019, Chris Kilding wrote:
> My plugin uses an external dependency, Moto (the AWS mock server) for its
> integration tests.
>
> Moto is written in Python, installed with Pip, in a virtualenv. It can be used
> either directly (where we must do the pip install
My plugin uses an external dependency, Moto (the AWS mock server) for its
integration tests.
Moto is written in Python, installed with Pip, in a virtualenv. It can be used
either directly (where we must do the pip install ourselves) or through the
Java wrapper Localstack (which does little
