You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 4, 2018. It is now read-only.
@tomdottom The docker image must have inside the jenkins agent ready for run. In my case, a workaround is use a custom Dockerfile with base of https://hub.docker.com/r/jenkinsci/slave/~/dockerfile/ and adding the things I need (docker for example).
Once you have a jenkins agent running inside the container, the sh will exec correctly.
I had the same problem, and it was caused because the format of the bash script was incorrect.
I noticed it when I tried to run my script on my local computer and I saw the error message:
/bin/sh^M: bad interpreter: No such file or directory.
After to fix this issue my script was executed successfully.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When trying to run the following declarative pipeline:
I get the error:
When monitoring the pipelines
@tmp
directory whilst its running I can seescript.sh
created.some system details
Jenkins running as a single node system which has docker installed.
The text was updated successfully, but these errors were encountered: