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 updates could be triggering this difference in 
behaviour.

Using *withEnv(['JENKINS_MAVEN_AGENT_DISABLED=true'])* disables all 
publishers (and all configurantion entries are not seen) except 

[withMaven] pipelineGraphPublisher - triggerDownstreamPipelines
[withMaven] Skip downstream job triggering for upstream build with ignored 
result status...
...


You still need to disable pipelineGraphPublisher with option 
*pipelineGraphPublisher(disabled: 
true)*.
Also, it seems that pipelineGraphPublisher is not in the plugin 
documentation <https://plugins.jenkins.io/pipeline-maven> but is available 
on Pipeline Syntax snippet generator.

On Wednesday, 13 December 2017 13:41:37 UTC+1, Stephen Connolly wrote:
>
> 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.
>

-- 
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/9f302194-4b22-4b50-a2c2-4fe8f125ee0d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to