You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What Operating System are you using (both controller, and any agents involved in the problem)?
This has been observed for the following scenarios:
Controller
Agent
Linux(ubuntu)
Linux(ubuntu)
Linux(ubuntu)
Windows-10
Reproduction steps
I've been able to reproduce with a simple dummy scenario:
Create a disabled freestyle job
New Freestyle
Name:01-Disabled
Description: This is a disabled project
Build: Add shell or Windows batch command
echo Hello I'm disabled
Disable the job
Create an an enabled freestyle job
New Freestyle
Name:02-Enabled
Desription:This project is enabled
Build: Add shell or Windows batch command
echo This step is enabled
Create a multijob that uses the two
New Multijob
Name: 00-Multijob
Desription: I call 01-Diabled and 02-Enabled
Build:
Add multijob phase
Name: P1
Job: 01-Disabled
Continue on Success
Add multimob phase
Name: P2
Job: 02-Enabled
Continue on Success
Run the multijob phase
View the job run information
It goes into infinite recursion in the display
Expected Results
It should not execute the disabled job.
The display should not go into infinite recursion. Previous releases of the plugin would display this as simply 02-Enabled, and not show 01-Disabled at all.
The following screenshot is from our real configuration when it was working (with 1.36). When we have the Test-Linux stage, after Build-Linux disabled. It's disabled in the Test-Linux job, NOT at the multijob layer.
Actual Results
Anything else?
This problem did not start until we upgraded to 611.v9d3180d752e6 from 1.36.
I've attached the config for the simple scenario I've explained. simple_example.zip
The text was updated successfully, but these errors were encountered:
We ran into this as well. The problem gets more noticeable if you allocate a lot of stack memory to the server (-Xss) because it cycles for a very long time and locks up the controller while recursing.
I tried downgrading to 1.36 and experienced the same infinite recursion when displaying the results of an old run that had a disabled job as part of the chain, so it's unclear how new this bug is. I have not figured out whether "new" runs will be healthier.
Our environment is Amazon Linux (redhat'ish) with Jenkins 2.346.3 (recent LTS) running on Java11.
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
This has been observed for the following scenarios:
Reproduction steps
I've been able to reproduce with a simple dummy scenario:
It goes into infinite recursion in the display
Expected Results
It should not execute the disabled job.
The display should not go into infinite recursion. Previous releases of the plugin would display this as simply 02-Enabled, and not show 01-Disabled at all.
The following screenshot is from our real configuration when it was working (with 1.36). When we have the Test-Linux stage, after Build-Linux disabled. It's disabled in the Test-Linux job, NOT at the multijob layer.
Actual Results
Anything else?
This problem did not start until we upgraded to 611.v9d3180d752e6 from 1.36.
I've attached the config for the simple scenario I've explained.
simple_example.zip
The text was updated successfully, but these errors were encountered: