> The concern would be that without CI you have very limited visibility into > the impact of the patches pre-merge. The automation at fd.io does a *lot* > for you…
Absolutely. For the hackathons CI was an order or two of magnitude too slow. And we would be doing the testing there and then. I don’t know how applicable that experience is for someone who’s buildiing a demo though. Cheers, Ole > On Wed, Nov 15, 2017 at 3:50 PM Jon Loeliger <j...@netgate.com> wrote: > On Wed, Nov 15, 2017 at 4:17 PM, Dave Wallace <dwallac...@gmail.com> wrote: > Folks, > > Per the action item from this yesterday's VPP weekly meeting, I'm asking for > opinions from the VPP community on allowing the creation of demo branches in > the VPP git repo. > > ... > > > Pro: Will allow utilization of LF infra to utilize CI process > Pro: Will allow publishing of demo artifacts for ease of reproduction of the > demo. > Con: Will pollute repo with ephemeral code that will rapidly become out of > date / dead. > Con: Sets precedent which may cause large numbers of non-production branches > over time. > > Please feel add additional Pro/Con comments here. Comments are welcome from > all members of the VPP community. > > Dave, > > In my opinion, creating a cloned fork and adding demo code there would be a > better approach. And that demo code will likely become obsolete and bit-rot > over time, > but it will forever be part of the repo. Over time it will just be dead > weight bloat. > The core code base should remain as a library and not get tied to any > specific application. > > HTH, > jdl > _______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
