I am talking about lines of text in the console of the job (so what is in Jenkins under the job run's "Console output"). So not in the developer .log or app. server servoy_log.txt but really the output of the job.
Those already appear like that for Servoy build errors and warnings, but
currently only errors can fail the export (warnings are just logged but don't fail) and there is no check for javascript errors as I already mentioned. If you want the possibility to fail export - so job - even for warnings and also check for JS errors you should
make a case.
Not sure where the equivalent of "Console output" appears in GitLab CI. But the basic idea should be the same.
What I was suggesting was that you don't even parse that output - just send the email with that output when job fails; at least that was easy to do in Jenkins. Of course if you can parse it as you used to and show problems nicer it's a plus...
That was my question: are you thinking of a nicer way to report these? Is it worth it?
PS: If you want to fail your job for warning markers - without any case to change Servoy then yes you'd need to parse the output and search for warnings yourself...