Skip to main content

bad interpreter: No such file or directory


1 comment

  • Michael Lasevich

    While it is an explanation of the problem, it is playing fast and loose with definition of "Resolution".  Any ideas how to actually get around this - the workspace name alone in my case is over 60 characters long - and this is not counting the job name or branch name or parent path or any other bits that are required. 


Please sign in to leave a comment.

About CloudBees Support

Our Support Engineers are available to help with any questions or problems you may have with any of our products.