Re: Parallelizing the CI doc build

2020-06-06 Thread Dan Eble
On Jun 6, 2020, at 16:03, Jonas Hahnfeld wrote: > Am Samstag, den 06.06.2020, 15:47 -0400 schrieb Dan Eble: >> On Jun 6, 2020, at 15:26, Dan Eble wrote: >>> split the doc stage of the build into multiple stages that can be run in >>> parallel on different runners >> >> For example, assigning ea

Re: Parallelizing the CI doc build

2020-06-06 Thread David Kastrup
Dan Eble writes: > Would we still be validating LilyPond properly if we split the doc > stage of the build into multiple stages that can be run in parallel on > different runners, or is it fundamentally important that we test "make > doc"? Well, given the current frequency of build system change

Re: Parallelizing the CI doc build

2020-06-06 Thread Jonas Hahnfeld
Am Samstag, den 06.06.2020, 15:47 -0400 schrieb Dan Eble: > On Jun 6, 2020, at 15:26, Dan Eble wrote: > > split the doc stage of the build into multiple stages that can be run in > > parallel on different runners > > For example, assigning each runner one or more languages to build. In my under

Re: Parallelizing the CI doc build

2020-06-06 Thread Dan Eble
On Jun 6, 2020, at 15:26, Dan Eble wrote: > > split the doc stage of the build into multiple stages that can be run in > parallel on different runners For example, assigning each runner one or more languages to build. — Dan

Parallelizing the CI doc build

2020-06-06 Thread Dan Eble
Would we still be validating LilyPond properly if we split the doc stage of the build into multiple stages that can be run in parallel on different runners, or is it fundamentally important that we test "make doc"? — Dan