-
Bug
-
Resolution: Unresolved
-
Major
-
None
Multiple assigment parameters in referencedParameters doesn't initialize its values properly.
There're releaseBranch, releaseNumber and serviceName parameters (see the attached file).
releaseNumber property depends on releaseBranch
and serviceName property depends on both releaseNumber and releaseBranch
The Groove script of releaseBranch returns "main" value always. This value is set up as first chosen parameter in the lookup component automatically.
The Groovy script of releaseNumber depends on releaseBranch and return the list ([100, 101, 102, 103]). The lookup component initializes the default value 100 as well.
It's expected that these two initialized values ("main" and 100) are available for the Groovy Script in serviceName, but it's not.
When the page is refreshed the ['Could not get releaseBranch param'] and ['Could not get either releaseBranch or releaseNumber param(s)'] values are blinked. It points on executing fallbackScript scripts.
Moreover the error has been picked up from the Jenkins log file when fallbackScript is not used in Jenkinsfile script (see attached jenkins.log file). A recorded video (15.10.2024_08.38.35_REC.mp4) shows infinity scrolling icon when fallbackScript is not used.
Release version is
2.8.4
[JENKINS-73928] The referencedParameters property does't trigger properties
Description |
Original:
Multiple assigment referencedParameters doesn't initialize linked values.
There're releaseBranch, releaseNumber and serviceName parameters (see the attached file). *releaseNumber* property depends on *releaseBranch* and *serviceName* property depends on both *releaseNumber* and *releaseBranch* The Groove script of releaseBranch returns "main" value always. This value is set up as first chosen parameter in the lookup component automatically. The Groovy script of releaseNumber depends on releaseBranch and return a list ([100, 101, 102, 103]). The lookup components initializes the default value 100 as well. It's expected that these two initialized values ("main" and 100) are available for reading in the Groovy Script in serviceName, but doesn't. Release version is [2.8.4|https://updates.jenkins.io/download/plugins/uno-choice/2.8.4/uno-choice.hpi] |
New:
Multiple assigment referencedParameters doesn't initialize linked values.
There're releaseBranch, releaseNumber and serviceName parameters (see the attached file). *releaseNumber* property depends on *releaseBranch* and *serviceName* property depends on both *releaseNumber* and *releaseBranch* The Groove script of releaseBranch returns "main" value always. This value is set up as first chosen parameter in the lookup component automatically. The Groovy script of releaseNumber depends on releaseBranch and return the list ([100, 101, 102, 103]). The lookup component initializes the default value 100 as well. It's expected that these two initialized values ("main" and 100) are available for the Groovy Script in serviceName, but it's not. Release version is [2.8.4|https://updates.jenkins.io/download/plugins/uno-choice/2.8.4/uno-choice.hpi] |
Description |
Original:
Multiple assigment referencedParameters doesn't initialize linked values.
There're releaseBranch, releaseNumber and serviceName parameters (see the attached file). *releaseNumber* property depends on *releaseBranch* and *serviceName* property depends on both *releaseNumber* and *releaseBranch* The Groove script of releaseBranch returns "main" value always. This value is set up as first chosen parameter in the lookup component automatically. The Groovy script of releaseNumber depends on releaseBranch and return the list ([100, 101, 102, 103]). The lookup component initializes the default value 100 as well. It's expected that these two initialized values ("main" and 100) are available for the Groovy Script in serviceName, but it's not. Release version is [2.8.4|https://updates.jenkins.io/download/plugins/uno-choice/2.8.4/uno-choice.hpi] |
New:
Multiple assigment parameters in referencedParameters doesn't initialize its values properly.
There're releaseBranch, releaseNumber and serviceName parameters (see the attached file). *releaseNumber* property depends on *releaseBranch* and *serviceName* property depends on both *releaseNumber* and *releaseBranch* The Groove script of releaseBranch returns "main" value always. This value is set up as first chosen parameter in the lookup component automatically. The Groovy script of releaseNumber depends on releaseBranch and return the list ([100, 101, 102, 103]). The lookup component initializes the default value 100 as well. It's expected that these two initialized values ("main" and 100) are available for the Groovy Script in serviceName, but it's not. Release version is [2.8.4|https://updates.jenkins.io/download/plugins/uno-choice/2.8.4/uno-choice.hpi] |
Description |
Original:
Multiple assigment parameters in referencedParameters doesn't initialize its values properly.
There're releaseBranch, releaseNumber and serviceName parameters (see the attached file). *releaseNumber* property depends on *releaseBranch* and *serviceName* property depends on both *releaseNumber* and *releaseBranch* The Groove script of releaseBranch returns "main" value always. This value is set up as first chosen parameter in the lookup component automatically. The Groovy script of releaseNumber depends on releaseBranch and return the list ([100, 101, 102, 103]). The lookup component initializes the default value 100 as well. It's expected that these two initialized values ("main" and 100) are available for the Groovy Script in serviceName, but it's not. Release version is [2.8.4|https://updates.jenkins.io/download/plugins/uno-choice/2.8.4/uno-choice.hpi] |
New:
Multiple assigment parameters in referencedParameters doesn't initialize its values properly.
There're releaseBranch, releaseNumber and serviceName parameters (see the attached file). *releaseNumber* property depends on *releaseBranch* and *serviceName* property depends on both *releaseNumber* and *releaseBranch* The Groove script of releaseBranch returns "main" value always. This value is set up as first chosen parameter in the lookup component automatically. The Groovy script of releaseNumber depends on releaseBranch and return the list ([100, 101, 102, 103]). The lookup component initializes the default value 100 as well. It's expected that these two initialized values ("main" and 100) are available for the Groovy Script in serviceName, but it's not. When the page is refreshed the ['Could not get releaseBranch param'] and ['Could not get either releaseBranch or releaseNumber param(s)'] values are blinked. It points on executing fallbackScript scripts. Moreover the error has been picked up from the Jenkins log file when fallbackScript is not used in Jenkinsfile script (. Release version is [2.8.4|https://updates.jenkins.io/download/plugins/uno-choice/2.8.4/uno-choice.hpi] |
Description |
Original:
Multiple assigment parameters in referencedParameters doesn't initialize its values properly.
There're releaseBranch, releaseNumber and serviceName parameters (see the attached file). *releaseNumber* property depends on *releaseBranch* and *serviceName* property depends on both *releaseNumber* and *releaseBranch* The Groove script of releaseBranch returns "main" value always. This value is set up as first chosen parameter in the lookup component automatically. The Groovy script of releaseNumber depends on releaseBranch and return the list ([100, 101, 102, 103]). The lookup component initializes the default value 100 as well. It's expected that these two initialized values ("main" and 100) are available for the Groovy Script in serviceName, but it's not. When the page is refreshed the ['Could not get releaseBranch param'] and ['Could not get either releaseBranch or releaseNumber param(s)'] values are blinked. It points on executing fallbackScript scripts. Moreover the error has been picked up from the Jenkins log file when fallbackScript is not used in Jenkinsfile script (. Release version is [2.8.4|https://updates.jenkins.io/download/plugins/uno-choice/2.8.4/uno-choice.hpi] |
New:
Multiple assigment parameters in referencedParameters doesn't initialize its values properly.
There're releaseBranch, releaseNumber and serviceName parameters (see the attached file). *releaseNumber* property depends on *releaseBranch* and *serviceName* property depends on both *releaseNumber* and *releaseBranch* The Groove script of releaseBranch returns "main" value always. This value is set up as first chosen parameter in the lookup component automatically. The Groovy script of releaseNumber depends on releaseBranch and return the list ([100, 101, 102, 103]). The lookup component initializes the default value 100 as well. It's expected that these two initialized values ("main" and 100) are available for the Groovy Script in serviceName, but it's not. When the page is refreshed the ['Could not get releaseBranch param'] and ['Could not get either releaseBranch or releaseNumber param(s)'] values are blinked. It points on executing fallbackScript scripts. Moreover the error has been picked up from the Jenkins log file when fallbackScript is not used in Jenkinsfile script (see attached jenkins.log file). Release version is [2.8.4|https://updates.jenkins.io/download/plugins/uno-choice/2.8.4/uno-choice.hpi] |
Attachment | New: jenkins.log [ 63435 ] |
Description |
Original:
Multiple assigment parameters in referencedParameters doesn't initialize its values properly.
There're releaseBranch, releaseNumber and serviceName parameters (see the attached file). *releaseNumber* property depends on *releaseBranch* and *serviceName* property depends on both *releaseNumber* and *releaseBranch* The Groove script of releaseBranch returns "main" value always. This value is set up as first chosen parameter in the lookup component automatically. The Groovy script of releaseNumber depends on releaseBranch and return the list ([100, 101, 102, 103]). The lookup component initializes the default value 100 as well. It's expected that these two initialized values ("main" and 100) are available for the Groovy Script in serviceName, but it's not. When the page is refreshed the ['Could not get releaseBranch param'] and ['Could not get either releaseBranch or releaseNumber param(s)'] values are blinked. It points on executing fallbackScript scripts. Moreover the error has been picked up from the Jenkins log file when fallbackScript is not used in Jenkinsfile script (see attached jenkins.log file). Release version is [2.8.4|https://updates.jenkins.io/download/plugins/uno-choice/2.8.4/uno-choice.hpi] |
New:
Multiple assigment parameters in referencedParameters doesn't initialize its values properly.
There're releaseBranch, releaseNumber and serviceName parameters (see the attached file). *releaseNumber* property depends on *releaseBranch* and *serviceName* property depends on both *releaseNumber* and *releaseBranch* The Groove script of releaseBranch returns "main" value always. This value is set up as first chosen parameter in the lookup component automatically. The Groovy script of releaseNumber depends on releaseBranch and return the list ([100, 101, 102, 103]). The lookup component initializes the default value 100 as well. It's expected that these two initialized values ("main" and 100) are available for the Groovy Script in serviceName, but it's not. When the page is refreshed the ['Could not get releaseBranch param'] and ['Could not get either releaseBranch or releaseNumber param(s)'] values are blinked. It points on executing fallbackScript scripts. Moreover the error has been picked up from the Jenkins log file when fallbackScript is not used in Jenkinsfile script (see attached jenkins.log file). Release version is [2.8.4|https://updates.jenkins.io/download/plugins/uno-choice/2.8.4/uno-choice.hpi] |
Attachment | New: 15.10.2024_08.38.35_REC.mp4 [ 63436 ] |
Description |
Original:
Multiple assigment parameters in referencedParameters doesn't initialize its values properly.
There're releaseBranch, releaseNumber and serviceName parameters (see the attached file). *releaseNumber* property depends on *releaseBranch* and *serviceName* property depends on both *releaseNumber* and *releaseBranch* The Groove script of releaseBranch returns "main" value always. This value is set up as first chosen parameter in the lookup component automatically. The Groovy script of releaseNumber depends on releaseBranch and return the list ([100, 101, 102, 103]). The lookup component initializes the default value 100 as well. It's expected that these two initialized values ("main" and 100) are available for the Groovy Script in serviceName, but it's not. When the page is refreshed the ['Could not get releaseBranch param'] and ['Could not get either releaseBranch or releaseNumber param(s)'] values are blinked. It points on executing fallbackScript scripts. Moreover the error has been picked up from the Jenkins log file when fallbackScript is not used in Jenkinsfile script (see attached jenkins.log file). Release version is [2.8.4|https://updates.jenkins.io/download/plugins/uno-choice/2.8.4/uno-choice.hpi] |
New:
Multiple assigment parameters in referencedParameters doesn't initialize its values properly.
There're releaseBranch, releaseNumber and serviceName parameters (see the attached file). *releaseNumber* property depends on *releaseBranch* and *serviceName* property depends on both *releaseNumber* and *releaseBranch* The Groove script of releaseBranch returns "main" value always. This value is set up as first chosen parameter in the lookup component automatically. The Groovy script of releaseNumber depends on releaseBranch and return the list ([100, 101, 102, 103]). The lookup component initializes the default value 100 as well. It's expected that these two initialized values ("main" and 100) are available for the Groovy Script in serviceName, but it's not. When the page is refreshed the ['Could not get releaseBranch param'] and ['Could not get either releaseBranch or releaseNumber param(s)'] values are blinked. It points on executing fallbackScript scripts. Moreover the error has been picked up from the Jenkins log file when fallbackScript is not used in Jenkinsfile script (see attached jenkins.log file). A recorded video ({*}15.10.2024_08.38.35_REC.mp4{*}) shows infinity scrolling icon when fallbackScript is not used. Release version is [2.8.4|https://updates.jenkins.io/download/plugins/uno-choice/2.8.4/uno-choice.hpi] |
Priority | Original: Minor [ 4 ] | New: Major [ 3 ] |