Re: javac compiler errors
Wouldn't it be better if Jenkins would already provide a feature to visualize compile errors? (And plug-ins can add new patterns for new compiler types?) I can add such a feature in the warnings plug-in, however I think it would make more sense to have that part in Jenkins core… Currently my plug-in shows only warnings. What do others think? How could we improve compiler error visualization? Ulli Am 11.06.2013 um 22:44 schrieb Kevin Fleming (BLOOMBERG/ 731 LEXIN) kpflem...@bloomberg.net: Ahh, well, it would take a bit of configuration. The Warnings plugin allows you to define your own patterns to be used to capture content from the job output, so you could take the existing patterns for javac and extend them to capture errors as well. One note, though: it only captures one line of each warning, not the whole thing (including any context the compiler may output, although javac generally does a terrible job of that). The person reviewing the problems will end up going back to the console output anyway to get the remaining details. - Original Message - From: jenkinsci-users@googlegroups.com To: jenkinsci-users@googlegroups.com Cc: Kevin Fleming (BLOOMBERG/ 731 LEXIN) At: Jun 11 2013 16:39:53 How? I've had a short email conversation with the warnings plugin maintainer, Ulli Hafner, and he said it only does warnings: For javac, only warnings are shown since errors are already flagged by Jenkins as compile errors. Thank you, Alex On Tuesday, June 11, 2013 3:29:03 PM UTC-5, Kevin Fleming wrote: The Warnings plugin can be used to harvest compiler warning and error messages and display them in a dedicated area of the build results page. - Original Message - From: jenkins...@googlegroups.com To: jenkins...@googlegroups.com At: Jun 11 2013 16:27:56 Is there anyway to have jenkins report javac compiler errors on the project page or the build results page? It seems odd that one needs to drill down into the Console Output to see what went wrong during the build process. Alex -- 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 jenkinsci-use...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: javac compiler errors
I think it would be very helpful to have this as part of Jenkins core. Christoph Ulli Hafner ullrich.haf...@gmail.com schrieb: Wouldn't it be better if Jenkins would already provide a feature to visualize compile errors? (And plug-ins can add new patterns for new compiler types?) I can add such a feature in the warnings plug-in, however I think it would make more sense to have that part in Jenkins core… Currently my plug-in shows only warnings. What do others think? How could we improve compiler error visualization? Ulli Am 11.06.2013 um 22:44 schrieb Kevin Fleming (BLOOMBERG/ 731 LEXIN) kpflem...@bloomberg.net: Ahh, well, it would take a bit of configuration. The Warnings plugin allows you to define your own patterns to be used to capture content from the job output, so you could take the existing patterns for javac and extend them to capture errors as well. One note, though: it only captures one line of each warning, not the whole thing (including any context the compiler may output, although javac generally does a terrible job of that). The person reviewing the problems will end up going back to the console output anyway to get the remaining details. - Original Message - From: jenkinsci-users@googlegroups.com To: jenkinsci-users@googlegroups.com Cc: Kevin Fleming (BLOOMBERG/ 731 LEXIN) At: Jun 11 2013 16:39:53 How? I've had a short email conversation with the warnings plugin maintainer, Ulli Hafner, and he said it only does warnings: For javac, only warnings are shown since errors are already flagged by Jenkins as compile errors. Thank you, Alex On Tuesday, June 11, 2013 3:29:03 PM UTC-5, Kevin Fleming wrote: The Warnings plugin can be used to harvest compiler warning and error messages and display them in a dedicated area of the build results page. - Original Message - From: jenkins...@googlegroups.com To: jenkins...@googlegroups.com At: Jun 11 2013 16:27:56 Is there anyway to have jenkins report javac compiler errors on the project page or the build results page? It seems odd that one needs to drill down into the Console Output to see what went wrong during the build process. Alex -- 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 jenkinsci-use...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
javac compiler errors
Is there anyway to have jenkins report javac compiler errors on the project page or the build results page? It seems odd that one needs to drill down into the Console Output to see what went wrong during the build process. Alex -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: javac compiler errors
How? I've had a short email conversation with the warnings plugin maintainer, Ulli Hafner, and he said it only does warnings: For javac, only warnings are shown since errors are already flagged by Jenkins as compile errors. Thank you, Alex On Tuesday, June 11, 2013 3:29:03 PM UTC-5, Kevin Fleming wrote: The Warnings plugin can be used to harvest compiler warning and error messages and display them in a dedicated area of the build results page. - Original Message - From: jenkins...@googlegroups.com javascript: To: jenkins...@googlegroups.com javascript: At: Jun 11 2013 16:27:56 Is there anyway to have jenkins report javac compiler errors on the project page or the build results page? It seems odd that one needs to drill down into the Console Output to see what went wrong during the build process. Alex -- 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 jenkinsci-use...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: javac compiler errors
Ahh, well, it would take a bit of configuration. The Warnings plugin allows you to define your own patterns to be used to capture content from the job output, so you could take the existing patterns for javac and extend them to capture errors as well. One note, though: it only captures one line of each warning, not the whole thing (including any context the compiler may output, although javac generally does a terrible job of that). The person reviewing the problems will end up going back to the console output anyway to get the remaining details. - Original Message - From: jenkinsci-users@googlegroups.com To: jenkinsci-users@googlegroups.com Cc: Kevin Fleming (BLOOMBERG/ 731 LEXIN) At: Jun 11 2013 16:39:53 How? I've had a short email conversation with the warnings plugin maintainer, Ulli Hafner, and he said it only does warnings: For javac, only warnings are shown since errors are already flagged by Jenkins as compile errors. Thank you, Alex On Tuesday, June 11, 2013 3:29:03 PM UTC-5, Kevin Fleming wrote: The Warnings plugin can be used to harvest compiler warning and error messages and display them in a dedicated area of the build results page. - Original Message - From: jenkins...@googlegroups.com To: jenkins...@googlegroups.com At: Jun 11 2013 16:27:56 Is there anyway to have jenkins report javac compiler errors on the project page or the build results page? It seems odd that one needs to drill down into the Console Output to see what went wrong during the build process. Alex-- 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 jenkinsci-use...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
