|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-5949) Trim JUnit stack trac... [email protected] (JIRA)
- [JIRA] (JENKINS-5949) Trim JUnit stack... [email protected] (JIRA)
- [JIRA] (JENKINS-5949) Trim JUnit stack... [email protected] (JIRA)
- [JIRA] (JENKINS-5949) Trim JUnit stack... [email protected] (JIRA)
- [JIRA] (JENKINS-5949) Trim JUnit stack... [email protected] (JIRA)
- [JIRA] (JENKINS-5949) Trim JUnit stack... [email protected] (JIRA)
- [JIRA] (JENKINS-5949) Trim JUnit stack... [email protected] (JIRA)

The way I have implemented this is with a new parameter (maxLength) which can be used to specify the max KB of data to print as part of the FAILED_TESTS token. If the output would exceed the amount specified, then it truncates the output and adds "...output truncated" to the output. The default value of the parameter imposes no limit to maintain current functionality by default. Will this meet the request?