On Wednesday, 16 September 2020 at 10:47:01 UTC, wjoe wrote:
On Wednesday, 16 September 2020 at 10:23:16 UTC, Iain Buclaw
wrote:
On Wednesday, 16 September 2020 at 09:33:05 UTC, wjoe wrote:
[...]
build_bootstrap=enabled should be OK. Even better, it
configures with --enable-checking=release.
[...]
All tasks could be ran in parallel as there's no dependencies
between them. The Package task though I'd imagine should be
reserved for the release branches, so it's only ran
infrequently.
Configuration wise that's not a problem at all. My reasoning
for the dependency was that there's no point in making a
release tar ball if the Unittests task fails.
It's not really the end of the world if a test fails. While
tagged releases should ideally all pass, some failures can occur
that are not our fault (i.e: x32 has a libc bug that causes some
syscalls to fail and trigger asserts in a couple libphobos tests).
For non-tagged builds, I imagine we'd just be replacing the
previously built tarball based on the given branch it was built
off, so if something really is broken, in the worst case we just
wait until a fix goes in and retrigger CI. Or if some downstream
is affected, we'd have some sort of versioning in place (such as
syncthing) to do a quick restore.
