I guess the other approach is to have the plugin append to the Jenkins
system log. The plugin is using slf4j with jul-to-slf4j with a log4j2.xml
configuration that goes to SYSTEM_OUT. Before I start trying to find the
write logging settings, is this possible?
Thanks
On Tuesday, December 19,
Running build related things in the Jenkins JVM is kind of an anti-pattern
IMHO. Better to fork a JVM that you have complete control over the
classloader, in which case the logging goes to STDOUT and you just pipe
that to the build log
On 18 December 2017 at 20:16, Shaun Thompson
I'm looking to output external logging, API's that use slf4j, to the build
logs.
On Monday, December 18, 2017 at 8:16:18 AM UTC-6, Jesse Glick wrote:
>
> On Sat, Dec 16, 2017 at 2:18 PM, Shaun Thompson > wrote:
> > intercept logging in a Pipeline
> > coming from the
On Sat, Dec 16, 2017 at 2:18 PM, Shaun Thompson wrote:
> intercept logging in a Pipeline
> coming from the TaskListener.PrintStream getLogger() for other API's that
> are using slf4j.
Not sure what you are talking about. Build logs (`TaskListener`) and
the system log
I'm looking for ideas on a clean way to intercept logging in a Pipeline
coming from the TaskListener.PrintStream getLogger() for other API's that
are using slf4j.
Thanks
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe