Closed timja closed 6 years ago
I confirmed that the change to Jenkins core resolves the message.
Resolved by the Jenkins Core patch
Code changed in jenkins
User: Oleg Nenashev
Path:
pom.xml
http://jenkins-ci.org/commit/groovy-postbuild-plugin/6fd0cd8a95015e394fc61bae14ab4bcc2cf2bc08
Log:
JENKINS-48922 - Update plugin POM to reproduce the issue in PCT
Code changed in jenkins
User: ikedam
Path:
Jenkinsfile
pom.xml
http://jenkins-ci.org/commit/groovy-postbuild-plugin/61f2d13e491ea42a5572590b1903a0acfbfef11c
Log:
Merge pull request #29 from oleg-nenashev/jep-200/pct-compat
JENKINS-48922 - Update plugin to make it runnable in PCT
Compare: https://github.com/jenkinsci/groovy-postbuild-plugin/compare/c2638a586703...61f2d13e491e
As reported by markewaite in https://groups.google.com/forum/#!topic/jenkinsci-dev/EALjDtS4riU
It happens because the plugin serializes StringBuilder to the disk in the action.
The system log includes the following information:
Originally reported by oleg_nenashev, imported from: Groovy PostBuild plugin is not compatible with JEP-200