Hide Forgot
Description of problem: For a user looking to use Ruby/Python or an alternative shell as part of a Jenkins build, it is not possible because these tools are not built into the Jenkins image. This RFE is to request that alternative shells like python and ruby are included in the Jenkins image, so that they can be used as part of build automation.
Eric, given that we support arbitrary slave images which can contain other shell tools, do you still think it's critical that the jenkins master image also include these tools? It seems like a slippery slope (python, ruby, perl...). Users can certainly extend the jenkins master image themselves if they want additional tools included in it.