-
Bug
-
Resolution: Fixed
-
Major
-
None
-
WinXP, Linux
I have a managed script which accepts two parameters.
I have a job where I want to call this script only when the specific condition is met.
So I reconfigure that job and hit 'save' and no error occurs. Then I reload webpage and see that the buildstep is saved but its arguments are not.
Saving fails both for 'Conditional step (Single)' and for 'Conditional step (Multiple)'
UPD: jenkins: 1.480.3
plugins: conditional step : 1.2
managed scripts : 1.0.1
config file provider: 2.2.1
[JENKINS-15995] Arguments passed to Managed Script called in Conditional BuildStep could not be saved
Description |
Original:
I have a managed script which accepts two parameters. I have a job where I want to call this script only when the specific condition is met. So I reconfigure that job and hit 'save' and no error occurs. Then I reload webpage and see that the buildstep is saved but its arguments are not. Saving fails both for 'Conditional step (Single)' and for 'Conditional step (Multiple)' |
New:
I have a managed script which accepts two parameters. I have a job where I want to call this script only when the specific condition is met. So I reconfigure that job and hit 'save' and no error occurs. Then I reload webpage and see that the buildstep is saved but its arguments are not. Saving fails both for 'Conditional step (Single)' and for 'Conditional step (Multiple)' UPD: jenkins: 1.480.3 plugins: conditional step : 1.2 managed scripts : 1.0.1 config file provider: 2.2.1 |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 146797 ] | New: JNJira + In-Review [ 192089 ] |
I'm currently on vacation, but I'll look into it soon...