Bug 1367445

Summary:	[RFE] Provide a Python Jenkins Kubernetes Plug-in Image to accommodate alternative build scripting languages
Product:	OpenShift Container Platform	Reporter:	Eric Rich <erich>
Component:	RFE	Assignee:	Ben Parees <bparees>
Status:	CLOSED DEFERRED	QA Contact:	Xiaoli Tian <xtian>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.2.1	CC:	aos-bugs, bparees, erich, jokerman, mmccomas, mrobson
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-01-29 14:57:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Eric Rich 2016-08-16 12:25:41 UTC

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.

Comment 1 Ben Parees 2016-11-10 02:21:42 UTC

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.