This stack trace looks a lot like the one posted in JENKINS-51290
, which was marked as fixed
in Pipeline Multibranch 2.19 based on the changelog for that plugin. Does that
issue line up with what you are seeing, and are you using Pipeline Multibranch
2.18 or older? If so, I would try updating,
I'm using Jenkins on OpenShift with the kubernetes plugin for creating
Jenkins workers. Occasionally we get the following error whenever the
pipeline first runs but can't explain what is going on; simply rerun it and
the 2nd time will work.
Many thanks for someone who can point out to what is goi