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 Console
output. Same as using the options from pipeline configuration.
Having the publishers disabled by default would be a better starting point,
to avoid extra configuration. I'm now following JENKINS-46785.
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 even shown here(it should !?). None of them is installed on
TEST instance.
Dec 20, 2017 10:40:28 AM FINE
org.jenkinsci.plugins.pipeline.maven.publishers.FindbugsAnalysisPublisher
No org.codehaus.mojo:findbugs-maven-plugin:findbugs execution found
On console log, it could mention that they are not installed or even not
shown at all. At the moment, there is no indication that the plugins are
not installed.
In case of JGiven, it is not clear (at least for me) if the abort is due to
missing jenkins plugin or if the project being built, does not use jgiven.
In my understanding, I would assume the latter.
[debug] [withMaven] Run 'Findbugs Publisher'...
[debug] [withMaven] Run 'JGiven Publisher'...
[debug] [withMaven] jgivenPublisher - JGiven not found within your project
dependencies, aborting.
Not sure if this input is already being considered (our previsously
discarded) but if you think it should have a new bug report open, let me
know :)
On Friday, 15 December 2017 00:53:50 UTC+1, Cyrille Le Clerc wrote:
>
> 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 what happened:
>
> - "Use pipeline defined publisher for 'Findbugs Publisher'" --> the
> config of the findbugs publisher is defined in the pipeline, in
> "withMaven(options:[findbugsPublisher(...)]"
> - "Skip 'Findbugs Publisher' disabled by configuration" --> the
> Findbugs Publisher is disabled
> - "pipelineGraphPublisher - triggerDownstreamPipelines" --> even if
> you disable the "pipelineGraphPublisher" by configuration, we have a
> listener of the pipeline build completion to decide if we trigger
> downstream pipelines. We need to wait for the completion of the build
> because the downstream pipeline trigger strategy is based on the result of
> the upstream build, you probably don't want to trigger downstream
> pipelines
> if your build failed.
>
> Stephen Connolly mentioned another use case:disabling all the
> publishers unless they are explicitly enabled in the pipeline
> ("withMaven(options:[myPublisher(enabled:
> true])"). James Nord had created a while ago the RFE JENKINS-46785 add a
> way to disable all reporters (and selectively enable a few)
> <https://www.google.com/url?q=https%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FJENKINS-46785&sa=D&sntz=1&usg=AFQjCNEsQIiR9rW44gUjN7gVQD32PZNnDQ>
> .
> If have started to work on it with
> https://github.com/jenkinsci/pipeline-maven-plugin/pull/116 and James
> validated the user Experience. I'll provide details later.
>
> Did this clarify your messages?
>
> Cyrille
>
>
>
> On Thursday, December 14, 2017 at 11:46:07 AM UTC+1, nco...@lbisa.com
> wrote:
>>
>> 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 instances.
>>
>> Additionally, tested remove the logger from test and seems that the
>> default console output is the same as:
>> org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution
>>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/1b928717-df20-41ae-82fa-c5b7b1b017db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
