The registry is an interesting question. We've had a lot of discussion about other types of registries (mostly Artifactory and Nexus) and those are multi-content type registries that can also store RPMs, as well as docker images. I'm not opposed to an RPM registry, but a first class integration with a multi-content type registry has some other advantages.
As far as an RPM build type, that's very reasonable. Is there a one size fits all build flow for RPM, or would different environments (fedora, centos, RHEL) or users (ISVs, big deployments, Satellite) have different requirements? On Fri, Jun 17, 2016 at 6:19 AM, Tobias Florek <[email protected]> wrote: > Hi, > > I experimented a bit with using rpm-ostree to build minimal CentOS-based > Docker containers. In particular these containers don't have yum (or > python) installed. > > That works pretty fine, and I'd like to use this approach to build > containers on openshift. Of course there could be a rpm-ostree builder > for convenience, but I am not talking about that (it works using > a custom builder as is). To build applications on top of these base > containers, I use rpm as build artefact (as Colin Walters somewhere > recommends himself) which I compose on top of the base image. Right now, > my custom builder builds the rpm right before composing the container, > before throwing away the (s)rpm. I'd like to separate these two steps > in openshift, preferably without using jenkins. > > So I propose that there is a rpm registry that can be used as build > trigger automatically, analogous to the docker registry. > Also there might be a build-type that does not build docker containers, > but rpms. > > What do you think? > Tobias Florek > > _______________________________________________ > dev mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > _______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
