On Sat, Feb 8, 2020 at 7:24 PM Jonas Hahnfeld <hah...@hahnjo.de> wrote:
> > the point is that you can take a snapshot of the full build at a point > in time. As long as the C++ code doesn't change dramatically between that > point and the commit to be tested, you'd get cache hits on a "clean" build > at a new commit, making the whole thing faster. > > So you do intend to create a new "base release image" for every commit? > The initial proposal had > > The base release image is made at official LilyPond releases, or at > > any release that has a new graphical regtest result > which means we will have "dramatic" changes of the C++ code later in > the cycle. > We'd make them as often as necessary. My thinking is that we don't have to do this on every commit. > Jonas > -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen
