Description of problem: There is not an easy way to use secrets to authenticate and pull source code from non-public code repos like github. For instance, if a customer has an internal (and protected) git repo (like Stash). Right now, you have to create a create secrets.json file, do some base64 encoding of the private key, and edit the build config, blah blah blah. This leaves alot of room for human error. We need an easy way enter and associate these secrets with external repos via the web console. Thanks! -Nick
This section in the docu is not enough for the explanation? https://docs.openshift.com/enterprise/3.0/dev_guide/builds.html#using-private-repositories-for-builds FYI: Ben's reply in the internal thread http://post-office.corp.redhat.com/archives/openshift-sme/2015-July/msg01740.html
Good enough for me. Thanks guys! -Nick