[users at bb.net] Handling additional log files

[Pierre Tardy]

Creating a followup step is what I would do as the simplest.

You can also do a ShellCommand subclass that will download the logs
conditionally in "evaluateCommand".
You can use getFileContentFromWorker from CompositeStepMixin and then
addFullLog.
This has the caveat of loading the full content of the log into memory,
which could not be scalable.

Another option is to always watch the log using ShellCommand's logfiles,
and delete them using data API in evaluateCommand.

Note that issue #3025 is only about waterfall. step hiding works in normal
buildsummary views, which are used everywhere else.

Regards,
Pierre


Le lun. 3 août 2020 à 11:06, Ryan Schmidt <buildbot at ryandesign.com> a
écrit :

>
>
> On Aug 3, 2020, at 03:38, Ryan Schmidt wrote:
>
> > I'm considering creating an additional build step that would only run if
> the previous step failed (can I do that?) that would find and cat each
> config.log.
>
> Or maybe I want the step to run every time, but if it doesn't find any
> config.log files (i.e. if the step produces nothing on stdout) then the
> step would be hidden using hideStepIf somehow.
>
> Except that according to https://github.com/buildbot/buildbot/issues/3025
> hideStepIf doesn't work anymore?
>
> _______________________________________________
> users mailing list
> users at buildbot.net
> https://lists.buildbot.net/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildbot.net/pipermail/users/attachments/20200803/a6379f42/attachment.html>