Bug 1399001

Summary: Support "--from-dir" parameter for "Trigger OpenShift Build" in "OpenShift V3 Plugin for Jenkins"
Product: OpenShift Container Platform Reporter: Takayoshi Tanaka <tatanaka>
Component: RFEAssignee: Ben Parees <bparees>
Status: CLOSED WONTFIX QA Contact: Xiaoli Tian <xtian>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: aos-bugs, jokerman, mmccomas
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: 2017-05-20 22:25:19 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 Takayoshi Tanaka 2016-11-28 03:10:15 UTC
From the RFE template:

> 3. What is the nature and description of the request? 
Add "--from-dir" option to Jenkins Pipeline Openshift plugin that behaves exactly the same as oc start-build --frrom_dir option. 

> 4. Why does the customer need this? (List the business requirements here) 
When integrating Jenkins with Openshift, Jenkins performs a checkout of source code, performs some unit tests, and then calls Openshift to run a BuildConfig, which pulls the source code all over again.  Apart from the mucking around having to extract the commit id from Jenkins (which is not natively supported in Jenkins 2 Pipelines yet) so that the buildconfig runs on the same version of the source code, it also involves pulling source code down twice, which is slows things down and wastes bandwidth

> 5. How would the customer like to achieve this? (List the functional requirements here) 
Trigger Openshift Build option to trigger a build using the "--from-dir" oc start-build option so that a build can be triggered from the source code that Jenkins has already checked out. 

> 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. 
Run it as see it build

> 10. List any affected packages or components.  
Jenkins Pipeline Openshift Plugin (using Jenkins 2, but don't think it matters).
https://github.com/openshift/jenkins-plugin

Comment 3 Takayoshi Tanaka 2016-12-01 08:34:37 UTC
Could you tell me when we can get next update? The customer is waiting so I'd like to know if it takes time to receive next update.