Re: Disable withMaven publishers default configuration

> > 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

Re: Disable withMaven publishers default configuration

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

Re: Disable withMaven publishers default configuration

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

Re: Disable withMaven publishers default configuration

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

Disable withMaven publishers default configuration

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

Track docker images usage

Hi Is there any tips on how to be able to track the overall docker image usage in a Jenkins server? Like X image is being used by Y or Y and Z projects. Tried using the CloudBees Docker Traceability plugin but the link

Job properties are not (should be !?) cumulative

Project properties are not cumulative when additional settings are set during the pipeline. For example, if setting a Parameterized build and later in the pipeline, a Discard Old Builds is set, the Parameterized build is unset. I had this happening when the Discard Old Builds were used in a

Re: Pipeline one-liner causes hanging job ?

> > This caused my Pipeline Job to hang - so I have to kill it. > As mentioned in this issue, you can use as workaround assert false : 'oh no!' Not sure if the resolution was already released. -- You received this message because you

Re: Techniques for managing an scp call to a remote box, with a specific principal

> > Yes, I've seen those two plugins, but I don't understand how I would use > either of these from a pipeline job. As Rachel mentioned, Publish over ssh is still lacking pipeline support. You can check additional pipeline plugins compatibility here