-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins 2.73
Parametrized Trigger 2.35.2
I am guessing that Pipeline jobs do not (or cannot) provide the capability to determine what jobs trigger them, but the FreestyleJob itself does not indicate (either on the build page or in the console output) that it triggered a PipelineJob.
Console Output looks as if nothing happened at all:
00:00:00.000 commit notification xxxxx 00:00:00.072 [EnvInject] - Loading node environment variables. 00:00:00.081 Building remotely on xxxxxx 00:00:10.452 No emails were triggered. 00:00:10.471 Started calculate disk usage of build 00:00:10.472 Finished Calculation of disk usage of build in 0 seconds 00:00:10.482 Started calculate disk usage of workspace 00:00:10.610 Finished Calculation of disk usage of workspace in 0 seconds 00:00:10.612 Notifying upstream projects of job completion 00:00:10.616 No emails were triggered. 00:00:10.616 Finished: SUCCESS
However, the downstream PipelineJob was correctly triggered.
See configuration:
Steps to reproduce:
- Create a parameterized pipeline job
- Create a freestyle job that triggers the pipeline job with or without parameters.
- Run freestyle job
- Review console log.
[JENKINS-47352] No indication that a FreestyleJob triggered a PipelineJob
| Description |
Original:
I am guessing that Pipeline jobs do not (or cannot) provide the capability to determine what jobs trigger them, but the FreestyleJob itself does not indicate (either on the build page or in the console output) that it triggered a PipelineJob. Console Output looks as if nothing happened at all: *00:00:10.452* No emails were triggered.*00:00:10.471* Started calculate disk usage of build*00:00:10.472* Finished Calculation of disk usage of build in 0 seconds*00:00:10.482* Started calculate disk usage of workspace*00:00:10.610* Finished Calculation of disk usage of workspace in 0 seconds*00:00:10.612* Notifying upstream projects of job completion*00:00:10.616* No emails were triggered.*00:00:10.616* Finished: SUCCESS However, the downstream PipelineJob was correctly triggered. See configuration: !image-2017-10-09-06-53-11-921.png! h2. Steps to reproduce: # Create a parameterized pipeline job # Create a freestyle job that triggers the pipeline job with or without parameters. # Run freestyle job # Review console log. |
New:
I am guessing that Pipeline jobs do not (or cannot) provide the capability to determine what jobs trigger them, but the FreestyleJob itself does not indicate (either on the build page or in the console output) that it triggered a PipelineJob. Console Output looks as if nothing happened at all: {code:java} 00:00:00.000 commit notification xxxxx 00:00:00.072 [EnvInject] - Loading node environment variables. 00:00:00.081 Building remotely on xxxxxx 00:00:10.452 No emails were triggered. 00:00:10.471 Started calculate disk usage of build 00:00:10.472 Finished Calculation of disk usage of build in 0 seconds 00:00:10.482 Started calculate disk usage of workspace 00:00:10.610 Finished Calculation of disk usage of workspace in 0 seconds 00:00:10.612 Notifying upstream projects of job completion 00:00:10.616 No emails were triggered. 00:00:10.616 Finished: SUCCESS {code} However, the downstream PipelineJob was correctly triggered. See configuration: !image-2017-10-09-06-53-11-921.png! h2. Steps to reproduce: # Create a parameterized pipeline job # Create a freestyle job that triggers the pipeline job with or without parameters. # Run freestyle job # Review console log. |
