<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div>Hey Aaron,<br></div><div><br></div><div>What are you trying to do?<br></div><div><br></div><div>Generally speaking, a BuildConfig simply identifies a "source" that is used to produce an image. The build may be a docker build (source=Dockerfile), and STI build (source=git project+build image), or custom (no experience with this). The output of the build (the image) is pushed to the registry using the information in the referenced ImageStream. The ImageStream specifies the location of the registry, the repository and image names, and the tag (location/repository/image:tag).<br></div><div><br></div><div>Rob<br></div><div><br></div><div><br></div><hr id="zwchr"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div dir="ltr"><div class="gmail_default" style="font-size:small">Looking deeper into the capabilities of openshift origin[1] have we considered this as the core tech for pushing image content through the pipeline? I don't think I'm on the right mailing lists for this discussion. I'm just curious on the direction here.<br><div><br></div>[1] <a href="https://docs.openshift.com/enterprise/3.0/dev_guide/builds.html" target="_blank">https://docs.openshift.com/enterprise/3.0/dev_guide/builds.html</a><br></div></div>
<br>_______________________________________________<br>Container-tools mailing list<br>Container-tools@redhat.com<br>https://www.redhat.com/mailman/listinfo/container-tools<br></blockquote><div><br></div></div></body></html>