Bug 1303405

Summary: [DOCS] [3.2] Document that builds can now be started by pushing binary content
Product: OpenShift Container Platform Reporter: Vikram Goyal <vigoyal>
Component: DocumentationAssignee: Alex Dellapenta <adellape>
Status: CLOSED CURRENTRELEASE QA Contact: Wang Haoran <haowang>
Severity: medium Docs Contact: Vikram Goyal <vigoyal>
Priority: high    
Version: 3.1.0CC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-02 15:58:11 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:
Embargoed:
Deadline: 2016-03-15   

Description Vikram Goyal 2016-01-31 13:43:54 UTC 
In OSE 3.2, the developer can push binary content into a build and start the build.

The user will be able to access `oc start-build` and pass:

* a file - placed in an empty dir at / with the same name as build input
* a directory - tar.gz and sent to the server
* a zip or tar or tar.gz streamed via STDIN
* a local git repository and a commit

which will upload the contents to the builder pod and launch a build.

Dev for this feature is:
Michal Fojtik

Trello Card is:
https://trello.com/c/oI1ddWEn/273-5-users-can-push-binary-contents-to-trigger-a-build

QA is:
Haoran Wang

Likely guide is:
Dev Guide in Builds section: 
https://docs.openshift.com/enterprise/3.1/dev_guide/builds.html#binary-source

Upstream docs:
https://github.com/openshift/openshift-docs/pull/1312
Comment 1 Alex Dellapenta 2016-03-02 15:58:11 UTC 
Published in OSE 3.1 docs as of 3.1.1:

https://docs.openshift.com/enterprise/latest/dev_guide/revhistory_dev_guide.html#mon-feb-15-2016

https://docs.openshift.com/enterprise/latest/dev_guide/builds.html#starting-a-build

My PR was https://github.com/openshift/openshift-docs/pull/1583.