Am Samstag, den 08.02.2020, 19:18 +0100 schrieb Han-Wen Nienhuys: > > > On Sat, Feb 8, 2020 at 2:05 PM Jonas Hahnfeld <[email protected]> wrote: > > > > * if instead we build images for every commit, then incremental > > > > building of a provided patch will be fast(er) (_if_ it doesn't touch > > > > any header file). But what's then the point of using ccache, we can > > > > just trigger a full build? > > > > > > Full builds are slower. > > > > True, but my point is that it doesn't matter: You have to do a full > > build to populate ccache; or you just build with the changes already > > applied, what's the difference? > > > > 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. Jonas
signature.asc
Description: This is a digitally signed message part
