>
> I still think that when pipeline-maven auxiliar plugins are not installed,
> it shouldn't display that information on console log, when using this
> logger:
> org.jenkinsci.plugins.pipeline.maven
>
> On logger output, one can see that the findbugs plugin is not found and
> jgiven is not
Hi Cyrille
Thanks for your clarification.
I now have the TEST and PROD using the same logger
(org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution >> ALL).
Disabling the publishers on Global Tools Configuration screen, the
publishers are shown as "Skip ... disabled by configuration" in
Hello,
You had enabled logging on your test master and we display in the build
logs the logs of the plugin, this is why you had these messages on your
test masters.
You can disable globally publishers through the Global Tools Configuration
screen.
The message may not be intuitive but here is
Just noticed that PROD has a different logger. It is using:
org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution
and test was using:
org.jenkinsci.plugins.pipeline.maven
Both were set to log level ALL.
After set test instance to use the same logger, the output are similar in
both
Both PROD and test have the same Global Tool Configuration Maven
Configuration (defaults and no publishers configured) and are running the
same versions of Pipeline Maven Integration (3.0.3).
PROD is on Jenkins 2.92 and test on 2.93, so not sure if that and PROD not
restarted after plugin
Is prod running an older version of the plugin. Disabling is only a recent
feature. Also see
https://issues.jenkins-ci.org/plugins/servlet/mobile#issue/JENKINS-46785
for a related request about being able to disable default publishers so
that options only specifies the ones you want configured.
Hi
Does any one knows what provides and how to disable Maven not to trigger
"*Maven
Publishers with default configuration*:" info in Console Output?
If I run the same code on 2 different Jenkins instances, one of them do not
have this kind of diferenciation between Maven Publishers set by
