• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Component/s: pipeline-maven-plugin
• Labels:

  None
• Environment:

  Jenkins LTS 2.176.2
  Pipeline Maven Plugin 3.8.0

[JENKINS-62407] Builds displaying "downstreamPipelineTriggerRunListener" when not configured to do so

Ryan Fox created issue - 2020-05-22 19:55

Ryan Fox made changes - 2020-05-22 19:56

Description

Original: Seeing the following message appear in some jenkins jobs.  In many cases, the jobs are not doing any "withMaven" steps.  The task is using up an executor on the master node and with >60s duration, is using up too many resources.     [withMaven] downstreamPipelineTriggerRunListener - completed in 60330 ms   My jenkins system is air-gapped and I am unable to provide logs (only re-typed snippets)

New: Seeing the following message appear in some jenkins jobs.  In many cases, the jobs are not doing any "withMaven" steps (ex: npm builds).  The task is using up an executor on the master node and with >60s duration, is using up too many resources.      [withMaven] downstreamPipelineTriggerRunListener - completed in 60330 ms    My jenkins system is air-gapped and I am unable to provide logs (only re-typed snippets)

Ryan Fox made changes - 2020-05-22 19:56

Description

Original: Seeing the following message appear in some jenkins jobs.  In many cases, the jobs are not doing any "withMaven" steps (ex: npm builds).  The task is using up an executor on the master node and with >60s duration, is using up too many resources.      [withMaven] downstreamPipelineTriggerRunListener - completed in 60330 ms    My jenkins system is air-gapped and I am unable to provide logs (only re-typed snippets)

New: Seeing the following message appear in some jenkins jobs.  In many cases, the jobs are not doing any "withMaven" steps (ex: npm builds).  The task is using up an executor on the master node and with >60s duration, is using up too many resources.   {{ }} {{ [withMaven] downstreamPipelineTriggerRunListener - completed in 60330 ms}} {{  }} My jenkins system is air-gapped and I am unable to provide logs (only re-typed snippets)

Ryan Fox made changes - 2020-05-22 19:56

Description

Original: Seeing the following message appear in some jenkins jobs.  In many cases, the jobs are not doing any "withMaven" steps (ex: npm builds).  The task is using up an executor on the master node and with >60s duration, is using up too many resources.   {{ }} {{ [withMaven] downstreamPipelineTriggerRunListener - completed in 60330 ms}} {{  }} My jenkins system is air-gapped and I am unable to provide logs (only re-typed snippets)

New: Seeing the following message appear in some jenkins jobs.  In many cases, the jobs are not doing any "withMaven" steps (ex: npm builds).  The task is using up an executor on the master node and with >60s duration, is using up too many resources.   {{ }}  {{ [withMaven] downstreamPipelineTriggerRunListener - completed in 60330 ms}} My jenkins system is air-gapped and I am unable to provide logs (only re-typed snippets)

Ryan Fox made changes - 2020-05-22 19:56

Description

Original: Seeing the following message appear in some jenkins jobs.  In many cases, the jobs are not doing any "withMaven" steps (ex: npm builds).  The task is using up an executor on the master node and with >60s duration, is using up too many resources.   {{ }}  {{ [withMaven] downstreamPipelineTriggerRunListener - completed in 60330 ms}} My jenkins system is air-gapped and I am unable to provide logs (only re-typed snippets)

New: Seeing the following message appear in some jenkins jobs.  In many cases, the jobs are not doing any "withMaven" steps (ex: npm builds).  The task is using up an executor on the master node and with >60s duration, is using up too many resources.   {quote}{{{{ }}}} {{[withMaven] downstreamPipelineTriggerRunListener - completed in 60330 ms}}{quote} My jenkins system is air-gapped and I am unable to provide logs (only re-typed snippets)

Ryan Fox made changes - 2020-05-22 19:56

Description

Original: Seeing the following message appear in some jenkins jobs.  In many cases, the jobs are not doing any "withMaven" steps (ex: npm builds).  The task is using up an executor on the master node and with >60s duration, is using up too many resources.   {quote}{{{{ }}}} {{[withMaven] downstreamPipelineTriggerRunListener - completed in 60330 ms}}{quote} My jenkins system is air-gapped and I am unable to provide logs (only re-typed snippets)

New: Seeing the following message appear in some jenkins jobs.  In many cases, the jobs are not doing any "withMaven" steps (ex: npm builds).  The task is using up an executor on the master node and with >60s duration, is using up too many resources.   {quote}{{[withMaven] downstreamPipelineTriggerRunListener - completed in 60330 ms}} {quote} My jenkins system is air-gapped and I am unable to provide logs (only re-typed snippets)

Ryan Fox made changes - 2020-05-22 19:59

Description

Original: Seeing the following message appear in some jenkins jobs.  In many cases, the jobs are not doing any "withMaven" steps (ex: npm builds).  The task is using up an executor on the master node and with >60s duration, is using up too many resources.   {quote}{{[withMaven] downstreamPipelineTriggerRunListener - completed in 60330 ms}} {quote} My jenkins system is air-gapped and I am unable to provide logs (only re-typed snippets)

New: Seeing the following message appear in some jenkins jobs.  In many cases, the jobs are not doing any "withMaven" steps (ex: npm builds).  The task is using up an executor on the master node and with >60s duration, is using up too many resources.  The job will show the build is complete, but the console log output will keep spinning until this message appears. {quote}{{[withMaven] downstreamPipelineTriggerRunListener - completed in 60330 ms}} {quote} My jenkins system is air-gapped and I am unable to provide logs (only re-typed snippets)

Arnaud Héritier made changes - 2020-08-30 21:36

Assignee

Original: Alvaro Lobato [ alobato ]

Collapse comment: Benoit added a comment - 2021-12-26 15:28, Edited by Benoit - 2022-07-13 19:42

Benoit added a comment - 2021-12-26 15:28 - edited

Just one question : do you have both jobs doing

withMaven(...)
{ ... }

and others not doing 

withMaven

or only jobs not doing 

withMaven

 ?

Expand comment: Benoit added a comment - 2021-12-26 15:28, Edited by Benoit - 2022-07-13 19:42

Benoit added a comment - 2021-12-26 15:28 - edited Just one question : do you have both jobs doing withMaven(...) { ... } and others not doing  withMaven or only jobs not doing  withMaven  ?

Benoit made changes - 2021-12-26 15:28

Assignee

New: Benoit [ bguerin ]

Load more newer events