<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>And one more practical issue.</p>
<p>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?</p>
<p>Thanks.<br>
</p>
<br>
<div class="moz-cite-prefix">On 09/22/2016 04:48 AM, Andrew Lee
Rubinger wrote:<br>
</div>
<blockquote
cite="mid:CABm567F0XOPyOLMRNTHOf6AN2pRkE9XpgdAbXu=xrmVEX=EWvw@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Sep 22, 2016 at 7:26 AM,
Baiju Muthukadan <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:bmuthuka@redhat.com"
target="_blank">bmuthuka@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi
Konrad,<br>
<br>
On Thu, Sep 22, 2016 at 4:45 PM, Konrad Kleine <<a
moz-do-not-send="true" href="mailto:kkleine@redhat.com">kkleine@redhat.com</a>>
wrote:<br>
[...snip...]<br>
<span class="">> With a monorepo (and I think this is
what KB mentioned on Bluejeans) we<br>
> would need to rebuild the docker image for core
every time someone makes a<br>
> ui change. This leads to a docker image for core
with revision X+1. Hence,<br>
> we would need to roll out a new image even if
nothing has changed.<br>
<br>
</span>Probably we should use one of these build system to
solve it:<br>
<br>
- <a moz-do-not-send="true"
href="http://www.pantsbuild.org/" rel="noreferrer"
target="_blank">http://www.pantsbuild.org/</a> by
Twitter<br>
- <a moz-do-not-send="true" href="https://buckbuild.com/"
rel="noreferrer" target="_blank">https://buckbuild.com/</a>
by Facebook<br>
- <a moz-do-not-send="true" href="https://www.bazel.io/"
rel="noreferrer" target="_blank">https://www.bazel.io/</a>
by Google<br>
<br>
This article is a good read (Pants build):<br>
<a moz-do-not-send="true"
href="http://www.pantsbuild.org/why_use_pants.html"
rel="noreferrer" target="_blank">http://www.pantsbuild.org/why_<wbr>use_pants.html</a>
(search for Monorepo)<br>
</blockquote>
<div><br>
</div>
<div>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).</div>
<div><br>
</div>
<div>S,</div>
<div>ALR</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Regards,<br>
Baiju M<br>
<div class="HOEnZb">
<div class="h5"><br>
______________________________<wbr>_________________<br>
almighty-public mailing list<br>
<a moz-do-not-send="true"
href="mailto:almighty-public@redhat.com">almighty-public@redhat.com</a><br>
<a moz-do-not-send="true"
href="https://www.redhat.com/mailman/listinfo/almighty-public"
rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/almighty-<wbr>public</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">Red Hat Developer Programs Architecture
<div>@ALRubinger</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
almighty-public mailing list
<a class="moz-txt-link-abbreviated" href="mailto:almighty-public@redhat.com">almighty-public@redhat.com</a>
<a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/almighty-public">https://www.redhat.com/mailman/listinfo/almighty-public</a>
</pre>
</blockquote>
<br>
</body>
</html>