That was a strange case. The message is atypical (can't initialize a Trilead class) and seems to only be associated with one agent. I have deleted that agent and started a new build of PR-35.
Not clear why that agent had the issue, but it is easy to discard an agent and allow the allocator to provision a new one. On Mon, Aug 10, 2020 at 10:12 AM Goyot, Martin <[email protected]> wrote: > Hi there, > > Is there a current issue with the Jenkins pipeline for plugins or are we > doing something wrong? Our builds seems to not be able to connect to the > AWS machines: > https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Ftuleap-oauth-plugin/detail/PR-35/4/pipeline > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CA%2Bb6JB9TtcG6RiW_R_bZNtq7K6iBKVUcWchENBVtkSmtoUqjyw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CA%2Bb6JB9TtcG6RiW_R_bZNtq7K6iBKVUcWchENBVtkSmtoUqjyw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGnMmO7cBEQNz6OBOzxFRx2NEHtNSr_06zisXDWY5ZukA%40mail.gmail.com.
