On Tue, Nov 22, 2016 at 4:29 PM, Ted Xiao <[email protected]> wrote: > through the PR > https://github.com/jenkinsci/workflow-job-plugin/pull/27/files#diff-5ac278e2951f186bb7e2f76208e6ed05R76 > , there is a comment // TODO JENKINS-30777 decorate with > ConsoleLogFilter.all()
Yes—if and when a use case for applying a global (`@Extension`-registered) `ConsoleLogFilter` arises. AFAIK there are none; under JENKINS-38381, sending log results to an external system uses a different API. (`ConsoleLogFilter` is involved in the implementation, but these are locally created filters, not global extensions.) See the downstream https://github.com/jenkinsci/logstash-plugin/pull/18 for a (crude) example. Please note that development on this system is currently on hold. It is functionally complete and has basic test coverage, but is not production ready. I have not yet written up a friendly design guide. > Does that mean I need to use explicit declare such as > > withContext(new MyConsoleLogFilter()) { > sh 'process' > } No, it is transparent to job definitions. -- 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/CANfRfr3-sK0cmhH8ZMaafmpqcSQYjQhv5sTJo1MvzQAhTex%2BDw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
