Klever

Recently we met the case when there were no original sources for error traces. The suggested way (to use more code coverage details) could not help since the issue was due to an invalid build base. #10633 will help to avoid this particular issue, but it will not help to avoid all such issues that Core can easily provide.

I suggest to check all references from entities (error traces, code coverage, maybe something else) and fail jobs referencing non-existing original sources, i.e. source files starting with "source files/". We expect a nice error message in Bridge, e.g.:

Error trace/code coverage references non-existing original source file "path/to/file"