Bug 1382938

Summary: cannot set dockerfilePath when running `oc new-build`
Product: OpenShift Container Platform Reporter: Aleksandar Kostadinov <akostadi>
Component: RFEAssignee: Ben Parees <bparees>
Status: CLOSED WONTFIX QA Contact: Wang Haoran <haowang>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.3.0CC: aos-bugs, jokerman, mepley, mmccomas, nick, wsun
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-12 11:55:29 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 Aleksandar Kostadinov 2016-10-08 15:30:32 UTC
Description of problem:
One may wish to create builds based on different `Dockerfile` name. e.g. `Dockerfile.centos`

Version-Release number of selected component (if applicable):
oc v3.3.1.1


How reproducible:
always

Steps to Reproduce:
1. oc new-build -h

Actual results:
nothing about dockerfilePath

Expected results:
some command line option to set the value

Without such option `new-build` is only possible when dockerfile name is Dockerfile

Comment 1 Nicholas Schuetz 2017-11-19 18:16:14 UTC
I would like this feature as well.  As it is now, i have to 'oc patch' the buildconfig after the new-build to set the dockerfilePath.  Would rather be able to call an option from the new-build to set this and skip the second step.

-Nick

Comment 2 Nicholas Schuetz 2018-01-07 15:59:11 UTC
Bump.

We need an option for this on new-build:

https://docs.openshift.com/container-platform/3.7/dev_guide/builds/build_strategies.html#dockerfile-path

Note, i have many customers using my custom image howto to build their own s2i image chains where the lack of this simple feature causes confusion (and extra steps).

https://github.com/nnachefski/ocpstuff/tree/master/images

Comment 4 Michael Epley 2018-04-30 18:42:26 UTC
Seconded. 'oc edit'/'oc patch' is a workaround, but awkward/confusing/requires additional, specialized api knowledge.

Comment 6 Kirsten Newcomer 2019-06-12 11:55:29 UTC
With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers.  Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant.

This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. 

If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new 

Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new 

As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.

Comment 7 Aleksandar Kostadinov 2019-12-12 22:43:45 UTC
moved to https://jira.coreos.com/browse/WRKLDS-126