On Mon, Jan 10, 2022 at 6:19 AM Chris Kilding <
chris+jenk...@chriskilding.com> wrote:
> kubernetes-pipeline-plugin and gitlab-plugin appear to be the 2 other
> plugins under jenkinsci that use docker-maven-plugin. Is it worth advising
> them to switch to Testcontainers at some point as well?
>
W
The Moto KeyError seemed to be a one-off flake; I haven't seen it happen since
then. Testcontainers seems to be working reliably enough over subsequent
builds, so counting this as fixed :)
kubernetes-pipeline-plugin and gitlab-plugin appear to be the 2 other plugins
under jenkinsci that use doc
On Wed, Jan 5, 2022 at 7:41 AM Chris Kilding
wrote:
> Log is here:
>
More useful is the test stderr
https://ci.jenkins.io/job/Plugins/job/aws-secrets-manager-secret-source-plugin/job/PR-37/2/testReport/io.jenkins.plugins.casc.secretsmanager/SecretSourceIT/linux_11_2_263_4___Build__linux_11_2_263
I tried migrating from the docker-maven-plugin to testcontainers. The resulting
code is indeed a little cleaner, and it's nice to not have to run an
out-of-band step before running the test suite. Unfortunately the build still
fails on ci.jenkins.io, so the underlying Docker issue is probably st
Thanks for reporting and pinging us!
I confirm that this timeout error is not related to the Jenkins Kubernetes
plugin issue that we face on others Jenkins instances (it’s a VM agent with a
Docker Engine in this case).
(The "fabric8" component from the error stack was misleading @Mark ;) ).
We
