[JIRA] (JENKINS-49894) Active Choices Reactive Reference Parameter triggering the groovy script twice

[brunodepau...@yahoo.com.br (JIRA)]

Title: Message Title

Bruno P. Kinoshita commented on JENKINS-49894   Re: Active Choices Reactive Reference Parameter triggering the groovy script twice Have just spent some minutes debugging it, and I believe I now understand what's causing the issue. Can't fix it right now due to limited bandwidth to develop, but the below is a short explanation of the problem (and also a note to myself in the future, when working on this issue again). I only reproduced it on the first time the page is loaded. Debugging, it is possible to see the first call comes from Jelly tags being evaluated. And the second call comes from _javascript_ code. The issue appears to be that when we put the elements on the UI, we also intentionally call the update method on the server side, to get the right values. Then once everything is loaded, there is a JS call to refresh the elements' values. The ideal approach would be to have Jelly creating the elements, then using JS to start the execution. But that's not easy to implement without breaking other things. Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.