[almighty] Monorepo

[Joshua Wilson]

I envision the UI being built as separate projects/repos. I think it takes
less effort to maintain a project if it is in it's own repo. Additionally,
how would you share a project in an OSS way if it is a part of the whole. I
think it may hinder contributions if someone starts using a UI project and
has to work with it inside a repo that has all the other things.

Joshua

On Thu, Sep 22, 2016 at 9:58 PM, Alexey Kazakov <alkazako at redhat.com> wrote:

> And one more practical issue.
>
> What about permissions? It's easy to set up permissions individually for
> separate repos. But as I understand it can be tricky on
> project/file/microsevice level using git monorepos. And github doesn't
> support it. Or I'm missing something?
>
> Thanks.
>
> On 09/22/2016 04:48 AM, Andrew Lee Rubinger wrote:
>
>
>
> 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
>
>
> _______________________________________________
> almighty-public mailing listalmighty-public at redhat.comhttps://www.redhat.com/mailman/listinfo/almighty-public
>
>
>
> _______________________________________________
> almighty-public mailing list
> almighty-public at redhat.com
> https://www.redhat.com/mailman/listinfo/almighty-public
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/almighty-public/attachments/20160923/9eedac2b/attachment.htm>