Hi I'm looking at fixing JENKINS-54840 <https://issues.jenkins-ci.org/browse/JENKINS-54840> in the build-failure-analyzer plugin
It has functionality where a user can force another analysis to be run on a build This gets the log file on disk, opens a PrintStream to it and appends log information to it about the scan result Code: https://github.com/jenkinsci/build-failure-analyzer-plugin/blob/master/src/main/java/com/sonyericsson/jenkins/plugins/bfa/sod/ScanOnDemandTask.java#L110 On recent pipeline versions this is logging exceptions on every call "WARNING org.jenkinsci.plugins.workflow.job.WorkflowRun getLogFileAvoid calling getLogFile on TestWorkflow/TestWorkflow #362 java.lang.UnsupportedOperationException" Is there a supported way to append to a log file after the build is completed? I see ways to get an InputStream, the log text and writeLogTo (seems to be for writing a whole log though) Or should this functionality be re-written? My guess is that build-failure-analyzer should probably have it's own log file, which can just be overwritten on every scan. If this is the approach is there any good example out there that you would recommend? Thanks Tim -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicsP%2B1hpkVEjT319ZTg9oS7_KrAt2x0qe6HzFYDAFv72w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
