The output that the stages will do is controlled so there will be at most 30-40 lines of text. And also I'll truncate the text before sending it to GH if it's beyond a certain size.
On Monday, April 15, 2019 at 8:51:59 PM UTC+3, Jesse Glick wrote: > > On Mon, Apr 15, 2019 at 10:41 AM Daniel Anechitoaie > <[email protected] <javascript:>> wrote: > > 3) When build fails. Here I would need to get the output of the stage > the failed to be able to send that to GitHub. > > I guess you could capture the stage output, but this could in general > be massive. Do you really need to send it to GitHub? JENKINS-28119 > might be a better approach: just send GitHub a link back to Jenkins. > > > For #3 I did as you suggested from @Ullrich link as a block scoped > function which seems perfect. > > You could call `StepContext.saveState` to ensure that all output is > recorded even if Jenkins is restarted in the middle of the stage. > Other than that, I think it would work, other than the scalability > problem. > -- 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/f465c526-d3a1-456c-8c29-647dec6e4634%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
