-
Notifications
You must be signed in to change notification settings - Fork 594
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dockerExecute with dockerVolumeBind is now broken #4705
Comments
@c0d1ngm0nk3y , this seems to have broken pipelines that run in jenkins instance where volume binds can be done without any restrictions |
@vtintillier , do you run on your custom jenkins instance ? |
We run on a JaaS instance |
afaik JaaS instance did not allow volume binds and this was not considered downstream when Piper executed on |
We've always used this volume bind. Let me try what happens if we remove it. |
The root of the jenkins-library/vars/dockerExecute.groovy Line 390 in 6efb21b
But as @anilkeshav27 already mentioned: Previously the |
@vtintillier Like Philipp already mentioned, the So I would propose, you just remove the |
I confirm it works without the |
Thank you all for your help! |
But this never worked anyway and even on docker, it is expected in a different format. |
Thanks for the volume bind option for K8S. However, I wonder why we do now use different formats of the dockerVolumeBind parameter for K8S and Jenkins worker nodes? |
@Kiemes , the volume bind we have allowed is very restricted , it only allow a |
Hello
since #4673 was delivered, our pipeline is broken. We have this in our scripted pipeline:
This now fails with
Thank you for your help.
The text was updated successfully, but these errors were encountered: