Re: ConsoleLogFilter not working for builds on slaves

OK - thanks for the info. JENKINS-38381 definitely sounds like the way forward - keeping an eye on that.. On Friday, 19 January 2018 20:05:56 UTC, Jesse Glick wrote: > > On Fri, Jan 19, 2018 at 2:06 PM, Tim Webster > wrote: > > Could I use 'contextual' ConsoleLogFilter

Re: ConsoleLogFilter not working for builds on slaves

On Fri, Jan 19, 2018 at 2:06 PM, Tim Webster wrote: > Could I use 'contextual' ConsoleLogFilter to do what I need then? If what you need is simply to *copy* all log lines somewhere else, performance be damned, and you do not mind this being configured on a per-job basis,

Re: ConsoleLogFilter not working for builds on slaves

Could I use 'contextual' ConsoleLogFilter to do what I need then? I confess I don't really know what that means though - I'll look at the Timestamper plugin. Although if JENKINS-38381 is going to be the preferred approach, I can also wait for that - or do both. This is an internal project at

Re: ConsoleLogFilter not working for builds on slaves

On Fri, Jan 19, 2018 at 12:44 PM, Markus Winter wrote: > Why is ConsoleLogFilter not supported in pipeline. Because…it isn’t yet. And JENKINS-38381, the better approach, was blocked for the moment due to lack of test infrastructure. > Timestamper plugin is also using a

Re: ConsoleLogFilter not working for builds on slaves

Why is ConsoleLogFilter not supported in pipeline. Timestamper plugin is also using a ConsoleLogFilter to add the timestamps in pipeline (https://github.com/jenkinsci/timestamper-plugin/blob/master/src/main/java/hudson/plugins/timestamper/pipeline/TimestamperStep.java) Sure it has the

Re: ConsoleLogFilter not working for builds on slaves

On Fri, Jan 19, 2018 at 11:50 AM, Tim Webster wrote: > pipeline doesn't work on master either. No, `ConsoleLogFilter` is not supported for Pipeline currently. See JENKINS-38381, some variant of which would be the preferred API for adding this kind of functionality. --

Re: ConsoleLogFilter not working for builds on slaves

apologies - pipeline doesn't work on master either. I will look at the pipeline support for plugins stuff... Thanks On Friday, 19 January 2018 16:34:19 UTC, Tim Webster wrote: > > Just realised I think it's something to do with it being a Pipeline job - > a freestyle job seems to work on the

Re: ConsoleLogFilter not working for builds on slaves

Just realised I think it's something to do with it being a Pipeline job - a freestyle job seems to work on the remote slave. So: - Freestyle job works everywhere - Pipeline job only on master. Any ideas? On Friday, 19 January 2018 15:05:08 UTC, Jesse Glick wrote: > > On Fri, Jan 19, 2018 at

Re: ConsoleLogFilter not working for builds on slaves

On Fri, Jan 19, 2018 at 9:47 AM, Tim Webster wrote: > Was wondering if I need to use > a different extension point or something Not that I am aware of. Sounds like a bug offhand. -- You received this message because you are subscribed to the Google Groups "Jenkins

Re: ConsoleLogFilter not working for builds on slaves

Basically I just wanted a simple plugin that could forward console logs to a remote collector. The existing ones around are pretty specific the the collector/indexer (e.g. Splunk, ELK, Logstash, etc). We're looking at using OK Log, which only requires a host and port to connect to:

Re: ConsoleLogFilter not working for builds on slaves

On Fri, Jan 19, 2018 at 7:54 AM, Tim Webster wrote: > I've written a plugin that forwards console logs to a remote TCP log > collector, using a ConsoleLogFilter. I am not sure of your specific problem, but BTW JENKINS-38381 and related issues propose a more solid

ConsoleLogFilter not working for builds on slaves

Hi, I've written a plugin that forwards console logs to a remote TCP log collector, using a ConsoleLogFilter. It works perfectly for jobs running on master, but gets ignored for jobs running on slaves. It's borrowing heavily from the Splunk plugin in that it 'tees' the console logs both to