[almighty] Monorepo

[Andrew Lee Rubinger]

On Thu, Sep 22, 2016 at 7:26 AM, Baiju Muthukadan <bmuthuka at redhat.com>
wrote:

> Hi Konrad,
>
> On Thu, Sep 22, 2016 at 4:45 PM, Konrad Kleine <kkleine at redhat.com> wrote:
> [...snip...]
> > With a monorepo (and I think this is what KB mentioned on Bluejeans) we
> > would need to rebuild the docker image for core every time someone makes
> a
> > ui change. This leads to a docker image for core with revision X+1.
> Hence,
> > we would need to roll out a new image even if nothing has changed.
>
> Probably we should use one of these build system to solve it:
>
> - http://www.pantsbuild.org/ by Twitter
> - https://buckbuild.com/ by Facebook
> - https://www.bazel.io/ by Google
>
> This article is a good read (Pants build):
> http://www.pantsbuild.org/why_use_pants.html (search for Monorepo)
>

Or more simply, N pipelines (one for each deployable component) that are
triggered by a git push but only take action on some filesystem pattern
that denotes the changeset is affected (e.g. **/ui/* would fire the UI
build, else nothing).

S,
ALR


>
> Regards,
> Baiju M
>
> _______________________________________________
> almighty-public mailing list
> almighty-public at redhat.com
> https://www.redhat.com/mailman/listinfo/almighty-public
>



-- 
Red Hat Developer Programs Architecture
@ALRubinger
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/almighty-public/attachments/20160922/be3c1d0a/attachment.htm>