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)?
Windows (Controller)
Windows (Agent)
Reproduction steps
Create a new 'Extended Choice Parameter'
Name 'Test'
Select 'JSON Parameter Type'
Select 'JSON Parameter Config Javascript'
Put simple IF statement with alert message if (0 < 5) alert ('Test')
Save configuration
Click on Build with Parameters
(!) Syntax error caught in debug mode in web browser (see the attached screenshot below)
Expected Results
It pops up an alert message when go on 'Build with Parameters' page
Actual Results
No popup with an alert message appears because of syntax error in used javascript when go on 'Build with Parameters' page
Anything else?
It worked fine in the previous version extended-choice-parameter:359.v35dcfdd0c20d Currently when logical operators like <, >, &&, || are used in javascript they are converted to HTML chars
The text was updated successfully, but these errors were encountered:
Jenkins and plugins versions report
Environment
Jenkins: 2.401.2
OS: Windows Server 2019 - 10.0
Java: 11.0.19 - Azul Systems, Inc. (OpenJDK 64-Bit Server VM)
Plugin:
Name: extended-choice-parameter
Version: 373.v1a_ecea_fdf2a_a_
What Operating System are you using (both controller, and any agents involved in the problem)?
Windows (Controller)
Windows (Agent)
Reproduction steps
Expected Results
It pops up an alert message when go on 'Build with Parameters' page
Actual Results
No popup with an alert message appears because of syntax error in used javascript when go on 'Build with Parameters' page
Anything else?
It worked fine in the previous version extended-choice-parameter:359.v35dcfdd0c20d Currently when logical operators like <, >, &&, || are used in javascript they are converted to HTML chars
The text was updated successfully, but these errors were encountered: