Question about JUnit rules and console out
17 views
Skip to first unread message
Mads Nielsen
Jun 12, 2015, 6:21:26 AM6/12/15
to jenkin...@googlegroups.com
Hey fellow developers!
I have an issue which i am having a hard time finding out and fixing. Basically, we have a test-suite which makes uses of custom test rules to print information to the console about our tests, where we test a custom tool with parameters and expected results.
What we noticed is that if we up the parent pom version from 1.532.3 -> 1.554.1 almost all our console output does NOT get displayed in the console out when we run our jenkins tests within jenkins (Regular System.out.println), we make heavy use of the JenkinsRule in our tests for integration test, but i am wondering as to what could have changed in between those two, that could cause almost all our console output to not be displayed in the console log for our builds?
Anyone who can shed some light on this?
Best regards,
Mads
Jesse Glick
Jun 12, 2015, 5:18:31 PM6/12/15
to Jenkins Dev
On Fri, Jun 12, 2015 at 6:21 AM, Mads Nielsen <m...@praqma.net> wrote:
> What we noticed is that if we up the parent pom version from 1.532.3 -> 1.554.1 almost all our console output does NOT get displayed in the console out when we run our jenkins tests within jenkins (Regular System.out.println), we make heavy use of the JenkinsRule in our tests for integration test, but i am wondering as to what could have changed in between those two, that could cause almost all our console output to not be displayed in the console log for our builds?
https://github.com/jenkinsci/jenkins/commit/f1205fa4d613119909e0266823344dd8e6d5a519
> What we noticed is that if we up the parent pom version from 1.532.3 -> 1.554.1 almost all our console output does NOT get displayed in the console out when we run our jenkins tests within jenkins (Regular System.out.println), we make heavy use of the JenkinsRule in our tests for integration test, but i am wondering as to what could have changed in between those two, that could cause almost all our console output to not be displayed in the console log for our builds?
amended by
https://github.com/jenkinsci/jenkins/commit/2edf25a26b740f42228b75a56de45dfe4ca8f198
Still displayed if you pass -Dtest=… to diagnose a failure
interactively, and still present in Surefire results, just suppressed
by default from the build log to keep it from being unwieldy.
Mads Nielsen
Jun 15, 2015, 5:26:18 AM6/15/15
to jenkin...@googlegroups.com
Hi Jesse,
Thanks! that clears it up for me.
Best regards,
Mads
--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr18sJ08C6%3Drf%2BZeTi%2B-L2MM2tQOX2UTdengxyiWd%2BntoA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages