We believe the latest update to the docker-workflow-plugin may have broken the windows execution of the docker.stop() command within the pipeline (as it stopped working around that time)
the pipeline is defined with the following steps:
previously the job executed the above as follows:
however now the job fails at the stop step (and while the docker run does execute, it does not appear in the logs anymore)
so it has now completely messed up the stop step - appearing to use the entire run command as the container id?