Jenkins git-plugin Question for Console Output

[aja...@invoca.com]

Hey there,

Was told by the developers that someone here might be able to assist me in a question that I have. So, I have confirmed through the developers that the git-plugin itself is causing Jenkins to output some information in the Console Output after it runs a test, but my question is if anyone knows the best way to go about silencing some of these outputs in order to clean up the Console Output. 

If anyone has any ideas, they would be greatly appreciated. 

Thanks!

[Vincent Latombe]

Hello,

could you give some example of these output?

Vincent

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/7d708b3f-4edd-42d5-8e3b-e2cce4b13da7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Alec Jacobs]

My bad, I guess I forgot to include that. I have outlined in green the only output that we would like to have in the log, everything else is somewhat not necessary. Thanks!

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/UhQr6OggWL4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAH-zGCiDjy%3DkT%3DkAnjXe4%2BKVnDmw8zi7b_d7%2BTzsSWodW4cD1w%40mail.gmail.com.

[Vincent Latombe]

Hello,

judging from your current output, you are currently running your slave with git client plugin in verbose mode (note : this is *not* the default behaviour). This feature is controlled by the following system property : hudson.plugins.git.IGitAPI.verbose . If false, you won't see any of the git commands (lines prefixed by '>') in your screenshot.

Also, I can also recommend you to leverage existing test report infrastructure provided by Jenkins, by producing a JUnit-compatible report, or using a plugin such as XUnit plugin to transform the output into the JUnit one. That way, you benefit from graphical report, trend and drilldown into test failures when they happen. And as a side-effect, your developers no longer have to go check out the console to check test results ;)

HTH,

Vincent

Vincent

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAP7AWpPJtAfbW%2B6iOrXcfSz%3DY%3DBoo-2x-S8wQCtxkLgRjOKt_Q%40mail.gmail.com.

[Alec Jacobs]

Thank you! I had managed to find the VERBOSE setting and set that to false right before you sent this and was about to test, so you also mentioning this makes me feel a lot better about it. Thanks! I will also checkout XUnit as per your recommendation

Much Appreciated,

Alec Jacobs

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAH-zGCj4sxnesncVU2A-JL%3Dwm-%3Dr%3DMRSp_LdHyDVb8Ji8pkWig%40mail.gmail.com.