Active Choices Reactive and Reactive Reference parameters can be dynamically updated(cascade update) when the value of other job UI control(s) change(s).Active Choices Reactive and Reactive Reference parameters dynamically generate value options for a build parameter using a Groovy script or a Scriptler script.Similar to Active Choices Parameter above: A text box filter can be optionally shown to aid in filtering the value options.Īctive Choices Reactive and Reactive Reference Parametersīoth of these parameters have additional useful behaviors and Reactive Reference has some unique rendering options.Active Choices parameters can be rendered as standard selection lists, check boxes and radio buttons.An Active Choices parameter dynamically generates a list of value options for a build parameter using a Groovy script or a script from the Scriptler catalog.We will then provide a guide to their configuration. We will introduce the Active Choices based UI controls by briefly describing their behavior and rendering characteristics. rendered with a variety of UI controls, including dynamic HTML (see NOTE above on the security risks).multi-valued (can have more than one value).dynamically updated based on other UI parameters.dynamically generated (using Groovy or a Scriptler script).When that issue is closed, the plug-in should work fine with Pipelines, DSL, timers, cron, REST-API-triggered jobs, etc.Īctive Choices parameters allow users to select value(s) for a job parameter. Follow JENKINS-63284 for updates on a version that does not require the UI. We navigate the DOM using JavaScript to create the relationship and reactivity between parameters. NOTE: The plug-in was developed in a way that it relies heavily on the HTML/DOM of the Jenkins UI. When configuring jobs with this feature, keep in mind how the parameter will be rendered and whether it could be a security issue. NOTE: The Reactive Reference Parameter allows for parameters to be displayed as formatted HTML. Active Choices Reactive Reference Parameter.Once the plugin is installed, three new parameter types become available: These custom scripts support the use of the Jenkins Java API, system environment variables, global node properties, and potentially external Java and Javascript libraries. Active Choices parameters can be dynamically updated and can be rendered as combo-boxes, check-boxes, radio-buttons or rich HTML UI widgets.Īctive Choices parameters are scripted using Groovy, or (optionally) Scriptler Groovy scripts. The sum of the sizes of all of the installed components can be later accessed through the built-in variable $.The Active Choices plugin is used in parametrized freestyle Jenkins jobs to create scripted, dynamic and interactive job parameters. If 0, then it will automatically be calculated based on the size of the packed files. : Required disk space in the target system.

: Whether or not the component can be edited in the component selection page. : Whether or not the component is visible in the component selection page. If the component is not selected, its action lists won’t be executed and its folders won’t be unpacked. : Whether or not the component is selected. This detailed description will be displayed when clicking in the component description in the component selection page. : A detailed description of the component. This description will be included in the list of the visible components presented to the user. This name must be unique and just contain alphanumeric characters and underscores.

Installbuilder choiceparameter value