provide log file to submitters

Right now we only tell people their submission is faulty but not in what way -- we should really provide the log file, maybe with some system internals masked. @jjpr-mit what do you think should not be made public from the log file?
Ideally we could also format the logs similar to how travis does it, i.e. expandable logs per command. Maybe there is a jenkins plugin for this? In that case, sending the log file would probably get rid of the structure, but perhaps we could display it in jenkins with a token or on the website?

No files or tests are named; start by tracing how submissions are validated and how Jenkins logs are produced and exposed to submitters. Define which system internals must be masked, then confirm that submitters can view safely formatted logs, with expandable command sections if supported.

Written by the indexing model from the issue text.