Zack Galbreath

You're right, buildSummary.php should link to coverage and dynamic analysis when present. Even better would be a table of quick-links to the various parts of a build (configure, build errors,...

Thanks for the report. Can you check if you have a value for `APP_URL` set in your .env file?

Our docker-compose system creates separate containers for the database and the web server. So you could probably get away with recreating the web server as-is, and then using it to...

Does this work for you? ``` docker-compose run --rm cdash configure ``` That _should_ run CDash's configure step without reinstalling a fresh database. https://github.com/Kitware/CDash/blob/master/docs/docker.md#install-cdash

> The presented web page (install.php) contains my parameters for the database configuration, but requires the admin mail address and password to be entered. When I do this and click...

I'll experiment locally with reusing an existing database container for a new CDash 3.0.3 docker container. I'll let you know how it goes.

#1258 was merged yesterday. That removed the dependency on a pinned version of Bernard, which was a big blocker for PHP 8 support. I hope to revisit this soon to...

Thanks for letting us know. We'll take a look.

It is not. Our current strategy is still to display static analysis defects as build errors.

You're talking about the graphs on `buildSummary.php`, right? If so, is it possible that your build name changed?