[Container-tools] using openshift origin v3 to back centos build pipeline

[Aaron Weitekamp]

Rob, this is in the context of building an centos upstream image pipeline.
I'm not working on it directly but suggesting, as you pointed out, that
openshift provides a lot of the infrastructure that is required.
On Jul 17, 2015 3:32 PM, "Rob Cernich" <rcernich at redhat.com> wrote:

> Hey Aaron,
>
> What are you trying to do?
>
> 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).
>
> Rob
>
>
> ------------------------------
>
> 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.
>
> [1] https://docs.openshift.com/enterprise/3.0/dev_guide/builds.html
>
> _______________________________________________
> Container-tools mailing list
> Container-tools at redhat.com
> https://www.redhat.com/mailman/listinfo/container-tools
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/container-tools/attachments/20150717/9ff97190/attachment.htm>