> Am 19.05.2015 um 12:18 schrieb Tomasz Majchrowski <[email protected]>: > > > Thank you Ulrich for quick response. > > 1) With the reference to the console log: What about adding information that > the warning is coming out of console log and just link to console log ?
Some parsers do this already (Maven parser). Is still not understand your use case: normally you link to the file that contains the warning and not to the file that contains the warning report. Can you elaborate on your use case? > 2) With the reference to the external file: If I understand this right, the > issue is that the input file might be a file that reside on the remote slave > hosts. This means that can't be link easily and present by master. Let me > know if my understanding of the issue is right. No, the parsers do not work on files, they work on input streams. So the information if the stream is from the console log or file (master or slave) is not available for a parser up to now. > > Best regards, Tomasz Majchrowski. > > W dniu wtorek, 19 maja 2015 11:36:25 UTC+2 użytkownik Ullrich Hafner napisał: > This is not possible. Since a parser might be used to parse the console log > or a external file this information is not available. > >> Am 19.05.2015 um 11:18 schrieb Tomasz Majchrowski <[email protected] >> <javascript:>>: >> >> Hi, >> >> Does anyone know if there a possibility to include log file-name that >> contains warning in the report produced by warning plugin? The generated >> report is very detail, however I could not find this information out there. >> Thanks in advance >> >> Best regards, Tomasz Majchrowski >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/7b418d82-6ddc-490c-b002-4ee90b5c88cd%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/7b418d82-6ddc-490c-b002-4ee90b5c88cd%40googlegroups.com?utm_medium=email&utm_source=footer>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/cbb93a53-a202-4d05-b361-c3ab371e9b8c%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-users/cbb93a53-a202-4d05-b361-c3ab371e9b8c%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/42C74965-0450-415A-B719-B4DDBB4A1A70%40gmail.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP using GPGMail
