-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
Jenkins LTS 2.176.2
Pipeline Maven Plugin 3.8.0
-
-
1203.v75b_321f1c89f
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.
[withMaven] downstreamPipelineTriggerRunListener - completed in 60330 ms
My jenkins system is air-gapped and I am unable to provide logs (only re-typed snippets)
- is duplicated by
-
-
- Closed
-
- links to
[JENKINS-62407] Builds displaying "downstreamPipelineTriggerRunListener" when not configured to do so
Ryan Fox
created issue -
Ryan Fox
made changes -
| 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 -
| 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 -
| 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 -
| 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 -
| 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 -
| 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) |
| Assignee | Original: Alvaro Lobato [ alobato ] |
Benoit
made changes -
| Assignee | New: Benoit [ bguerin ] |
Benoit
made changes -
| Link |
New:
This issue is duplicated by |
Benoit
made changes -
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
