url stringlengths 11 2.25k | text stringlengths 88 50k | ts timestamp[s]date 2026-01-13 08:47:33 2026-01-13 09:30:40 |
|---|---|---|
https://issues.jenkins.io/login.jsp?os_destination=https%3A%2F%2Fissues.jenkins.io%2Fsecure%2Fissues | Log into Atlassian - Jenkins Jira Log in Skip to main content Skip to sidebar Dashboards Projects Issues Give feedback to Atlassian Help Keyboard Shortcuts About Jira Jira Credits Log In 📢 Jenkins core issues have been migrated to GitHub , no new core issues can be created in Jira Atlassian Jira Project Management Software About Jira Report a problem Powered by a free Atlassian Jira open source license for The Linux Foundation. Try Jira - bug tracking software for your team. Atlassian | 2026-01-13T09:29:33 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3AinvisibleEntry | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:33 |
https://cloudflare.com/it-it/events/ | Eventi di Cloudflare | Cloudflare Registrati Lingue English English (United Kingdom) Deutsch Español (Latinoamérica) Español (España) Français Italiano 日本語 한국어 Polski Português (Brasil) Русский 繁體中文 简体中文 Piattaforma Connettività cloud La connettività cloud di Cloudflare offre oltre 60 servizi di rete, sicurezza e prestazioni. Enterprise Per organizzazioni di grandi e medie dimensioni Piccola impresa Per le piccole organizzazioni Partner Diventa un partner Cloudflare Casi d'uso Modernizza le applicazioni Accelera le prestazioni Assicura la disponibilità delle app Ottimizza l'esperienza Web Modernizza la sicurezza Sostituisci la VPN Proteggiti dal phishing Proteggi le app Web e le API Modernizza le reti Rete di caffetterie Modernizza la WAN Semplifica la tua rete aziendale Argomenti CXO Adotta l'IA Integra l'IA negli ambienti di lavoro e nelle esperienze digitali Sicurezza dell'IA Applicazioni sicure di IA agentica e IA generativa Conformità dei dati Semplifica la conformità e riduci al minimo i rischi Crittografia post-quantistica Proteggi i dati e rispetta gli standard di conformità Settori Sanità Settore bancario Vendita al dettaglio Gaming Settore pubblico Risorse Guide sul prodotto Architetture di riferimento Report di analisi Impegno Eventi Demo Webinar Workshop Richiedi una demo Prodotti Prodotti Sicurezza dell&#039;ambiente di lavoro Zero Trust Network Access Secure Web Gateway Sicurezza delle e-mail Cloud Access Security Broker (CASB) Sicurezza delle applicazioni Protezione da attacchi DDoS L7 Web Application Firewall Sicurezza delle API Gestione dei bot Prestazioni delle applicazioni CDN DNS Smart Routing Load balancing Rete e SASE Protezione da attacchi DDoS L3/4 NaaS / SD- WAN Firewall-as-a-Service Interconnessione di rete Piani e prezzi Piani Enterprise Piani per piccole imprese Piani individuali Confronta i piani Servizi globali Pacchetti di supporto e successo Esperienza Cloudflare ottimizzata Servizi professionali Implementazione guidata da esperti Gestione tecnica dell'account Gestione tecnica mirata Assistenza per le operazioni di sicurezza Monitoraggio e risposta di Cloudflare Registrazione dominio Acquista e gestisci domini 1.1.1.1 Resolver DNS gratuito Risorse Guide sul prodotto Architetture di riferimento Report di analisi Demo e tour dei prodotti Aiutami a scegliere Sviluppatori Documentazione Libreria per sviluppatori Documentazione e guide Demo applicazioni Scopri cosa puoi costruire Tutorial Tutorial di creazione passo-passo Architettura di riferimento Diagrammi e modelli di progettazione Prodotti Intelligenza artificiale AI Gateway Osserva e controlla le app IA Workers AI Esegui modelli ML sulla nostra rete Elaborazione Observability Log, metriche e tracce Workers Crea e distribuisci app serverless Media Images Trasforma, ottimizza le immagini Realtime Crea app audio e video in tempo reale Archiviazione e database D1 Crea database SQL serverless R2 Archivia i dati senza costose tariffe in uscita Piani e prezzi Workers Crea e distribuisci app serverless Workers KV Archivio chiave-valore serverless per le app R2 Archivia i dati senza ingenti costi in uscita Esplora i progetti Le testimonianze dei clienti Demo IA in 30 secondi Guida rapida per iniziare Esplora Workers Playground Crea, testa e distribuisci Sviluppatori Discord Unisciti alla community Inizia a costruire Partner Partner network Cresci, innova e soddisfa le esigenze dei clienti con Cloudflare Portale Partner Trova risorse e registra offerte Tipi di partnership Programma PowerUP Fai crescere la tua attività mantenendo i tuoi clienti connessi e protetti Partner Technology Esplora il nostro ecosistema di partnership e integrazioni tecnologiche Global Systems Integrator (GSI) Supporta una trasformazione digitale su larga scala senza interruzioni Service Provider Scopri la nostra rete di stimati fornitori di servizi Programma di agenzia self-service Gestisci gli account self-service per i tuoi clienti Portale peer-to-peer Informazioni sul traffico per la tua rete Trova un partner Potenzia la tua attività: entra in contatto con i partner Cloudflare Powered+. Risorse Impegno Demo + tour dei prodotti Demo di prodotti on demand Case study Storie di successo con Cloudflare Webinar Discussioni approfondite Workshop Forum virtuali Libreria Guide utili, roadmap e altro ancora Report Approfondimenti dalla ricerca di Cloudflare Blog Approfondimenti tecnici e notizie sui prodotti Centro di apprendimento Strumenti formativi e contenuti dimostrativi Costruisci Architettura di riferimento Guide tecniche Guide ai prodotti e alle soluzioni Documentazione prodotti Documentazione Documentazione sviluppatori Esplora theNET Approfondimenti esecutivi per l'impresa digitale Cloudflare TV Serie ed eventi innovativi Cloudforce One Ricerca e operazioni sulle minacce Radar Tendenze del traffico e della sicurezza di Internet Report di analisi Report di ricerca di settore Eventi Prossimi eventi regionali Attendibilità, privacy e conformità Informazioni e criteri di conformità Supporto Contattaci Forum della community Hai perso l'accesso all'account? Sviluppatori Discord Ottieni assistenza Azienda informazioni aziendali Leadership Incontra i nostri leader Relazioni con gli investitori Informazioni per gli investitori Stampa Esplora le notizie recenti Opportunità di lavoro Esplora i ruoli aperti fiducia, privacy e sicurezza Privacy Criteri, dati e protezione Fiducia Criteri, processi e sicurezza Conformità Certificazione e regolamentazione Trasparenza Criteri e divulgazioni Interesse pubblico Umanitario Progetto Galileo Governo Progetto Athenian Elezioni Cloudflare For Campaigns Salute Project Fair Shot Una rete globale Posizioni e stato globali Accedi Contatta il reparto Vendite Segnati la data per Cloudflare Connect San Francisco 2026 19–22 ottobre 2026 Unisciti a migliaia di leader del settore per un'opportunità senza precedenti di promuovere l'innovazione e la collaborazione in occasione di Cloudflare Connect 2025. Ulteriori informazioni Tutti gli eventi programmati Nord e Sud America EMEA APJC Washington, DC GovCIO AI Summit • Jan 9 Coming soon San Diego, CA AFCEA West • Feb 10 - Feb 12 Coming soon Dallas, TX Immerse Dallas • Feb 12 Learn more Bogota, CO Immerse Bogota, Colombia • Feb 19 Coming soon New York, NY NASTD East-West • Mar 2 - Mar 5 Coming soon Washington, DC Billington State & Local • Mar 9 - Mar 11 Coming soon Mexico City, MX Immerse CDMX, Mexico • Mar 12 Coming soon San Jose, CA NVIDIA GTC • Mar 16 - Mar 17 Coming soon San Francisco, CA RSAC • Mar 23 - Mar 24 Coming soon Houston, TX Immerse Houston • Apr 2 Coming soon New York, NY Immerse New York • Apr 14 Coming soon São Paulo, BR Immerse Sao Paulo, Brazil • Apr 15 Coming soon Boston, MA Immerse Boston • Apr 16 Coming soon Montreal, CA Immerse Montreal • Apr 22 Coming soon Las Vegas, NV Google Cloud Next • Apr 22 - Apr 23 Coming soon Minneapolis, MN Immerse Minneapolis • Apr 23 Coming soon Philadelphia, PA NASCIO Midyear • Apr 28 - May 1 Coming soon Buenos Aires, AR Immerse Buenos Aires, Argentina • May Coming soon Kansas City, MO NLIT • May 4 - May 6 Coming soon Anaheim, CA Immerse Anaheim/SoCal • May 6 Coming soon Tampa, FL SOF Week • May 18 - May 21 Coming soon Toronto, CA Immerse Toronto • May 20 Coming soon Chicago, IL Immerse Chicago • May 28 Coming soon National Harbor, MD Gartner Security & Risk Management Summit (USA) • Jun 1 - Jun 2 Coming soon Baltimore, MD TechNet Cyber • Jun 2 - Jun 4 Coming soon Austin, TX NASTD Midwest-South • Jun 8 - Jun 11 Coming soon Vancouver, CA Immerse Vancouver • Jun 10 Coming soon Seattle, WA Immerse Seattle • Jun 18 Coming soon Las Vegas, NV Black Hat USA • Aug 3 - Aug 6 Coming soon Denver, CO NASTD Annual • Aug 23 - Aug 26 Coming soon Las Vegas, NV Crowdstrike fal.con • Aug 31 - Sept 1 Coming soon San Diego, CA NASCIO Annual • Sept 27 - Sept 30 Coming soon Denver, CO EDUCAUSE Annual • Sept 29 - Oct 2 Coming soon Santiago, CL Immerse Santiago, Chile • Oct Coming soon San Francisco, CA Cloudflare Global Connect 2026 • Oct 19 - Oct 20 Coming soon Orlando, FL Gartner IT Symposium • Oct 19 - Oct 20 Coming soon Atlanta, GA Immerse Atlanta • Nov 12 Coming soon Las Vegas, NV AWS re:Invent • Nov 30 - Dec 4 Coming soon INTRODUZIONE Piani gratuiti Piani per piccole imprese Per le aziende Ottieni un suggerimento Richiedi una demo Contatta il reparto Vendite SOLUZIONI Connettività cloud Servizi per le applicazioni SASE e sicurezza dell'ambiente di lavoro Servizi di rete Piattaforma per sviluppatori SUPPORTO Centro assistenza Assistenza clienti Forum della community Sviluppatori Discord Hai perso l'accesso all'account? Stato di Cloudflare CONFORMITÀ Risorse di conformità Fiducia GDPR IA responsabile Rapporto sulla trasparenza Segnala un abuso INTERESSE PUBBLICO Progetto Galileo Progetto Athenian Cloudflare per campagne Progetto Fair Shot AZIENDA Informazioni su Cloudflare Mappa di rete Il nostro team Loghi e cartella stampa Diversità, equità e inclusione Impact/ESG © 2026 Cloudflare, Inc. Informativa sulla privacy Condizioni per l’utilizzo Report Problemi di sicurezza Attendibilità e sicurezza Preferenze sull'uso dei cookie Marchio registrato | 2026-01-13T09:29:33 |
https://wordpress.com/ru/support/github-deployments/ | Как применять развёртывания GitHub на WordPress.com — Поддержка Товары Возможности Ресурсы Тарифные планы и цены Войти Начало работы Меню Хостинг WordPress WordPress для агентств Станьте аффилированным партнёром Доменные имена ИИ-конструктор сайтов Платформа для создания веб-сайтов Создайте блог Рассылка Professional Email Услуги по разработке веб-сайтов Commerce WordPress Studio WordPress для корпоративных клиентов Обзор Темы WordPress Плагины WordPress Паттерны WordPress Google Apps Центр поддержки Новости WordPress Генератор фирменных имён Инструмент создания логотипов Найдите новые записи Популярные метки Поиск по блогу Закрыть меню навигации Начало работы Регистрация Войти Детали Тарифные планы и цены Товары Хостинг WordPress WordPress для агентств Станьте аффилированным партнёром Доменные имена ИИ-конструктор сайтов Платформа для создания веб-сайтов Создайте блог Рассылка Professional Email Услуги по разработке веб-сайтов Commerce WordPress Studio WordPress для корпоративных клиентов Возможности Обзор Темы WordPress Плагины WordPress Паттерны WordPress Google Apps Ресурсы Центр поддержки Новости WordPress Генератор фирменных имён Инструмент создания логотипов Найдите новые записи Популярные метки Поиск по блогу Приложение Jetpack Подробнее Центр поддержки Руководства Курсы Форумы Связаться Поиск Центр поддержки / Руководства Центр поддержки Руководства Курсы Форумы Связаться Руководства / Управление учётной записью / Инструменты / Как применять развёртывания GitHub на WordPress.com Как применять развёртывания GitHub на WordPress.com GitHub Deployments интегрирует ваши репозитории GitHub непосредственно с вашим сайтом WordPress.com, что создаёт для вас автоматизированный рабочий процесс под управлением версии для развёртывания плагинов и тем или полного изменения сайта. В этом руководстве описаны процессы настройки и управления подключёнными репозиториями. Эта функция доступна на сайтах с тарифными планами WordPress.com Business или Commerce . Если вы приобрели тарифный план Business, не забудьте его активировать . Чтобы работать с этой функцией, необходимо повысить уровень тарифного плана , если у вас бесплатный сайт или вы пользуетесь тарифным планом Personal или Premium. В этом руководстве Обучающее видео Как подключить репозиторий Управление настройками развёртывания Расширенное развёртывание Как развернуть код Управление действующими подключениями Журналы запусков развёртываний Как отключить репозиторий Как отключить WordPress.com от GitHub Появились вопросы? Спросите помощника на базе ИИ Наверх Обучающее видео Это видео на английском языке. YouTube предлагает функции автоматического перевода, чтобы вы могли смотреть его на своём языке: Чтобы включить автоматически переведённые субтитры: Запустите видео. Нажмите значок ⚙️ Настройки (в правом нижнем углу видео). Выберите Субтитры/CC . Нажмите Автоматический перевод . Выберите нужный язык. Чтобы слушать автоматический дубляж (экспериментальная функция): Нажмите ⚙️ Настройки . Выберите Аудиодорожка . Выберите язык, на котором хотите слушать видео: ℹ️ Переводы и дубляж создаются автоматически с помощью Google, могут содержать неточности, а функция автоматического дубляжа всё ещё находится на стадии тестирования и доступна не для всех языков. Как подключить репозиторий Прежде чем развернуть репозиторий GitHub на сайте WordPress.com, необходимо настроить связь между ними, выполнив следующие действия: Перейдите на страницу «Сайты» по адресу https://wordpress.com/sites . Нажмите на название сайта, чтобы перейти к его обзору. Нажмите на вкладку Развёртывания . Нажмите кнопку « Подключить репозиторий ». Если далее появляется список репозиториев, то ваша учётная запись GitHub уже подключена. Перейдите к шагу 11. Нажмите кнопку « Установить приложение WordPress.com ». Откроется новое окно, и вам будет предложено войти в учётную запись GitHub, если вы этого ещё не сделали. Затем вы увидите следующий экран: Нажмите кнопку « Авторизовать WordPress.com для разработчиков ». Выберите организацию или учётную запись GitHub, где расположен ваш репозиторий. Выберите репозитории, к которым вы хотите подключиться: Все репозитории : при выборе этой опции WordPress.com получит доступ ко всем имеющимся и будущим репозиториям выбранной учётной записи GitHub. Это относится в том числе к открытым репозиториям в статусе «Только для чтения». Только указанные репозитории : при выборе этой опции вы сможете выбрать, к каким репозиториям данной учётной записи GitHub получит доступ WordPress.com. Выбрав опцию, нажмите кнопку Установить . Новое окно закроется, и вы вернётесь на WordPress.com. Выбранные репозитории должны отображаться рядом с учётной записью GitHub, связанной с ними. Нажмите Выбрать рядом с репозиторием, к которому требуется подключиться. На этом этапе WordPress.com для разработчиков будет отображаться под рубриками Авторизованные приложения GitHub и Установленные приложения GitHub . Управление настройками развёртывания После выбора репозитория нужно будет задать настройки развёртывания. Ветка развёртывания: по умолчанию — основная ветка репозитория (как правило, главная ), но можно указать другую желаемую ветку. Папка назначения : папка сервера, где требуется развернуть файлы. Для плагинов это будет /wp-content/plugins/my-plugin-name . Для тем это будет /wp-content/themes/my-theme-name . Для частичного развёртывания сайта (например, несколько плагинов или тем) можно использовать /wp-content . Контент репозитория будет объединён с имеющимся контентом сайта WordPress в указанной директории. Автоматические развёртывания . Есть два способа развёртывания на WordPress.com: Автоматически : после подтверждения код будет развёрнут на вашем сайте WordPress.com. Для предварительных версий сайтов рекомендуется автоматическое развёртывание. Вручную : код будет развёрнут после того, как вы направите запрос на развёртывание . Для рабочих сайтов рекомендуется развёртывание вручную. Режим развёртывания . Развёртывания бывают двух типов: Простой: этот режим копирует все файлы из ветки репозитория на сайт и развёртывает их без постобработки. Расширенный: в этом режиме можно использовать сценарий рабочего процесса, активировав индивидуальные этапы сборки, такие как установка зависимостей Composer, тестирование кода перед развёртыванием и управление развёртыванием файлов. Идеальный вариант для репозиториев, которым требуется ПО Composer или Node. Дополнительные сведения см. ниже в разделе «Расширенный режим развёртывания» . После настройки всех параметров нажмите кнопку Подключить . Ваш репозиторий будет добавлен. Обратите внимание, что первое развёртывание необходимо запускать автоматически или вручную .После этого в любой момент можно подключить другой репозиторий, нажав кнопку « Подключить репозиторий ». Расширенное развёртывание Расширенное развёртывание позволяет создать сценарий рабочего процесса для обработки файлов в репозитории перед развёртыванием. Это открывает множество возможностей, таких как проверка кода на соответствие вашим стандартам программирования, запуск модульных тестов, исключение файлов из развёртывания, установка зависимостей и многое другое. Вначале ознакомьтесь с примерами рабочих процессов . Чтобы настроить расширенное развёртывание, выполните следующие действия: Появится форма для настройки развёртывания. Нажмите на название репозитория, чтобы управлять подключением. Справа в разделе « Выберите режим развёртывания » нажмите Расширенный . Если репозиторий уже содержит файл рабочего процесса, здесь можно его выбрать. Система проверит файл на наличие ошибок. Если ошибок нет, переходите к шагу 7. Также можно выбрать опцию « Создать новый рабочий процесс », чтобы добавить предварительно настроенный файл рабочего процесса. При выборе этой опции файл рабочего процесса wpcom.yml , если он уже имеется в вашем репозитории, будет перезаписан. Нажмите кнопку « Установить мой рабочий процесс », чтобы разместить файл рабочего процесса в репозитории. После добавления и успешной проверки рабочего процесса нажмите кнопку Обновить . Теперь в вашем репозитории будет проводиться расширенное развёртывание. Как развернуть код Следующий этап после подключения репозитория GitHub к сайту — развёртывание вашего кода. Доступны два способа развёртывания: автоматическое и вручную . Не рекомендуется проводить автоматические развёртывания рабочих сайтов, так как любые изменения кода в репозитории автоматически развёртываются из GitHub на действующем сайте. Вместо этого лучше настроить автоматическое развёртывание предварительной версии сайта , а затем, когда всё будет готово, синхронизировать её с рабочим сайтом. Развёртывания вручную позволяют контролировать актуализацию изменений кода на рабочем сайте, так как вручную будет запускаться каждое отдельное развёртывание. Если вы не хотите использовать предварительную версию сайта, рекомендуем разворачивать сайт вручную. Чтобы запустить развёртывание вручную, выполните следующие действия: Перейдите на страницу «Сайты» по адресу https://wordpress.com/sites . Нажмите на название сайта, чтобы перейти к его обзору. Нажмите на вкладку Развёртывания . Нажмите на меню с тремя точками (⋮) в репозитории, который вы хотите развернуть. Выберите « Запустить развёртывание вручную ». Вы увидите баннер с уведомлением «Запуск развёртывания создан», а статус развёртывания изменится на «В очереди». Дождитесь завершения развёртывания (статус изменится на «Развёрнуто»). Снова нажмите меню с тремя точками (⋮) и выберите « Просмотреть запуски развёртываний ». В журнале запусков развёртываний указаны автор и развёрнутый коммит. Нажмите на запись о запуске развёртывания, чтобы просмотреть дополнительную информацию. Управление действующими подключениями Чтобы управлять действующими подключениями к репозиториям GitHub, сделайте следующее: Перейдите на страницу «Сайты» по адресу https://wordpress.com/sites . Нажмите на название сайта, чтобы перейти к его обзору. Нажмите на вкладку Развёртывания . Откроется список подключений. Список подключений отображается, если действует хотя бы одно подключение между репозиторием GitHub и вашим сайтом. В списке имеется информация о каждом подключении, в том числе: имя и ветка репозитория, последний развёрнутый на сайте коммит, дата развёртывания, место размещения кода, время и статус развёртывания. После нажатия на меню с тремя точками (⋮) становятся доступны дополнительные действия: Запустить развёртывание вручную: запускает развёртывание последнего коммита настроенной ветви. Просмотреть запуски развёртываний: открывает представление журнала запусков развёртываний подключённого репозитория. Настроить подключение: открывает представление управления подключениями репозитория. Отключить репозиторий: удаляет подключение между репозиторием и сайтом. Журналы запусков развёртываний Журналы запусков развёртываний содержат подробные пошаговые протоколы каждого развёртывания, запускаемого автоматически или вручную. Эти журналы помогают отслеживать изменения, следить за состоянием развёртывания и устранять любые возникающие неполадки. Вы можете просмотреть протоколы ближайших 10 запусков за последние 30 дней, изучить процесс в деталях и проверить, всё ли прошло как надо. Чтобы просмотреть журналы развёртываний, выполните следующие действия: Перейдите на страницу «Сайты» по адресу https://wordpress.com/sites . Нажмите на название сайта, чтобы перейти к его обзору. Нажмите на вкладку Развёртывания . Нажмите на меню с тремя точками (⋮) рядом с репозиторием, журналы которого вы хотите просмотреть. Выберите « Просмотреть запуски развёртываний ». В представлении списка запусков развёртывания отображаются развёрнутые на сайте коммиты, статус развёртывания, дата и продолжительность. Нажмите на нужный запуск в любой точке, чтобы раскрыть протокол и просмотреть подробные сведения о развёртывании. Журналы содержат записи обо всех выполняемых командах, от получения кода из GitHub до размещения его в целевой директории. Можно раскрывать строки журнала, чтобы просматривать дополнительную информацию, нажимая на ссылку « Показать ещё ». Как отключить репозиторий Если вы отключите репозиторий GitHub от своего сайта, после этого никакие изменения в репозитории больше не отразятся на сайте. По умолчанию развёрнутые файлы остаются на вашем сайте, но вы можете удалить их в ходе отключения. Чтобы отключить репозиторий, выполните следующие действия: Перейдите на страницу «Сайты» по адресу https://wordpress.com/sites . Нажмите на название сайта, чтобы перейти к его обзору. Нажмите на вкладку Развёртывания . Нажмите на меню с тремя точками (⋮) в репозитории. Выберите « Отключить репозиторий ». Появится диалоговое окно. Нажмите переключатель, чтобы удалить с сайта связанные файлы. Нажмите « Отключить репозиторий », чтобы закрыть диалоговое окно и отключить репозиторий. Обратите внимание, что WordPress.com для разработчиков останется в списках ваших установленных приложений GitHub и авторизованных приложений GitHub . Дело в том, что WordPress.com не лишается доступа к репозиторию несмотря на то, что подключение удалено. Как отключить WordPress.com от GitHub Вы можете отозвать доступ WordPress.com к вашей учётной записи GitHub. Это можно сделать в любой момент, открыв настройки приложений на GitHub. Чтобы отозвать авторизованный доступ приложения к вашей учётной записи GitHub, выполните следующие действия: Откройте Авторизованные приложения GitHub . Нажмите кнопку Отозвать рядом с приложением WordPress.com для разработчиков . Нажмите кнопку « Я понимаю, отозвать доступ ». Даже если вы отзовёте доступ к авторизованному приложению, код всё равно может быть развёрнут, так как приложение WordPress.com для разработчиков остаётся установленным в выбранных учётных записях. Чтобы отозвать доступ к установке WordPress.com и отключить развёртывание кода на сайте WordPress.com, выполните следующие действия: Откройте Установленные приложения GitHub . Нажмите Настроить рядом с WordPress.com для разработчиков . В области Опасная зона нажмите Удалить , а затем нажмите ОК . Удаление WordPress.com из списка авторизованных приложений не означает, что репозитории будут удалены или перестанут работать; ваши репозитории останутся на GitHub после того, как вы отзовёте доступ WordPress.com, но WordPress.com больше не сможет разворачивать код. Ваша оценка: Похожие руководства Резервное копирование и восстановление сайта Время чтения: 1 мин Приложения для WordPress.com Время чтения: 1 мин Подключение к SSH Время чтения: 1 мин Панель действий Время чтения: 1 мин В этом руководстве Обучающее видео Как подключить репозиторий Управление настройками развёртывания Расширенное развёртывание Как развернуть код Управление действующими подключениями Журналы запусков развёртываний Как отключить репозиторий Как отключить WordPress.com от GitHub Появились вопросы? Спросите помощника на базе ИИ Наверх Не можете найти то, что вам нужно? Свяжитесь с нами Получайте ответы от нашего помощника на базе ИИ и пользуйтесь круглосуточной экспертной поддержкой в платных тарифных планах. Задайте вопрос на нашем форуме Просматривайте вопросы и получайте ответы от других опытных пользователей. Copied to clipboard! WordPress.com Товары Хостинг WordPress WordPress для агентств Станьте аффилированным партнёром Доменные имена ИИ-конструктор сайтов Платформа для создания веб-сайтов Создайте блог Professional Email Услуги по разработке веб-сайтов WordPress Studio WordPress для корпоративных клиентов Возможности Обзор Темы WordPress Плагины WordPress Паттерны WordPress Google Apps Ресурсы Блог WordPress.com Генератор фирменных имён Инструмент создания логотипов WordPress.com Reader Доступность Удалить подписки Помощь Центр поддержки Руководства Курсы Форумы Связаться Разработчикам Компания Детали Пресса Условия использования Конфиденциальность Отказ от продажи персональных данных и их передачи третьим лицам Заявление о защите конфиденциальности для пользователей из Калифорнии Deutsch Español Français Bahasa Indonesia Italiano Nederlands Português do Brasil Svenska Türkçe Русский العربية עִבְרִית 日本語 한국어 简体中文 繁體中文 English Deutsch Español Français Bahasa Indonesia Italiano Nederlands Português do Brasil Svenska Türkçe Русский العربية עִבְרִית 日本語 한국어 简体中文 繁體中文 English Мобильные приложения Загрузить из App Store Скачать с Google Play Социальные сети WordPress.com в Facebook WordPress.com в Х (ранее Twitter) WordPress.com в Instagram WordPress.com на YouTube Automattic Automattic Вакансии Загружаются Комментарии... Опубликовать комментарий... E-mail (обязательно) Имя (обязательно) Сайт Поддержка Регистрация Войти Копировать ссылку Сообщить об этом содержимом Управление подписками | 2026-01-13T09:29:33 |
https://chromewebstore.google.com/detail/category/top-charts/detail/askbelynda-sustainable-sh/category/extensions/productivity/detail/bettercampus-prev-betterc/cndibmoanboadcifjkjbdpjgfedanolh | Chrome Web Store Skip to main content Chrome Web Store My extensions & themes Developer Dashboard Give feedback Sign in Discover Extensions Themes Welcome to Chrome Web Store Welcome to the Chrome Web Store Supercharge your browser with extensions and themes for Chrome See collection Favorites of 2025 Discover the standout AI extensions that made our year See collection Every day is Earth Day Plant trees, shop sustainably, and more See collection Adobe Photoshop Easily remove backgrounds, adjust colors and more. Plus, get 6 months free access to Photoshop web. 3.7 600K Users See details The future of writing Elevate your writing and create engaging and high-quality content effortlessly See collection 1 / 5 Top categories Shopping Entertainment Tools Art & Design Accessibility Top charts Trending Kami for Google Chrome™ Education 4.6 Average rating 4.6 out of 5 stars. Learn more about results and reviews. BetterCampus (prev. BetterCanvas) Education 4.9 Average rating 4.9 out of 5 stars. Learn more about results and reviews. Read&Write for Google Chrome™ Accessibility 3.4 Average rating 3.4 out of 5 stars. Learn more about results and reviews. See more Popular Volume Master Accessibility 4.8 Average rating 4.8 out of 5 stars. Learn more about results and reviews. Free VPN for Chrome - VPN Proxy VeePN Workflow & Planning 4.5 Average rating 4.5 out of 5 stars. Learn more about results and reviews. AdBlock — block ads across the web Workflow & Planning 4.5 Average rating 4.5 out of 5 stars. Learn more about results and reviews. See more New and notable Ad Block Wonder Privacy & Security 4.3 Average rating 4.3 out of 5 stars. Learn more about results and reviews. Smart popup blocker Tools 4.6 Average rating 4.6 out of 5 stars. Learn more about results and reviews. Manus AI Browser Operator Tools 4.5 Average rating 4.5 out of 5 stars. Learn more about results and reviews. See more Editors' Picks for you Handpicked by Chrome Editors See collection Extend your browser See more Discover a new level of convenience and customization with side panel extensions Chat with all AI models (Gemini, Claude, DeepSeek…) & AI Agents | AITOPIA 4.9 Average rating 4.9 out of 5 stars. Learn more about results and reviews. AI Agent Marketplace & AI Sidebar with all AI models (Gemini, Claude, DeepSeek & more) and hundreds of AI Agents Adobe Photoshop 3.7 Average rating 3.7 out of 5 stars. Learn more about results and reviews. Easily remove backgrounds, adjust colors and more. Plus, get 6 months free access to Photoshop web. BrowserGPT: ChatGPT Anywhere Powered by GPT 4 4.4 Average rating 4.4 out of 5 stars. Learn more about results and reviews. Write, reword, and translate 8x faster. Reply to emails in a click. Works on Google Docs, Gmail, YouTube, Twitter, Instagram, etc. Sidebar: ChatGPT, Bookmarks, GPT-4o | Meomni 4.8 Average rating 4.8 out of 5 stars. Learn more about results and reviews. Ultimate Sidebar ChatGPT Assistant, Bookmarks with AI, Calendar and Tasks Fleeting Notes 4.6 Average rating 4.6 out of 5 stars. Learn more about results and reviews. Quick notes from the browser to Obsidian Eclipse your screen Dim the lights with our dark mode selections See collection Chrome monthly spotlight Promising extensions to try out Web Highlights: PDF & Web Highlighter + Notes & AI Summary Productivity Highlighter & Annotation Tool for Websites & PDFs with AI Summary - free, easy to use, no sign-up required. Moonlight: AI Colleague for Research Papers Everything you need to read a paper: explanation, summary, translation, chat, and reference search. Reboost - Track Water Intake and Set Reminders Track your water intake and set custom reminders. Stay hydrated, stay on track, and never miss a break! ✨ YouTube Notes to Notion with Udemy, Coursera, BiliBili and more by Snipo Take YouTube notes directly to Notion, generate AI flashcards, capture screenshots, and sync learning courses with Notion Works with Gmail See more Boost your email productivity Boomerang for Gmail 4.2 Average rating 4.2 out of 5 stars. Learn more about results and reviews. Meeting scheduling and email management tool trusted by millions. Schedule meetings, track responses, send later, and more. Checker Plus for Gmail™ 4.7 Average rating 4.7 out of 5 stars. Learn more about results and reviews. Get notifications, read, listen to or delete emails without opening Gmail and easily manage multiple accounts. Email Tracker by Mailtrack® 4.4 Average rating 4.4 out of 5 stars. Learn more about results and reviews. Free, unlimited email tracker for Gmail, trusted by millions. Accurate, reliable, GDPR-compliant, and Google-audited. Streak CRM for Gmail 4.5 Average rating 4.5 out of 5 stars. Learn more about results and reviews. Manage sales and customer relationships directly inside Gmail. GMass: Powerful mail merge for Gmail 4.8 Average rating 4.8 out of 5 stars. Learn more about results and reviews. A powerful mass email and mail merge system for Gmail. Just for fun Bring some joy to your browser See collection Learn a new language See more Study while you browse Google Translate 4.2 Average rating 4.2 out of 5 stars. Learn more about results and reviews. View translations easily as you browse the web. By the Google Translate team. Rememberry - Translate and Memorize with Flashcards 4.6 Average rating 4.6 out of 5 stars. Learn more about results and reviews. Translate words while browsing and turn them into spaced repetition flashcards to build foreign language vocabulary. DeepL: translate and write with AI 4.7 Average rating 4.7 out of 5 stars. Learn more about results and reviews. Translate while you read and write with DeepL Translate, the world’s most accurate translator. Relingo - Master vocabulary while browsing websites and watching YouTube 4.6 Average rating 4.6 out of 5 stars. Learn more about results and reviews. Relingo extract words, full-text immersive translation while browsing. Also supports bilingual subtitles for Youtube, Netflix, etc. Readlang Web Reader 4.3 Average rating 4.3 out of 5 stars. Learn more about results and reviews. Read websites in the language you're learning, translate words you don't know, and we'll create flashcards to help you remember. Game on See more Beat boredom with bite-sized games in your browser BattleTabs 4.7 Average rating 4.7 out of 5 stars. Learn more about results and reviews. Multiplayer Battles in your New Tab Tiny Tycoon 4.7 Average rating 4.7 out of 5 stars. Learn more about results and reviews. Build a tiny tycoon on a tiny planet. Boxel 3D 4.6 Average rating 4.6 out of 5 stars. Learn more about results and reviews. Boxel 3D is a speedrunning game packed with challenging levels, custom skins, online multiplayer, and a creative level editor. Ice Dodo 4.6 Average rating 4.6 out of 5 stars. Learn more about results and reviews. Play 3D game easily by clicking the little icon at the top right corner of your browser. Boxel Golf 4.7 Average rating 4.7 out of 5 stars. Learn more about results and reviews. Boxel Golf is a multiplayer golf game packed with challenging courses, custom hats, and a powerful level builder. Work smarter, not harder with AI Automate tasks and stay focused and organized with AI-powered productivity extensions See collection For music lovers See more Equalizers, radios, playlists, and more Volume Master 4.8 Average rating 4.8 out of 5 stars. Learn more about results and reviews. Up to 600% volume boost Music Mode for YouTube™ 4.5 Average rating 4.5 out of 5 stars. Learn more about results and reviews. Hides the video and thumbnails on YouTube. Blocks the video keeping only the audio on YouTube Music. Smart Mute 4.5 Average rating 4.5 out of 5 stars. Learn more about results and reviews. Listen to audio one tab at a time. Modest Guitar | Columns for Ultimate-Guitar 4.8 Average rating 4.8 out of 5 stars. Learn more about results and reviews. Multiple columns and fullscreen for Ultimate-Guitar tabs Chrome Piano 4.5 Average rating 4.5 out of 5 stars. Learn more about results and reviews. Play the piano in your browser Google apps About Chrome Web Store Developer Dashboard Privacy Policy Terms of Service Help | 2026-01-13T09:29:33 |
https://chromewebstore.google.com/detail/category/detail/volume-master/top-charts/detail/volume-master/collection/get_started | Chrome Web Store Skip to main content Chrome Web Store My extensions & themes Developer Dashboard Give feedback Sign in Discover Extensions Themes Welcome to Chrome Web Store Welcome to the Chrome Web Store Supercharge your browser with extensions and themes for Chrome See collection Favorites of 2025 Discover the standout AI extensions that made our year See collection Every day is Earth Day Plant trees, shop sustainably, and more See collection Adobe Photoshop Easily remove backgrounds, adjust colors and more. Plus, get 6 months free access to Photoshop web. 3.7 600K Users See details The future of writing Elevate your writing and create engaging and high-quality content effortlessly See collection 1 / 5 Top categories Shopping Entertainment Tools Art & Design Accessibility Top charts Trending Kami for Google Chrome™ Education 4.6 Average rating 4.6 out of 5 stars. Learn more about results and reviews. BetterCampus (prev. BetterCanvas) Education 4.9 Average rating 4.9 out of 5 stars. Learn more about results and reviews. Read&Write for Google Chrome™ Accessibility 3.4 Average rating 3.4 out of 5 stars. Learn more about results and reviews. See more Popular Volume Master Accessibility 4.8 Average rating 4.8 out of 5 stars. Learn more about results and reviews. Free VPN for Chrome - VPN Proxy VeePN Workflow & Planning 4.5 Average rating 4.5 out of 5 stars. Learn more about results and reviews. AdBlock — block ads across the web Workflow & Planning 4.5 Average rating 4.5 out of 5 stars. Learn more about results and reviews. See more New and notable Ad Block Wonder Privacy & Security 4.3 Average rating 4.3 out of 5 stars. Learn more about results and reviews. Smart popup blocker Tools 4.6 Average rating 4.6 out of 5 stars. Learn more about results and reviews. Manus AI Browser Operator Tools 4.5 Average rating 4.5 out of 5 stars. Learn more about results and reviews. See more Editors' Picks for you Handpicked by Chrome Editors See collection Extend your browser See more Discover a new level of convenience and customization with side panel extensions Chat with all AI models (Gemini, Claude, DeepSeek…) & AI Agents | AITOPIA 4.9 Average rating 4.9 out of 5 stars. Learn more about results and reviews. AI Agent Marketplace & AI Sidebar with all AI models (Gemini, Claude, DeepSeek & more) and hundreds of AI Agents Adobe Photoshop 3.7 Average rating 3.7 out of 5 stars. Learn more about results and reviews. Easily remove backgrounds, adjust colors and more. Plus, get 6 months free access to Photoshop web. BrowserGPT: ChatGPT Anywhere Powered by GPT 4 4.4 Average rating 4.4 out of 5 stars. Learn more about results and reviews. Write, reword, and translate 8x faster. Reply to emails in a click. Works on Google Docs, Gmail, YouTube, Twitter, Instagram, etc. Sidebar: ChatGPT, Bookmarks, GPT-4o | Meomni 4.8 Average rating 4.8 out of 5 stars. Learn more about results and reviews. Ultimate Sidebar ChatGPT Assistant, Bookmarks with AI, Calendar and Tasks Fleeting Notes 4.6 Average rating 4.6 out of 5 stars. Learn more about results and reviews. Quick notes from the browser to Obsidian Eclipse your screen Dim the lights with our dark mode selections See collection Chrome monthly spotlight Promising extensions to try out Web Highlights: PDF & Web Highlighter + Notes & AI Summary Productivity Highlighter & Annotation Tool for Websites & PDFs with AI Summary - free, easy to use, no sign-up required. Moonlight: AI Colleague for Research Papers Everything you need to read a paper: explanation, summary, translation, chat, and reference search. Reboost - Track Water Intake and Set Reminders Track your water intake and set custom reminders. Stay hydrated, stay on track, and never miss a break! ✨ YouTube Notes to Notion with Udemy, Coursera, BiliBili and more by Snipo Take YouTube notes directly to Notion, generate AI flashcards, capture screenshots, and sync learning courses with Notion Works with Gmail See more Boost your email productivity Boomerang for Gmail 4.2 Average rating 4.2 out of 5 stars. Learn more about results and reviews. Meeting scheduling and email management tool trusted by millions. Schedule meetings, track responses, send later, and more. Checker Plus for Gmail™ 4.7 Average rating 4.7 out of 5 stars. Learn more about results and reviews. Get notifications, read, listen to or delete emails without opening Gmail and easily manage multiple accounts. Email Tracker by Mailtrack® 4.4 Average rating 4.4 out of 5 stars. Learn more about results and reviews. Free, unlimited email tracker for Gmail, trusted by millions. Accurate, reliable, GDPR-compliant, and Google-audited. Streak CRM for Gmail 4.5 Average rating 4.5 out of 5 stars. Learn more about results and reviews. Manage sales and customer relationships directly inside Gmail. GMass: Powerful mail merge for Gmail 4.8 Average rating 4.8 out of 5 stars. Learn more about results and reviews. A powerful mass email and mail merge system for Gmail. Just for fun Bring some joy to your browser See collection Learn a new language See more Study while you browse Google Translate 4.2 Average rating 4.2 out of 5 stars. Learn more about results and reviews. View translations easily as you browse the web. By the Google Translate team. Rememberry - Translate and Memorize with Flashcards 4.6 Average rating 4.6 out of 5 stars. Learn more about results and reviews. Translate words while browsing and turn them into spaced repetition flashcards to build foreign language vocabulary. DeepL: translate and write with AI 4.7 Average rating 4.7 out of 5 stars. Learn more about results and reviews. Translate while you read and write with DeepL Translate, the world’s most accurate translator. Relingo - Master vocabulary while browsing websites and watching YouTube 4.6 Average rating 4.6 out of 5 stars. Learn more about results and reviews. Relingo extract words, full-text immersive translation while browsing. Also supports bilingual subtitles for Youtube, Netflix, etc. Readlang Web Reader 4.3 Average rating 4.3 out of 5 stars. Learn more about results and reviews. Read websites in the language you're learning, translate words you don't know, and we'll create flashcards to help you remember. Game on See more Beat boredom with bite-sized games in your browser BattleTabs 4.7 Average rating 4.7 out of 5 stars. Learn more about results and reviews. Multiplayer Battles in your New Tab Tiny Tycoon 4.7 Average rating 4.7 out of 5 stars. Learn more about results and reviews. Build a tiny tycoon on a tiny planet. Boxel 3D 4.6 Average rating 4.6 out of 5 stars. Learn more about results and reviews. Boxel 3D is a speedrunning game packed with challenging levels, custom skins, online multiplayer, and a creative level editor. Ice Dodo 4.6 Average rating 4.6 out of 5 stars. Learn more about results and reviews. Play 3D game easily by clicking the little icon at the top right corner of your browser. Boxel Golf 4.7 Average rating 4.7 out of 5 stars. Learn more about results and reviews. Boxel Golf is a multiplayer golf game packed with challenging courses, custom hats, and a powerful level builder. Work smarter, not harder with AI Automate tasks and stay focused and organized with AI-powered productivity extensions See collection For music lovers See more Equalizers, radios, playlists, and more Volume Master 4.8 Average rating 4.8 out of 5 stars. Learn more about results and reviews. Up to 600% volume boost Music Mode for YouTube™ 4.5 Average rating 4.5 out of 5 stars. Learn more about results and reviews. Hides the video and thumbnails on YouTube. Blocks the video keeping only the audio on YouTube Music. Smart Mute 4.5 Average rating 4.5 out of 5 stars. Learn more about results and reviews. Listen to audio one tab at a time. Modest Guitar | Columns for Ultimate-Guitar 4.8 Average rating 4.8 out of 5 stars. Learn more about results and reviews. Multiple columns and fullscreen for Ultimate-Guitar tabs Chrome Piano 4.5 Average rating 4.5 out of 5 stars. Learn more about results and reviews. Play the piano in your browser Google apps About Chrome Web Store Developer Dashboard Privacy Policy Terms of Service Help | 2026-01-13T09:29:33 |
https://cn.chinadaily.com.cn/a/202511/17/WS691aef29a310942cc4991e3f.html | 【世界说】美国消费者信心指数跌至三年来新低 经济压力凸显政策与民生脱节 - 中国日报网 【世界说】美国消费者信心指数跌至三年来新低 经济压力凸显政策与民生脱节 最新公布的密歇根大学消费者信心指数初值显示，11月美国消费者信心指数由10月的53.6降至50.3，不仅低于预期，更创下三年来的新低。这反映出，目前美国经济正面临物价持续上涨、企业成本传导压力加大、政府政策与民众实际感受脱节等多重挑战。 站内搜索 搜狗搜索 中国搜索 --> 订阅 移动 English 首页 时政 时政要闻 评论频道 理论频道 学习时代 两岸频道 资讯 独家 中国日报专稿 传媒动态 每日一词 法院公告 C财经 证券 独家 科技 产业 视频 专栏 双语 双语财讯 每日一词 双语新闻 新闻热词 译词课堂 --> 漫画 观天下 中国观察 中国日报网评 中国那些事儿 海外手记 侨一瞧 地方 文创 文旅 生活 中国有约 China Daily Homepage 中文网首页 时评 资讯 C财经 生活 视频 专栏 双语 --> 漫画 原创 观天下 地方频道 --> 关闭 中国日报网 > 世界说 > 【世界说】美国消费者信心指数跌至三年来新低 经济压力凸显政策与民生脱节 来源：中国日报网 2025-11-17 17:47 --> 分享到微信 中国日报网11月17日电 综合外媒报道，最新公布的密歇根大学消费者信心指数初值显示，11月美国消费者信心指数由10月的53.6降至50.3，不仅低于预期，更创下三年来的新低。这反映出，目前美国经济正面临物价持续上涨、企业成本传导压力加大、政府政策与民众实际感受脱节等多重挑战。 专家：信心下滑在于美民生压力持续加重 美国“共同梦想”网站日前报道指出，尽管特朗普政府曾承诺在上任首日即着手降低民众生活成本，但十个月过去，政府却表示民生负担危机可能要到2026年才会真正显现。与此同时，美国失业人数已突破百万，信用卡债务持续攀升，加剧了家庭财务压力。 报道截图 “基层合作组织”（Groundwork Collaborative）政策与倡导部门主管亚历克斯·雅克兹指出，美民众对经济的信心下滑源于实际生活压力的加重。他认为，当前政府在经济管理上未能有效改善民生，反而导致家庭债务创下新高，物价不断上涨，信心指数自然跌至低谷。 质疑民调忧虑，但物价上涨实难掩盖 福布斯新闻网站报道称，本月早些时候的调查显示，超过四分之三的美国人对个人财务状况感到忧虑，而政府却质疑民调的真实性，称其为“虚假信息”。然而，多数民众正经历的是物价上涨带来的支出增加。尽管特朗普政府宣称“生活成本已大幅下降”，但电费、家具、电子产品及食品杂货等价格自其就职以来便普遍上涨。 报道截图 《纽约邮报》日前也指出，尽管特朗普政府宣称已控制通胀，但消费者仍承受明显经济压力。美国消费者新闻与商业频道（CNBC）此前数据显示，今年1月至9月，亚马逊、塔吉特和沃尔玛服装价格平均上涨11.5%，大型连锁店家居用品、宠物用品及消耗品、健康美容产品以及耐用消费品价格分别上涨10.8%、6.1%、7%和8.3%。 多因素推高物价：民生消费受显著冲击 物价上涨受多重因素叠加影响，其中特朗普政府对多国加征关税的政策尤为关键，咖啡、家具、儿童玩具等多款商品价格受其影响普遍走高。 具体来看，尽管9月美国食品通胀率回落至3.1%，但肉类等部分食品价格依然高企。香蕉因关税影响价格上涨8.6%，牛肉价格则受干旱天气和进口关税双重作用，涨幅较为明显，政府正考虑增加阿根廷牛肉进口以缓解压力。 家具行业所受影响更为显著，10月美国政府宣布将部分家具关税提高至30%后，宜家等品牌多款产品随即上调价格，联邦数据显示，客厅及厨房家具价格同比上涨近10%。咖啡价格受气候异常和关税双重影响，同比大涨41%，南加州家族企业“克拉奇咖啡”已因成本上升两次上调价格。 物价上涨直接冲击民生消费。61岁的纽约皇后区居民克里斯·索汉，作为两次支持特朗普政府的选民，如今采购同样商品需花费更多资金，不得不减少购买频率、调整消费结构，他对当前政策效果感到失望。这一案例不仅反映出部分美国民众对政府政策的质疑与不满，更凸显出政策实施效果与民众期望之间的明显差距。 （编译：马芮 编辑：高琳琳 韩鹤） 【责任编辑：马芮】 COMPO WS691aef29a310942cc4991e3f https://cn.chinadaily.com.cn/a/202511/17/WS691aef29a310942cc4991e3f.html 世界说 【世界说】菲分析人士：高市早苗“生存威胁”论存多重逻辑谬误 尊重历史方为正途 【世界说】杰弗里·萨克斯：中国是合作伙伴而非威胁 美国遏制战略是损害自身的“回旋镖” 聚焦2025APEC丨一个视频带你了解含金量如此之高的APEC 【世界说】美国贸易政策又把养牛业者惹怒了：做法昧良心，感觉遭“背刺”！ 【世界说】美国GDP的虚拟泡沫：繁荣背后的经济“虚胖”幻象 【世界说】枪支令美国社会充斥消极氛围：对安全焦虑、对枪暴麻木 【世界说】两党互责，苦了民众伤了机构……美联邦政府停摆僵局持续 【世界说】美媒：关税非解决美国制造业痼疾良方，不如专注提高自身生产率 推荐阅读 飞龙在天，文心不惑——纪念古龙逝世四十周年系列活动在杭启幕 每日一词 | 农作物自主选育品种 self-bred crop varieties 每日一词 | 全国温室气体自愿减排交易市场 今年4月至10月 日本遭熊袭击人数创近年同期新高 越南一公路山体滑坡致大巴被掩埋 造成6死19伤 美联邦航空管理局宣布终止航班削减紧急令 安理会将表决加沙问题草案 美以在关键问题上有分歧 【世界说】菲分析人士：高市早苗“生存威胁”论存多重逻辑谬误 尊重历史方为正途 为你推荐 神奇的中国 海外手记 和评理 中国那些事儿 世界说 中国观察 新华社 中国日报网评 侨一瞧 事事关心 每日一词 中国经济网 中国新闻网 环球时报 中央电视台 中央人民广播电台 解放军报 中国新闻周刊 人民日报海外版 中国青年网 经济日报 光明日报 中国军网 求是 中国侨网 消费日报网 中国警察网 参考消息网 中国搜索 海外网 法制网 环球网 中青在线 中工网 中国西藏网 中国台湾网 央广网 光明网 人民网 国际在线 中国网 未来网 每日一词 一财网 新华网 为你推荐 神奇的中国 海外手记 和评理 中国那些事儿 世界说 中国观察 新华社 中国日报网评 侨一瞧 事事关心 每日一词 中国经济网 中国新闻网 环球时报 中央电视台 中央人民广播电台 解放军报 中国新闻周刊 人民日报海外版 中国青年网 经济日报 光明日报 中国军网 求是 中国侨网 消费日报网 中国警察网 参考消息网 中国搜索 海外网 法制网 环球网 中青在线 中工网 中国西藏网 中国台湾网 央广网 光明网 人民网 国际在线 中国网 未来网 每日一词 一财网 新华网 推荐阅读 飞龙在天，文心不惑——纪念古龙逝世四十周年系列活动在杭启幕 每日一词 | 农作物自主选育品种 self-bred crop varieties 每日一词 | 全国温室气体自愿减排交易市场 今年4月至10月 日本遭熊袭击人数创近年同期新高 越南一公路山体滑坡致大巴被掩埋 造成6死19伤 美联邦航空管理局宣布终止航班削减紧急令 安理会将表决加沙问题草案 美以在关键问题上有分歧 【世界说】菲分析人士：高市早苗“生存威胁”论存多重逻辑谬误 尊重历史方为正途 关于我们 | 联系我们 首页 时评 资讯 财经 生活 视频 专栏 漫画 独家 招聘 地方频道： 北京 天津 河北 山西 辽宁 吉林 黑龙江 上海 江苏 浙江 福建 江西 山东 河南 湖北 湖南 广东 广西 海南 重庆 四川 贵州 云南 西藏 陕西 新疆 深圳 友情链接： 人民网 新华网 中国网 国际在线 央视网 中国青年网 中国经济网 中国台湾网 中国西藏网 央广网 光明网 中国军网 中国新闻网 人民政协网 法治网 违法和不良信息举报 互联网新闻信息服务许可证10120170006 信息网络传播视听节目许可证0108263号 京公网安备11010502032503号 京网文[2011]0283-097号 京ICP备13028878号-6 中国日报网版权说明：凡注明来源为“中国日报网：XXX（署名）”，除与中国日报网签署内容授权协议的网站外，其他任何网站或单位未经允许禁止转载、使用，违者必究。如需使用，请与010-84883777联系；凡本网注明“来源：XXX（非中国日报网）”的作品，均转载自其它媒体，目的在于传播更多信息，其他媒体如需转载，请与稿件来源方联系，如产生任何问题与本网无关。 版权保护：本网登载的内容（包括文字、图片、多媒体资讯等）版权属中国日报网（中报国际文化传媒（北京）有限公司）独家所有使用。 未经中国日报网事先协议授权，禁止转载使用。给中国日报网提意见：rx@chinadaily.com.cn C财经客户端 扫码下载 Chinadaily-cn 中文网微信 首页 时评 资讯 C财经 生活 视频 专栏 地方 漫画 观天下 PC版 中文 English 中国日报版权所有 Content@chinadaily.com.cn × | 2026-01-13T09:29:33 |
https://gitstar-ranking.com/airbnb | airbnb - Gitstar Ranking Gitstar Ranking Users Organizations Repositories Rankings Users Organizations Repositories Sign in with GitHub airbnb Star 389148 Rank 17 Go to GitHub Fetched on 2026/01/09 04:12 198 Repositories javascript 148007 lottie-android 35551 lottie-web 31641 lottie-ios 26610 visx 20521 react-sketchapp 14905 epoxy 8562 css 7001 mavericks 5937 hypernova 5815 ts-migrate 5601 knowledge-repo 5538 lottie 4851 aerosolve 4801 DeepLinkDispatch 4409 ruby 3892 polyglot.js 3728 MagazineLayout 3354 native-navigation 3126 HorizonCalendar 3088 streamalert 2888 infinity 2788 airpal 2752 swift 2671 Showkase 2276 synapse 2068 paris 1912 AirMapView 1882 react-with-styles 1699 rheostat 1693 binaryalert 1443 epoxy-ios 1309 chronon 956 nerve 942 okreplay 786 RxGroups 690 react-outside-click-handler 615 ResilientDecoding 602 babel-plugin-dynamic-import-node 574 kafkat 502 babel-plugin-dynamic-import-webpack 496 babel-plugin-inline-react-svg 474 lunar 470 BuckSample 467 SpinalTap 450 artificial-adversary 401 dynein 387 hammerspace 371 node-memwatch 315 trebuchet 312 1 2 3 4 › Released by @k0kubun in December 2014. Fork me on GitHub . | 2026-01-13T09:29:33 |
https://wordpress.com/es/support/despliegues-de-github/ | Utilizar despliegues de GitHub en WordPress.com – Servicio de soporte WordPress.com Productos Funcionalidades Recursos Planes y precios Iniciar sesión Comenzar Menú Hosting WordPress WordPress para Agencias Hazte afiliado Dominios Creador de webs con IA Creador de webs Crea un blog Newsletter Correo electrónico profesional Servicio de diseño web Commerce WordPress Studio WordPress Enterprise Resumen Temas de WordPress Plugins de WordPress Patrones de WordPress Google Apps Centro de soporte Blog de WordPress.com Generador de nombres de empresa Creador de logos Descubrir nuevas publicaciones Etiquetas populares Buscar blog Cerrar el menú de navegación Comenzar Regístrate Iniciar sesión Acerca de Planes y precios Productos Hosting WordPress WordPress para Agencias Hazte afiliado Dominios Creador de webs con IA Creador de webs Crea un blog Newsletter Correo electrónico profesional Servicio de diseño web Commerce WordPress Studio WordPress Enterprise Funcionalidades Resumen Temas de WordPress Plugins de WordPress Patrones de WordPress Google Apps Recursos Centro de soporte Blog de WordPress.com Generador de nombres de empresa Creador de logos Descubrir nuevas publicaciones Etiquetas populares Buscar blog Aplicación de Jetpack Más información Centro de soporte Guías Cursos Foros Contacto Buscar Centro de soporte / Guías Centro de soporte Guías Cursos Foros Contacto Guías / Plugins y herramientas / Utilizar despliegues de GitHub en WordPress.com Utilizar despliegues de GitHub en WordPress.com GitHub Deployments integra tus repositorios de GitHub directamente con tu sitio de WordPress.com, ofreciéndote un flujo de trabajo automatizado y controlado por versiones para desplegar plugins, temas o cambios completos en el sitio. Esta guía cubre el proceso de configuración y cómo gestionar tus repositorios conectados. Esta función está disponible en sitios con los planes Business y Commerce de WordPress.com. Si tienes un plan Business, asegúrate de activarlo . Para los sitios con los planes gratuito, Personal y Premium, mejora tu plan para acceder a esta función. En esta guía Tutorial en vídeo Conectar un directorio Gestionar ajustes de despliegue Despliegue avanzado Despliega tu código Gestionar las conexiones existentes Registros de ejecución de despliegue Desconectar un repositorio Desconectar de WordPress.com de GitHub ¿Tienes alguna pregunta? Pregunta a nuestro AI Assistant Volver arriba Tutorial en vídeo Este vídeo está en inglés. YouTube ofrece funciones de traducción automática para que puedas verlo en tu idioma: Para subtítulos automáticos: Reproduce el vídeo. Haz clic en ⚙️ Ajustes (abajo a la derecha). Elige Subtítulos/CC → Traducción automática . Selecciona tu idioma. Para audio doblado automáticamente (experimental): Haz clic en ⚙️ Ajustes . Selecciona Pista de audio . Selecciona el idioma en el que quieras escuchar el vídeo. ℹ️ Las traducciones y doblajes son generados por Google, pueden no ser perfectos y aún no están disponibles para todos los idiomas. Conectar un directorio Antes de poder desplegar un repositorio de GitHub en tu sitio de WordPress.com, primero tendrás que configurar la conexión entre los dos siguiendo estos pasos: Visita tu página Sitios: https://wordpress.com/sites/ Haz clic en el nombre de tu sitio para ver la vista general del sitio. Haz clic en la pestaña Despliegues . Haz clic en el botón « Conectar ». Si ves los repositorios en la lista, ya has conectado tu cuenta de GitHub. Continuar con el paso 11. Haz clic en el botón « Instalar la aplicación de WordPress.com». Se abrirá una nueva ventana y se te pedirá que inicies sesión en tu cuenta de GitHub si aún no lo has hecho. A continuación verás esta pantalla: Haz clic en el botón « Autorizar WordPress.com para desarrolladores ». Selecciona la organización o cuenta de GitHub en la que se encuentra tu repositorio. Selecciona qué repositorio/repositorios te gustaría conectar: Todos los repositorios: Si seleccionas esta opción, WordPress.com tendrá acceso a todos los repositorios actuales y futuros que sean propiedad de la cuenta de GitHub seleccionada. Esto incluye los repositorios públicos que son de solo lectura. Solo seleccionar repositorios: Al seleccionar esta opción podrás elegir a qué repositorios puede acceder WordPress.com en la cuenta de GitHub seleccionada. Cuando hayas elegido una opción, haz clic en el botón Instalar . La nueva ventana se cerrará y volverás a WordPress.com. El repositorio o los repositorios que hayas elegido se mostrarán junto con la cuenta de GitHub asociada a ese repositorio: Haz clic en Seleccionar junto al repositorio que quieras conectar. En este punto, deberías ver WordPress.com para desarrolladores en tus aplicaciones de GitHub autorizadas y en las aplicaciones de GitHub instaladas . Gestionar ajustes de despliegue Una vez que selecciones un repositorio, tendrás que ajustar los ajustes de despliegue: Rama de despliegue: Por defecto es la rama por defecto del repositorio (normalmente principal ) pero se puede cambiar a la rama que quieras usar. Directorio de destino: la carpeta del servidor donde quieres desplegar los archivos. Para los plugins, será /wp-content/plugins/my-plugin-name . Para los temas, será /wp-content/themes/my-theme-name . Para un despliegue parcial del sitio (es decir, varios plugins o temas), puedes usar /wp-content . El contenido de un repositorio se fusionará con el contenido existente del sitio de WordPress en el directorio especificado. Despliegues automáticos: puedes desplegar en WordPress.com de dos formas: Automático: Una vez que se haya confirmado el código, se desplegará en tu sitio de WordPress.com. Se recomiendan despliegues automáticos para los sitios de pruebas. Manual: El código se desplegará cuando solicites un despliegue . Se recomiendan despliegues manuales para los sitios de producción. Modo de despliegue: Hay dos tipos de despliegues: Simple: este modo copiará todos los archivos de una rama del repositorio al sitio y los desplegará sin post-procesamiento. Avanzado: Con este modo, puedes usar un script de workflow, activando los pasos de compilación personalizados, como la instalación de dependencias de Composer, la realización de pruebas de código previas al despliegue y el control del despliegue de archivos. Ideal para repositorios que necesitan software Composer o Node. Para obtener más información , consulta Despliegue avanzado a continuación. Una vez configurados todos los ajustes, haz clic en el botón Conectar . Se añadirá tu repositorio: Ten en cuenta que debes activar el primer despliegue, ya sea de forma automática o manual .Puedes conectar otro repositorio en cualquier momento haciendo clic en el botón « Conectar repositorio ». Despliegue avanzado Con el despliegue avanzado, puedes proporcionar un script de flujo de trabajo para procesar los archivos de tu repositorio antes del despliegue. Esto abre muchas posibilidades, como la comprobación de tu código para garantizar que cumple con los estándares de codificación de tu equipo, la ejecución de pruebas unitarias, la exclusión de archivos del despliegue, la instalación de dependencias y mucho más. Para empezar, echa un vistazo a nuestras recetas de workflow. Para configurar el despliegue avanzado: Aparecerá un formulario donde puedes configurar el despliegue. Haz clic en el nombre del repositorio para gestionar la conexión. En el lado derecho, en « Elige el modo de despliegue», elige Avanzado . Si el repositorio ya contiene un archivo de workflow, puedes seleccionarlo aquí. El sistema comprobará si hay algún error en el archivo. Si no se encuentran errores, vaya al paso 7. También puedes seleccionar la opción « Crear nuevo flujo de trabajo» para añadir un archivo de flujo de trabajo preconfigurado. Si eliges esta opción, se sobrescribirá el archivo del flujo de trabajo wpcom.yml si ya existe en tu repositorio. Haz clic en el botón « Instalar flujo de trabajo para mí » para enviar el archivo de flujo de trabajo al repositorio. Cuando se haya añadido y verificado un flujo de trabajo, haz clic en Actualizar . Tu repositorio ahora utilizará el despliegue avanzado. Despliega tu código Después de conectar tu repositorio de GitHub a un sitio, el siguiente paso es realmente desplegar tu código. Hay dos métodos de despliegue disponibles: automático y manual . No se recomiendan despliegues automáticos para los sitios de producción en vivo, ya que cualquier cambio de código en el repositorio se despliega automáticamente desde GitHub al sitio en vivo. En su lugar, plantéate configurar el despliegue automático en un sitio de pruebas y sincronizarlo con el de producción cuando estés listo. Los despliegues manuales te dan más control sobre cuándo se publican los cambios de código, ya que tendrás que activar manualmente cada despliegue. Recomendamos los despliegues manuales si no quieres utilizar un sitio de pruebas. Para activar manualmente un despliegue: Visita tu página Sitios: https://wordpress.com/sites/ Haz clic en el nombre de tu sitio para ver la vista general del sitio. Haz clic en la pestaña Despliegues . Haz clic en el menú de puntos suspensivos (⋮) del repositorio que quieras desplegar. Selecciona « Activar despliegue manual ». Deberías ver una notificación de banner que diga «Se ha creado la ejecución de despliegue» y el estado de despliegue cambiará a «En cola». Espera a que se complete el despliegue (el estado cambiará a «Desplegado»). Vuelve a hacer clic en el menú de puntos suspensivos (⋮) y elige « Ver ejecuciones de despliegue». El registro de ejecución de despliegue muestra el autor y el commit desplegado. Si haces clic en la entrada de ejecución de despliegue, puedes ver más información. Gestionar las conexiones existentes Para gestionar las conexiones de tu repositorio de GitHub existente: Visita tu página Sitios: https://wordpress.com/sites/ Haz clic en el nombre de tu sitio para ver la vista general del sitio. Haz clic en la pestaña Despliegues . Deberías ver la lista de conexiones. La lista de conexiones se muestra si hay al menos una conexión entre un repositorio de GitHub y tu sitio. La lista incluye información relevante para cada conexión, como el nombre del repositorio y la rama, la última confirmación que se implementó en un sitio, cuándo ocurrió, dónde se colocó el código, cuánto tiempo duró la ejecución del despliegue y su estado. Hay acciones adicionales disponibles después de hacer clic en el menú de puntos suspensivos (⋮): Activar despliegue manual: inicia una ejecución de despliegue en la última confirmación de la rama configurada. Ver ejecuciones de despliegue: Abre la vista de registros de ejecuciones de despliegue para el repositorio conectado. Configurar la conexión: abre la vista de gestionar la conexión del repositorio. Desconectar repositorio: elimina la conexión entre el repositorio y el sitio. Registros de ejecución de despliegue Los registros de ejecuciones de despliegues proporcionan un registro detallado paso a paso de cada despliegue, ya sea que se active de forma automática o manual. Estos registros te ayudan a hacer un seguimiento de los cambios, supervisar el estado del despliegue y solucionar los problemas que puedan surgir. Con acceso a los registros de las últimas 10 ejecuciones en un plazo de 30 días, puedes revisar fácilmente lo que ha ocurrido durante cada despliegue y asegurarte de que todo funciona sin problemas. Para comprobar los registros de un despliegue: Visita tu página Sitios: https://wordpress.com/sites/ Haz clic en el nombre de tu sitio para ver la vista general del sitio. Haz clic en la pestaña Despliegues . Haz clic en el menú de puntos suspensivos (⋮) situado junto al repositorio para el que quieres ver los registros. Selecciona « Ver ejecucionesde despliegue ». La vista de lista Ejecuciones de despliegue muestra las confirmaciones que se han desplegado en el sitio, el estado del despliegue, la fecha y la duración. Haz clic en cualquier lugar de una ejecución para ampliar y ver más información sobre el despliegue. Los registros proporcionan un registro de todos los comandos ejecutados, desde obtener código de GitHub hasta colocarlo en el directorio de destino. Puedes ampliar las líneas de registro para ver más información haciendo clic en « mostrar más ». Desconectar un repositorio Cuando desconectas un repositorio de GitHub de tu sitio, cualquier cambio futuro en el repositorio ya no afectará a tu sitio. Por defecto, los archivos desplegados permanecen en tu sitio, pero tienes la opción de eliminarlos durante el proceso de desconexión. Para eliminar un repositorio: Visita tu página Sitios: https://wordpress.com/sites/ Haz clic en el nombre de tu sitio para ver la vista general del sitio. Haz clic en la pestaña Despliegues . Haga clic en el menú de puntos suspensivos (⋮) del repositorio. Selecciona « Desconectar repositorio ». Aparecerá una ventana de diálogo. Haz clic en el botón para eliminar los archivos asociados del sitio. Haz clic en « Desconectar repositorio » para cerrar el diálogo y desconectar el repositorio. Ten en cuenta que WordPress.com para desarrolladores seguirá apareciendo en tus aplicaciones de GitHub instaladas y en tus aplicaciones de GitHub autorizadas . Esto se debe a que WordPress.com todavía tiene acceso al repositorio, pero la conexión se ha eliminado. Desconectar de WordPress.com de GitHub También puedes revocar el acceso de WordPress.com a tu cuenta de GitHub. Puedes hacerlo en cualquier momento visitando la configuración de Aplicaciones en GitHub. Para revocar el acceso autorizado a la aplicación a tu cuenta de GitHub: Ve a las aplicaciones autorizadas de GitHub . Haz clic en Revocar junto a WordPress.com para desarrolladores . Haz clic en el botón « Entiendo, revocar acceso ». Incluso si revocas el acceso autorizado a la aplicación, se puede seguir implementando código porque la aplicación WordPress.com para desarrolladores sigue instalada en las cuentas seleccionadas. Para revocar el acceso a la instalación de WordPress.com y desactivar la posibilidad de desplegar código en tu sitio de WordPress.com: Ve a las aplicaciones de GitHub instaladas . Haz clic en Configurar junto a WordPress.com para desarrolladores . En el área Zona de peligro, haz clic en Desinstalar y, cuando se te pida, haz clic en Aceptar . Eliminar WordPress.com de la lista de aplicaciones autorizadas no significa que los repositorios se eliminarán o dejarán de funcionar; tus repositorios seguirán existiendo en GitHub después de que revoques el acceso a WordPress.com, pero WordPress.com ya no podrá desplegar código. Guías relacionadas Recetas de despliegues de GitHub 2 min de lectura Uso del escritorio de WP Admin 7 min de lectura Plugins 1 min de lectura Monitorización del sitio 7 min de lectura En esta guía Tutorial en vídeo Conectar un directorio Gestionar ajustes de despliegue Despliegue avanzado Despliega tu código Gestionar las conexiones existentes Registros de ejecución de despliegue Desconectar un repositorio Desconectar de WordPress.com de GitHub ¿Tienes alguna pregunta? Pregunta a nuestro AI Assistant Volver arriba ¿No has encontrado lo que necesitabas? Ponte en contacto con nosotros Obtén respuestas de nuestro AI Assistant, con acceso a soporte humano especializado las 24 horas del día en los planes de pago. Haz una pregunta en nuestro foro Busca preguntas y obtén respuestas de otros usuarios experimentados. Copied to clipboard! WordPress.com Productos Hosting WordPress WordPress para Agencias Hazte afiliado Dominios Creador de webs con IA Creador de webs Crea un blog Correo electrónico profesional Servicio de diseño web WordPress Studio WordPress Enterprise Funcionalidades Resumen Temas de WordPress Plugins de WordPress Patrones de WordPress Google Apps Recursos Blog de WordPress.com Generador de nombres de empresa Creador de logos WordPress.com Reader Accesibilidad Eliminar suscripciones Ayuda Centro de soporte Guías Cursos Foros Contacto Recursos para programadores Empresa Acerca de Prensa Condiciones del servicio Política de privacidad No vendas ni compartas mi información personal Aviso de privacidad para usuarios de California Deutsch Español Français Bahasa Indonesia Italiano Nederlands Português do Brasil Svenska Türkçe Русский العربية עִבְרִית 日本語 한국어 简体中文 繁體中文 English Deutsch Español Français Bahasa Indonesia Italiano Nederlands Português do Brasil Svenska Türkçe Русский العربية עִבְרִית 日本語 한국어 简体中文 繁體中文 English Aplicaciones móviles Descargar en App Store Obtener en Google Play Redes sociales WordPress.com en Facebook WordPress.com en X (Twitter) WordPress.com en Instagram WordPress.com en YouTube Automattic Automattic Trabaja con nosotros Cargando comentarios... Escribe un comentario... Correo electrónico (Obligatorio) Nombre (Obligatorio) Web | 2026-01-13T09:29:33 |
https://groovy.apache.org/ | The Apache Groovy™ programming language - Contribute Socialize Discuss on the mailing list Groovy on X Groovy on Bluesky Groovy on Mastodon Groovy on LinkedIn Events and conferences Source code on GitHub Report issues in Jira Stack Overflow questions Slack Community You are using an outdated browser. Please upgrade your browser to improve your experience. Apache Groovy™ Learn Documentation Download Support Contribute Ecosystem Blog posts Socialize Improve this doc Getting Involved Would you like to help us make the Groovy™ programming language even better? There are many ways in which you can get involved, make a difference and help the Groovy development team to make Groovy even, well, groovier? We really appreciate and welcome contributions and you can help us by: helping other users or discussing future language directions on the mailing lists contribute to discussions on Slack - this channel is not endorsed by the Apache Software Foundation, it's run by Groovy enthusiasts in the community for casual conversations and Q&A, reporting or fixing issues you encounter in our bug tracker documenting various aspects of the language or its APIs writing a blog post about some Groovy feature or your Groovy usage creating or commenting on the Groovy Enhancement Proposals which describe how we make significant changes to the language improving this website covering the code base with more tests to avoid future regressions, and of course, by contributing bug fixes or new features Discussing on the mailing lists and forums If you encounter a problem, want to discuss a new feature, share interesting findings, and more, then the mailing lists are the place to go to start a conversation with the Groovy developers and other Groovy users. Discussions on the mailing list are archived. It's the place to go to for all formal discussions or if you want to search the archives. Alternatively, for more casual conversations and Q&A, consider using the Slack channel. (This channel is not endorsed by the Apache Software Foundation; it's run by Groovy enthusiasts in the community.) Reporting issues If you are wanting to search existing issues, raise a new one or are keen to fix some existing issues, then you should become familiar with Groovy's Bug tracker . Before submitting a new issue, we recommend you read our guide to reporting issues Report an issue Writing a blog post Groovy has a lot of great features that some folks have never heard of. Why not write an interesting post about your favourite feature. You can use your own blogging platform or create a pull request for a new post in the blog part of our website which are published onto our own blogging site . Improving the documentation The documentation of the Groovy programming language comes in various forms: the reference documentation covering the language specification, the user guides, getting started, and more. the GroovyDoc APIs documenting the classes of the Groovy code base the Groovy GDK documentation, explaining how Groovy enriches the JDK APIs this website To contribute to the Groovy reference documentation, this blog post about writing your own post will give you numerous pointers. All the above is stored in our code repositories on Github , so having an account on Github would be ideal. Contributing to this website is fairly easy, if you have a Github account already, as you can click on the Improve this doc buttons that you can see on all the pages of this website. So don't hesitate to help us improve it, fix typos, broken language, clarify complicated sections, add new material, etc. Please check the following section for more information on how to contribute to our codebase. Contributing code If you know the area you want to contribute to, this is great, but if you are looking for some first contributions, the Groovy development team tries to maintain a list of tickets of possible easy contributions that could get you started on your journey to become a Groovy committer. Just raise your hand on the Groovy developer mailing list to tell us about your desire to work on that ticket. For more complicated tasks, the best approach is also to bring that to the attention of the Groovy developers, so they can give you some guidance on how best to tackle a particular problem, discuss implementation ideas and the semantics or scope of the proposed change. Cloning the code base To work on the Groovy code base, you should be proficient enough in git and you should have an account on Github to be able to create pull requests with your changes. Please fork https://github.com/apache/groovy and create a local clone of your fork as explained in fork a repo . Make sure you configure Git appropriately with the same email that you registered with on Github: git config --global user.name "YOUR NAME" git config --global user.email "YOUR EMAIL" You can verify these are configured appropriately by running: git config --list Working on the code base If you are working with the IntelliJ IDEA development environment, this screencast gives lots of details on how to setup your IDE. Then, to work on the Groovy code base, to build and test Groovy, you can follow the instructions from the readme file in the Groovy repository. The most important command you will have to run before sending your changes is the test command: ./gradlew test For a successful contribution, all tests should be green! Creating a pull request Once you are satisfied with your changes: commit your changes in your local branch push your changes to your remote branch on Github send us a pull request Subprojects The following subprojects are run under the auspices of the Groovy project: Geb is a browser automation solution. Donating to Friends of Groovy Open Collective As an independent initiative, members of the broader Groovy community have set up an open collective for Groovy: Friends of Groovy Open Collective This initiative is designed to complement the Apache project and the many contributions we get from our great community and supporters. Build status The Groovy sources are tested thanks to our continuous integration server . Groovy Learn Documentation Download Support Contribute Ecosystem Blog posts About Source code Security Books Thanks Sponsorship FAQ Search Socialize Discuss on the mailing list Groovy on X Groovy on Bluesky Groovy on Mastodon Groovy on LinkedIn Events and conferences Source code on GitHub Report issues in Jira Stack Overflow questions Slack Community The Groovy programming language is supported by the Apache Software Foundation and the Groovy community. Apache, Apache Groovy, Groovy, and the ASF logo are either registered trademarks or trademarks of The Apache Software Foundation. © 2003-2025 the Apache Groovy project — Groovy is Open Source: license , privacy policy . | 2026-01-13T09:29:33 |
https://gitstar-ranking.com/vercel | vercel - Gitstar Ranking Gitstar Ranking Users Organizations Repositories Rankings Users Organizations Repositories Sign in with GitHub vercel Star 495167 Rank 13 Go to GitHub Fetched on 2026/01/12 15:59 207 Repositories next.js 137106 hyper 44620 swr 32248 turborepo 29495 pkg 24423 ai 20788 ai-chatbot 19222 vercel 14618 commerce 13812 satori 12823 micro 10622 serve 9794 ncc 9756 styled-jsx 7800 nextjs-subscription-payments 7673 next-forge 6820 platforms 6583 ms 5487 examples 4911 next-learn 4636 og-image 4055 streamdown 4051 release 3586 geist-font 3103 hazel 3067 next-app-router-playground 2923 next-plugins 2675 virtual-event-starter-kit 2180 little-date 1950 async-retry 1905 react-tweet 1850 nextjs-postgres-nextauth-tailwindcss-template 1580 nft 1576 workflow 1565 ai-elements 1381 avatar 1346 style-guide 1315 modelfusion 1307 arg 1291 bidc 1237 nextjs-postgres-auth-starter 1027 nextgram 1008 next-react-server-components 996 fun 956 edge-runtime 893 on-demand-isr 892 server-components-notes-demo 750 nextjs-portfolio-starter 728 micro-dev 711 components.build 692 1 2 3 4 5 › Released by @k0kubun in December 2014. Fork me on GitHub . | 2026-01-13T09:29:33 |
https://wordpress.com/nl/support/github-deployments/ | GitHub-implementaties gebruiken op WordPress.com – Ondersteuning Producten Mogelijkheden Hulpmiddelen Abonnementen en prijzen Inloggen Aan de slag Menu WordPress Hosting WordPress voor agencies Een geassocieerd bedrijf worden Domeinnamen AI websitebouwer Websitebouwer Maak een blog aan Nieuwsbrief Professionele e-mail Website-ontwerpservices Commerce WordPress Studio WordPress voor bedrijven Overzicht WordPress-thema’s WordPress plugins WordPress patronen Google Apps Ondersteuningscentrum WordPress nieuws Bedrijfsnaamgenerator Logo maker Ontdek nieuwe berichten Populaire tags Blogs zoeken Sluit het navigatiemenu Aan de slag Aanmelden Inloggen Over Abonnementen en prijzen Producten WordPress Hosting WordPress voor agencies Een geassocieerd bedrijf worden Domeinnamen AI websitebouwer Websitebouwer Maak een blog aan Nieuwsbrief Professionele e-mail Website-ontwerpservices Commerce WordPress Studio WordPress voor bedrijven Mogelijkheden Overzicht WordPress-thema’s WordPress plugins WordPress patronen Google Apps Hulpmiddelen Ondersteuningscentrum WordPress nieuws Bedrijfsnaamgenerator Logo maker Ontdek nieuwe berichten Populaire tags Blogs zoeken Jetpack-app Meer weten Ondersteuningscentrum Handleidingen Cursussen Forums Contact Zoeken Ondersteuningscentrum / Handleidingen Ondersteuningscentrum Handleidingen Cursussen Forums Contact Handleidingen / Tools / GitHub-implementaties gebruiken op WordPress.com GitHub-implementaties gebruiken op WordPress.com GitHub-implementaties integreert je GitHub-repository’s rechtstreeks met je WordPress.com-site, waardoor je een versiegestuurde, geautomatiseerde workflow krijgt voor het implementeren van plugins, thema’s of volledige sitewijzigingen. Deze handleiding beschrijft het configuratieproces en hoe je je gekoppelde repository’s beheert. Deze functie is beschikbaar op sites met een Business- en Commerce-abonnement van WordPress.com . Als je een Business-abonnement hebt, moet je deze activeren . Voor gratis sites of sites met Personal- en Premium-abonnementen moet je je abonnement upgraden om toegang te krijgen tot deze functie. In deze handleiding Videotutorial Een repository koppelen Implementatie-instellingen beheren Geavanceerde implementatie Je code implementeren Bestaande koppelingen beheren Logboeken met uitgevoerde implementaties Een repository loskoppelen WordPress.com loskoppelen van GitHub Heb je nog vragen? Vraag het onze AI-assistent Terug naar boven Videotutorial Deze video is in het Engels. YouTube biedt automatische vertaalfuncties zodat je de video in je eigen taal kunt bekijken: Automatisch vertaalde ondertitels inschakelen: Speel de video af. Klik op het ⚙️ Instellingen -pictogram (rechtsonder in het videoscherm). Selecteer Ondertiteling/CC . Kies Automatisch vertalen . Selecteer je voorkeurstaal. Automatische nasynchronisatie (experimenteel) gebruiken: Klik op ⚙️ Instellingen . Selecteer Audiotrack . Kies de taal waarin je wilt luisteren. ℹ️ Vertalingen en nasynchronisaties worden automatisch gegenereerd door Google, kunnen onjuistheden bevatten en de automatische nasynchronisatie is nog in testfase, dus niet in alle talen beschikbaar. Een repository koppelen Voordat je een GitHub-repository kan implementeren op je WordPress.com-site, moet je eerst de verbinding tussen de twee instellen met behulp van de volgende stappen: Bezoek de pagina Sites: https://wordpress.com/sites/ Klik op de naam van je site om het siteoverzicht te bekijken. Klik op het tabblad Implementaties . Klik op de knop ‘ Repository koppelen ‘. Als je vervolgens repository’s ziet vermeld, heb je al je GitHub-account gekoppeld. Ga door aan naar stap 11. Klik op de knop ‘ De WordPress.com-app installeren ‘. Er wordt een nieuw venster geopend en je wordt gevraagd in te loggen op je GitHub-account als je dit nog niet hebt gedaan. Dan zie je dit scherm: Klik op de knop ‘ WordPress.com autoriseren voor ontwikkelaars ‘. Selecteer de GitHub-organisatie of het account waar je repository zich bevindt. Selecteer welke repository/repository’s je wilt koppelen: Alle repository’s: als je deze optie selecteert, krijgt WordPress.com toegang tot alle huidige en toekomstige repository’s die eigendom zijn van het geselecteerde GitHub-account. Dit is inclusief openbare repository’s die alleen-lezen zijn. Alleen repository’s selecteren: als je deze optie selecteert, kun je kiezen welke repository’s WordPress.com kan openen op het geselecteerde GitHub-account. Zodra je een optie hebt geselecteerd, klik je op de knop Installeren . Het nieuwe venster wordt gesloten en je wordt teruggeleid naar WordPress.com. Je geselecteerde repository/repository’s moeten worden vermeld samen met het GitHub-account dat aan die repository is gekoppeld: Klik op Selecteren naast de repository die je wilt koppelen. Op dit punt zou je WordPress.com voor ontwikkelaars moeten zien onder je geautoriseerde GitHub-apps en geïnstalleerde GitHub-apps . Implementatie-instellingen beheren Zodra je een repository selecteert, moet je de implementatie-instellingen aanpassen: Implementatie-branch: wordt standaard ingesteld op de standaard-branch van de repository (meestal main ), maar kan worden gewijzigd naar de branch die je wilt gebruiken. Doelmap: de servermap waar je de bestanden wilt implementeren. Voor plugins is het /wp-content/plugins/my-plugin-name . Voor thema’s is het /wp-content/themes/my-theme-name . Voor een gedeeltelijke site-implementatie (d.w.z. meerdere plugins of thema’s), kan je /wp-content gebruiken. De inhoud van een repository wordt samengevoegd met de bestaande inhoud van de WordPress-site in de gespecificeerde map. Automatische implementaties: er zijn twee manieren waarop je kan implementeren op WordPress.com: Automatisch: zodra de code is vastgelegd, wordt deze geïmplementeerd op je WordPress.com-site. Automatische implementaties worden aanbevolen voor testsites. Handmatig: de code wordt geïmplementeerd zodra je een implementatie aanvraagt. Handmatige implementaties worden aanbevolen voor productiesites. Implementatiemodus: er zijn twee soorten implementaties: Simpel: deze modus kopieert alle bestanden van een tak van de repository naar de site en implementeert ze zonder nabewerking. Geavanceerd: in deze modus kun je een workflowscript gebruiken dat aangepaste bouwstappen inschakelt, zoals het installeren van Opstel-afhankelijkhede, het uitvoeren van codetests voorafgaand aan de implementatie en het beheren van bestandsimplementatie. Ideaal voor repository’s die Opstel- of Node-software nodig hebben. Zie Geavanceerde implementatie hieronder voor meer informatie . Klik op de knop Koppelen zodra alle instellingen zijn geconfigureerd. Je repository wordt toegevoegd: Let op: je moet de eerste implementatie activeren, automatisch of handmatig . Je kan dan op elk moment koppelen aan een andere repository door op de knop ‘ Repository koppelen ‘ te klikken. Geavanceerde implementatie Met Geavanceerde implementatie kan je een workflowscript leveren om bestanden in je repository te verwerken voordat je ze implementeert. Dit opent vele mogelijkheden, zoals het controleren van je code om er zeker van te zijn dat deze voldoet aan de coderingsnormen van je team, het uitvoeren van unit-tests, het uitsluiten van bestanden van de implementatie, het installeren van afhankelijkheden en nog veel meer. Bekijk onze workflowrecepten om aan de slag te gaan. Geavanceerde implementatie instellen: Er verschijnt een formulier waarop je de implementatie kunt configureren. Klik op de naam van de repository om de verbinding te beheren. Aan de rechterkant, onder ‘ Je implementatiemodus kiezen ‘, kies je Geavanceerd . Als de repository al een workflowbestand bevat, kan je dat hier selecteren. Het systeem controleert het bestand op eventuele fouten. Als er geen fouten worden gevonden, ga dan verder naar stap 7. Je kunt ook de optie ‘ Nieuwe workflow maken ‘ selecteren om een vooraf geconfigureerd workflowbestand toe te voegen. Als je voor deze optie kiest, wordt het workflowbestand wpcom.yml overschreven als het al in je repository bestaat. Klik op de knop ‘ Installeer workflow voor mij ‘ om het workflowbestand toe te voegen aan de repository. Zodra een workflow is toegevoegd en geverifieerd, klik op Bijwerken . Je repository maakt nu gebruik van geavanceerde implementatie. Je code implementeren Nadat je je GitHub-repository hebt gekoppeld aan een site, is de volgende stap eigenlijk het implementeren van je code. Er zijn twee implementatiemethoden beschikbaar: automatisch en handmatig . Automatische implementaties worden niet aanbevolen voor live productiesites, omdat alle codewijzigingen in de repository automatisch worden geïmplementeerd van GitHub naar de live site. Overweeg in plaats daarvan om een automatische implementatie in te stellen voor een testsite en deze te synchroniseren met de productie zodra je er klaar voor bent. Handmatige implementaties geven je meer controle over wanneer je codewijzigingen live worden gepusht, omdat je elke implementatie handmatig moet activeren. We raden handmatige implementaties aan als je geen testsite wilt gebruiken. Handmatig een implementatie activeren: Bezoek de pagina Sites: https://wordpress.com/sites/ Klik op de naam van je site om het siteoverzicht te bekijken. Klik op het tabblad Implementaties . Klik op het menu met drie punten (⋮) in de repository die je wilt implementeren. Kies ‘ Handmatige implementatie activeren ‘. Je zou een bannermelding moeten zien met de tekst ‘Implementatie-uitvoering gemaakt’, en de implementatiestatus zal veranderen naar ‘In wachtrij geplaatst’. Wacht tot de implementatie is voltooid (de status wordt gewijzigd naar ‘Geïmplementeerd’). Klik nogmaals op het menu met drie punten (⋮) en kies ‘ Implementatie-uitvoeringen bekijken ‘. Het logboeken met uitgevoerde implementaties geeft de auteur en de geïmplementeerde commit weer. Als je op het item Implementatie uitvoeren klikt, kan je meer informatie bekijken. Bestaande koppelingen beheren Je bestaande koppelingen van GitHub-repository’s beheren: Bezoek de pagina Sites: https://wordpress.com/sites/ Klik op de naam van je site om het siteoverzicht te bekijken. Klik op het tabblad Implementaties . Je zou dan de lijst met koppelingen moeten zien. De lijst met verbindingen wordt weergegeven als er ten minste één koppeling is tussen een GitHub-repository en je site. De lijst bevat relevante informatie voor elke koppeling, zoals de naam en branch van de repository, de laatste commit die is geïmplementeerd op een site, wanneer deze is uitgevoerd, waar de code is geplaatst, hoelang de implementatie heeft geduurd en de status ervan. Er zijn aanvullende acties beschikbaar nadat je op het menu met drie punten (⋮) hebt geklikt: Handmatige implementatie activeren: start een implementatie op de laatste commit van de geconfigureerde branch. Implementatie-uitvoeringen bekijken: opent de weergave van het logboeken met uitgevoerde implementaties voor de gekoppelde repository. Koppeling configureren: opent de weergave Verbinding beheren voor de repository. Repository loskoppelen: verwijdert de verbinding tussen de repository en de site. Logboeken met uitgevoerde implementaties Logboeken met uitgevoerde implementaties bieden een gedetailleerd, stapsgewijs overzicht van elke implementatie, ongeacht of deze automatisch of handmatig wordt geactiveerd. Deze logboeken helpen je wijzigingen bij te houden, de implementatiestatus te bewaken en eventuele problemen op te lossen. Met toegang tot logboeken van de laatste 10 uitvoeringen binnen 30 dagen, kan je eenvoudig bekijken wat er tijdens elke implementatie is gebeurd en ervoor zorgen dat alles soepel verloopt. Logboeken van een implementatie controleren: Bezoek de pagina Sites: https://wordpress.com/sites/ Klik op de naam van je site om het siteoverzicht te bekijken. Klik op het tabblad Implementaties . Klik op het menu met drie punten (⋮) naast de repository waarvoor je de logboeken wilt bekijken. Selecteer ‘ Implementatie-uitvoeringen bekijken ‘. In de lijstweergave Implementatie-uitvoeringen worden afspraken weergegeven die zijn geïmplementeerd op de site, de implementatiestatus, de datum en de duur. Klik waar je ook bent tijdens een uitvoering om de weergave uit te klappen en meer informatie over de implementatie te bekijken. De logboeken bieden een record van alle uitgevoerde opdrachten, van het ophalen van code van GitHub tot het plaatsen in de doelmap. Je kunt de logregels uitvouwen om meer informatie te zien door op ‘ Meer weergeven ‘ te klikken. Een repository loskoppelen Wanneer je een GitHub-repository loskoppelt van je site, hebben toekomstige wijzigingen aan de repository niet langer invloed op je site. De geïmplementeerde bestanden blijven standaard op je site staan, maar je hebt de optie om ze te verwijderen tijdens het loskoppelingsproces. Een repository verwijderen: Bezoek de pagina Sites: https://wordpress.com/sites/ Klik op de naam van je site om het siteoverzicht te bekijken. Klik op het tabblad Implementaties . Klik op het menu met drie punten (⋮) in de repository. Selecteer ‘ Repository loskoppelen ‘. Er verschijnt een dialoogvenster. Klik op de schakelaar om gekoppelde bestanden van de site te verwijderen. Klik op ‘ Repository loskoppelen ‘ om het dialoogvenster te sluiten en de repository los te koppelen. Merk op dat WordPress.com voor ontwikkelaars nog steeds zal verschijnen in je geïnstalleerde GitHub-apps en je geautoriseerde GitHub-apps . Dit komt omdat WordPress.com nog steeds toegang heeft tot de repository, maar de koppeling is verwijderd. WordPress.com loskoppelen van GitHub Je kunt er ook voor kiezen om de toegang van WordPress.com tot je GitHub-account in te trekken. Je kan dit op elk moment doen door naar je applicatie-instellingen op GitHub te gaan. Geautoriseerde toegang tot je GitHub-account intrekken: Ga naar Geautoriseerde GitHub-apps . Klik op Intrekken naast WordPress.com voor ontwikkelaars . Klik op de knop ‘ Ik begrijp het, toegang intrekken ‘. Zelfs als je geautoriseerde toegang tot de app intrekt, kan er nog steeds code worden geïmplementeerd omdat de WordPress.com voor ontwikkelaars -app op de geselecteerde accounts blijft geïnstalleerd. De toegang tot de installatie van WordPress.com intrekken en de mogelijkheid om code te implementeren op je WordPress.com-site uitschakelen: Ga naar Geïnstalleerde GitHub-apps . Klik op Configureren naast WordPress.com voor ontwikkelaars . Klik in het gebied Gevarenzone op Verwijderen en klik vervolgens op OK wanneer dit wordt gevraagd. Het verwijderen van WordPress.com van de lijst met geautoriseerde apps betekent niet dat de repository’s worden verwijderd of niet meer werken; je repositories blijven bestaan op GitHub nadat je de toegang van WordPress.com hebt ingetrokken, maar WordPress.com kan geen code meer implementeren. Gerelateerde handleidingen Verbinding maken met SSH 4 min. leestijd Toegang tot de database van je site 3 min. leestijd De defensieve modus inschakelen: 1 min. leestijd In deze handleiding Videotutorial Een repository koppelen Implementatie-instellingen beheren Geavanceerde implementatie Je code implementeren Bestaande koppelingen beheren Logboeken met uitgevoerde implementaties Een repository loskoppelen WordPress.com loskoppelen van GitHub Heb je nog vragen? Vraag het onze AI-assistent Terug naar boven Kon je niet vinden wat je nodig had? Neem contact op Krijg antwoord van onze AI-assistent, met toegang tot 24/7 deskundige ondersteuning bij betaalde abonnementen. Stel een vraag op ons forum Blader door vragen en krijg antwoorden van andere ervaren gebruikers. Copied to clipboard! WordPress.com Producten WordPress Hosting WordPress voor agencies Een geassocieerd bedrijf worden Domeinnamen AI websitebouwer Websitebouwer Maak een blog aan Professionele e-mail Website-ontwerpservices WordPress Studio WordPress voor bedrijven Mogelijkheden Overzicht WordPress-thema’s WordPress plugins WordPress patronen Google Apps Hulpmiddelen WordPress.com blog Bedrijfsnaamgenerator Logo maker WordPress.com Lezer Toegankelijkheid Abonnementen verwijderen Hulp Ondersteuningscentrum Handleidingen Cursussen Forums Contact Hulpmiddelen voor ontwikkelaars Bedrijven Over Pers Gebruikersvoorwaarden Privacybeleid Mijn persoonsgegevens niet verkopen of delen Privacyverklaring voor gebruikers in Californië Deutsch Español Français Bahasa Indonesia Italiano Nederlands Português do Brasil Svenska Türkçe Русский العربية עִבְרִית 日本語 한국어 简体中文 繁體中文 English Deutsch Español Français Bahasa Indonesia Italiano Nederlands Português do Brasil Svenska Türkçe Русский العربية עִבְרִית 日本語 한국어 简体中文 繁體中文 English Mobiele apps Download op de App Store Verkrijg het op Google Play Social Media WordPress.com op Facebook WordPress.com op X (Twitter) WordPress.com op Instagram WordPress.com op YouTube Automattic Automattic Met ons samenwerken Reacties laden.... Laat een reactie achter... E-mail (Vereist) Naam (Vereist) Site Ondersteuning Aanmelden Inloggen Korte link kopiëren Deze inhoud rapporteren Beheer abonnementen | 2026-01-13T09:29:33 |
https://www.ecns.cn/video/2026-01-07/detail-iheyrzrv3836821.shtml | Insights丨From energy cooperation to industrial co-building: New momentum in Europe-China ties --> 中文 Home News Ecns Wire Business Travel Photo Video Voices RIGHT BG LINE Text: A A A Print Video Insights丨From energy cooperation to industrial co-building: New momentum in Europe-China ties 2026-01-07 09:14:31 Ecns.cn Editor : Meng Xiangjun ECNS App Download 2025 marks the 50th anniversary of the establishment of China-EU diplomatic relations. Bernardo Mendia, Secretary General of the Portugal-China Chamber of Commerce and Industry, noted during an exclusive interview with China News Network that Portugal and China have built a successful partnership in wind, solar and ocean-related sectors, with bilateral trade exceeding USD 9.2 billion in 2024. Mendia added that China is shifting from low-cost exports to high-tech, high-quality products. To foster a more balanced relationship, China is investing in factories in Europe, while Portugal seeks investment, technology transfer and job creation for mutual benefit. (Chen Tianhao) More Photo Maduro pleads not guilty in N.Y. court UN Security Council holds emergency meeting on Venezuela Harbin opens its 42nd Ice and Snow Festival China's Yangtze River remains world's busiest inland waterway by cargo throughput Bosideng Protest held in New York against U.S. military strikes on Venezuela Venezuelan President Nicolás Maduro transported to Brooklyn detention center International ice sculpture competition heats up in Harbin Mourners pay tribute to Crans-Montana bar fire victims Venezuelan leader Maduro brought to New York Beijing-Tangshan intercity railway starts full-line operation Passenger trips of 3 major Hainan airports exceed 50 million in 2025 First 'Grassland curling' attracts 350 competitors China launches two new satellites for space target detection test People perform 'circle dance' to pray for a bountiful new year in Qingha In numbers: China's high-speed rail mileage exceeds 50,000 km First batch of China's emergency humanitarian aid arrives in Cambodia Central London illuminated to welcome 2026 Chinese Foreign Minister meets Cambodian Deputy PM in Yunnan In Numbers: China holds Central Economic Work Conference to plan for 2026 Exploring vivid sports competition throughout 2025 Exploring stunning winter scenery in Altay China's first L3 self-driving car debuts in Chongqin Grand bridge ready for traffic operation in Guizhou Harbin's celebrity snowman lights up winter night Southbound Travel for Guangdong Vehicles scheme implemented for entry into urban Hong Kong China's Feng/Huang claim mixed doubles title at BWF World Tour Finals Exploring overwintering migratory birds in Poyang Lake Xi presents orders to promote two military officers to rank of genera Inner Mongolia holds winter festival Memorial held for victims of Bondi Beach shooting in Sydney New year display unveiled at Times Square Night view of the 27th Harbin Ice and Snow World resembles fairy tale China launches island-wide special customs operations in Hainan FTP Why the world comes to Yiwu Exploring Hainan Free Trade Port before island-wide special customs operations Most popular in 24h More Top news Musical theater market hits new heights China curbs dual-use item exports to Japan Hospital staff to be held accountable after newborn injured during umbilical cord procedure Humanoid robot works fully autonomously at a cinema China urges U.S. to stop using so-called 'China threat' as pretext to seek selfish gains More Video Insights丨China’s economy in UN official’s eyes: Resilience, exports, and high-tech transition Insights丨Portuguese economist sees stability and opportunity in China’s long-term planning LINE Media partners: People's Daily | Xinhua | CGTN | China Daily Back to top About Us | Jobs | Contact Us | Privacy Policy Copyright ©1999-2026 Chinanews.com. All rights reserved. Reproduction in whole or in part without permission is prohibited. [ 网上传播视听节目许可证（0106168) ] [ 京ICP证040655号 ] [ 京公网安备 11010202009201号 ] [ 京ICP备05004340号-1 ] --> --> | 2026-01-13T09:29:33 |
https://cloudflare.com/de-de/zero-trust/solutions/multi-channel-phishing/ | Multi-Channel-Phishing | Zero Trust | Cloudflare Registrieren Sprachen English English (United Kingdom) Deutsch Español (Latinoamérica) Español (España) Français Italiano 日本語 한국어 Polski Português (Brasil) Русский 繁體中文 简体中文 Plattform Connectivity Cloud Die Connectivity Cloud von Cloudflare bietet mehr als 60 Netzwerk-, Sicherheits- und Performance-Services. Enterprise Für große und mittelständische Unternehmen Kleinunternehmen Für kleine Organisationen Partner Werden Sie Cloudflare-Partner Anwendungsfälle Modernisierung von Anwendungen Höhere Performance App-Verfügbarkeit sicherstellen Web-Erfahrung optimieren Sicherheit modernisieren VPN-Ersatz Phishing-Schutz Schutz von Webanwendungen und APIs Netzwerkmodernisierung Coffee Shop-Networking WAN-Modernisierung Vereinfachung des Firmennetzwerks CXO-Themen KI einführen Die KI-Nutzung in der Belegschaft und digitalen Erlebnissen fördern. KI-Sicherheit Sichern Sie agentenbasierte KI- und GenAI-Anwendungen Datenkonformität Compliance optimieren und Risiken minimieren Post-Quanten-Kryptografie Daten schützen und Compliance-Standards erfüllen Branchen Gesundheitswesen Bankwesen Einzelhandel Gaming Öffentlicher Sektor Weitere Informationen Produktleitfaden Referenz-Architekturen Analyseberichte Vertiefung Ereignisse Demos Webinare Workshops Demo anfragen Produkte Produkte Workspace-Sicherheit Zero-Trust-Netzwerkzugriff Secure Web Gateway E-Mail-Sicherheit Cloud Access Security Broker Anwendungssicherheit DDoS-Schutz auf L7 Web Application Firewall API-Sicherheit Bot-Management Anwendungsperformance CDN DNS Smart Routing Load Balancing Netzwerke und SASE DDoS-Schutz auf L3/4 NaaS / SD- WAN Firewall as a Service Netzwerk-Interconnection Tarife und Preise Enterprise-Tarife KMU-Tarife Tarife für Privatanwender Zum Tarifvergleich Globale Dienste Support- und Success-Pakete Optimiertes Cloudflare-Erlebnis Professionelle Services Implementierung unter Leitung von Experten Technische Kundenbetreuung Fokussiertes technisches Management Security Operations-Dienst Cloudflare-Überwachung und -Vorfallsreaktion Domainregistrierung Domains kaufen und verwalten 1.1.1.1 Kostenlose DNS-Auflösung Weitere Informationen Produktleitfaden Referenz-Architekturen Analyseberichte Produktdemonstrationen und Rundgänge Entscheidungshilfe Entwickler Dokumentation Entwickler-Bibliothek Dokumentation und Leitfäden Anwendungsdemos Entwicklungsmöglichkeiten entdecken Tutorials Schritt-für-Schritt-Entwicklungsleitfäden Referenz-Architektur Diagramme und Designmuster Produkte Künstliche Intelligenz AI Gateway KI-Apps beobachten & steuern Workers AI ML-Modelle in unserem Netzwerk ausführen Rechenleistung Observability Protokolle, Metriken und Traces Workers Serverlose Apps erstellen/bereitstellen Medien Images Bilder transformieren & optimieren Realtime Echtzeit-Audio-/-Video-Apps entwickeln Speicher und Datenbank D1 Erstellen Sie serverlose SQL-Datenbanken R2 Daten ohne kostspielige Egress-Gebühren speichern Tarife und Preise Workers Serverlose Apps erstellen & bereitstellen Workers KV Serverloser Schlüssel-Werte-Speicher für Apps R2 Daten speichern ohne teure Egress-Gebühren Projekte entdecken Anwendungsbeispiele aus der Praxis KI-Demo in 30 Sekunden Schnellstart-Guide Erkunden Sie den Workers Playground Entwickeln, testen und bereitstellen Entwickler-Discord Werden Sie Teil der Community Jetzt entwickeln Partner Partner-Netzwerk Cloudflare hilft Ihnen zu wachsen, Innovationen voranzutreiben und Kundenbedürfnisse gezielt zu erfüllen. Partner-Portal Ressourcen finden und Angebote registrieren Arten von Partnerschaften PowerUP-Programm Unternehmenswachstum vorantreiben – während Kunden zuverlässig verbunden und geschützt bleiben Technologiepartner Entdecken Sie unser Ökosystem aus Technologie-Partnern und Integrationen Globale Systemintegratoren Unterstützen Sie eine nahtlose, groß angelegte digitale Transformation Service-Provider Entdecken Sie unser Netzwerk von geschätzten Service-Providern Self-Serve-Agenturprogramm Verwalten Sie Self-Serve-Konten für Ihre Kunden Peer-to-Peer-Portal Traffic-Einblicke für Ihr Netzwerk Einen Partner finden Steigern Sie Ihr Geschäft – vernetzen Sie sich mit Cloudflare Powered+ Partnern. Ressourcen Vertiefung Demos + Produktführungen On-Demand-Produktdemos Kundenreferenzen Mit Cloudflare zum Erfolg Webinare Aufschlussreiche Diskussionen Workshops Virtuelle Foren Bibliothek Hilfreiche Leitfäden, Roadmaps und mehr Berichte Erkenntnisse aus der Forschung von Cloudflare Blog Technische Vertiefungen und Produktneuigkeiten Learning Center Lerntools und praktische Ratgeber Erstellen Referenz-Architektur Technische Leitfäden Lösungs- & Produktleitfäden Produktdokumentation Dokumentation Dokumentation für Entwickler Kennenlernen theNET Erkenntnisse für das digitale Unternehmen Cloudflare TV Innovative Reihen und Events Cloudforce One Bedrohungsforschung und -maßnahmen Radar Internet-Traffic und Sicherheitstrends Analyseberichte Berichte von Branchenanalysten Ereignisse Kommende regionale Events Vertrauen, Datenschutz und Compliance Compliance-Informationen und -Richtlinien Support Kontakt Community-Forum Kontozugang verloren? Entwickler-Discord Hilfe holen Unternehmen Unternehmensinfos Leadership Vorstellung unseres Führungsteams Anlegerbeziehungen Informationen für Anleger Presse Aktuelle Nachrichten entdecken Stellenausschreibungen Offene Stellen erkunden Vertrauen, Datenschutz und Sicherheit Datenschutz Richtlinien, Daten und Schutz Vertrauen Richtlinien, Prozess und Sicherheit Compliance Zertifizierung und Regulierung Transparenz Richtlinien und Hinweise Öffentliches Interesse Humanitäre Hilfe Projekt Galileo Behörden Projekt „Athenian“ Wahlen Cloudflare for Campaigns Gesundheit Project Fair Shot Globales Netzwerk Globale Standorte und Status Anmelden Vertrieb kontaktieren Cloudy LLM-Zusammenfassungen von E-Mail-Erkennungen | Blog lesen > SASE & Workspace-Sicherheit Überblick Lösungen Produkte Ressourcen Preise Schutz vor Multi-Channel-Phishing mit Cloudflare Implementieren Sie einen mehrschichtigen Schutz, der über Ihren Posteingang hinausgeht Die Connectivity Cloud von Cloudflare bietet einen automatisierten, mehrschichtigen Ansatz zur Abwehr von Phishing-Bedrohungen über E-Mail, SMS, soziale Medien, Instant Messaging und andere Collaboration-Apps. Kontakt CLOUDFLARE MACHT DEN UNTERSCHIED Unkomplizierter, hochwirksamer Schutz Minimieren Sie das Phishing-Risiko mit branchenführenden Erkennungsfunktionen, die nur minimale Anpassungen erfordern. Stärkere Konsolidierung, niedrigere Kosten Reduzieren Sie Ihre Ausgaben mit einer einzigen, vollständig integrierten Plattform, die alle Phishing-Anwendungsfälle abdeckt. Schnell einsatzbereit, einfach zu verwalten Erhalten Sie sofortigen Schutz und reduzieren Sie den Zeit- und Arbeitsaufwand für die laufende Verwaltung. FUNKTIONSWEISE Vollständiger Multi-Channel-Schutz mit einer einzigen Plattform Nutzen Sie die einheitliche Sicherheitsplattform von Cloudflare, um zunächst E-Mails zu schützen und dann zusätzliche Zero Trust-Services zu aktivieren, um den Phishing-Schutz auf alle Kanäle auszuweiten. Kurzdarstellung der Lösung lesen Einfache Implementierung und Skalierung Fügen Sie schnell E-Mail-Sicherheit hinzu, um den wichtigsten Kanal zu schützen, und aktivieren Sie dann problemlos Multi-Channel-Funktionen in Ihrem eigenen Tempo. E-Mail-Bedrohungen stoppen Automatische Blockierung von Angriffen zur Übernahme geschäftlicher E-Mail-Konten (BEC), bösartigen Anhängen und anderen E-Mail-basierten Bedrohungen mit Hilfe von ML-gestützter kontextbezogener Analyse. Durch Datendiebstahl verursachte Sicherheitsverstöße verhindern Implementieren Sie bedingten Zugriff und Phishing-resistente FIDO2-Sicherheitsschlüssel, die als letzte Verteidigungslinie dienen, wenn Anmeldedaten gestohlen oder kompromittiert werden. Trügerische linkbasierte Angriffe blockieren Schirmen Sie Nutzer vor gezielten Angriffen ab, die verschiedene Kollaborationstools verwenden, um Nutzer zum Klicken auf geschickt verschleierte Links zu verleiten. Werner Enterprises bekämpft Phishing und konsolidiert die Sicherheit mit Cloudflare Werner Enterprises ist eines der größten Speditionsunternehmen in den Vereinigten Staaten und steht im Zentrum einer vernetzten Allianz von erstklassigen Supply-Chain-Lösungen. Das Unternehmen musste den Phishing-Schutz für seine große, verstreute Belegschaft verbessern, da die Angriffe immer häufiger und raffinierter wurden. Werner hat sich für Cloudflare Email Security entschieden, um die Posteingänge von Microsoft 365 zu schützen, den Schutz der Mobilgeräte- und Roaming-Nutzer zu verbessern und einen proaktiveren Ansatz zur Verhinderung von Phishing zu verfolgen. Das Unternehmen hat bösartige E-Mails reduziert und gleichzeitig die Komplexität der Verwaltung verringert. „Seit der Implementierung ist die Anzahl der bösartigen oder verdächtigen E-Mails, die unsere Benutzer täglich erhalten, um 50 % zurückgegangen.“ Sind Sie bereit, Phishing über mehrere Kanäle zu stoppen? Kontakt Anerkennung durch Analysten Cloudflare unter den Top 3 in der Kategorie „Aktuelles Angebot“ bei dieser Analysten-Bewertung von E-Mail-Sicherheitslösungen Cloudflare wird in der „Forrester Wave™-Bewertung von Sicherheitslösungen für E-Mails, Messengerdienste und Groupware, die im zweiten Quartal 2025 erschienen ist, als „Strong Performer“ eingestuft. Wir haben in neun Kategorien – darunter Anti-Malware und Sandboxing, Erkennung bösartiger URL und Websicherheit, Bedrohungsdaten sowie Inhaltsanalyse und -verarbeitung – die bestmögliche Bewertung (5.0/5.0) erhalten. In dem Bericht heißt es: „Cloudflare ist eine gute Wahl für Unternehmen, die die aktuellen Sicherheitstools für E-Mails, Messengerdienste und Groupware um eine tiefgreifende Analyse und Verarbeitung von Inhalten sowie um Funktionen zur Erkennung von Schadsoftware ergänzen möchten. Zum Bericht Was spricht für Cloudflare? Die Connectivity Cloud von Cloudflare vereinfacht den Schutz vor Multi-Channel-Phishing Die einheitliche Cloud-native Sicherheits- und Konnektivitätsplattform von Cloudflare richtet sich gegen Phishing in den Bereichen E-Mail, Instant Messaging, SMS, soziale Netzwerke und anderen Kollaborationstools. Modulare Architektur Erfüllen Sie eine ganze Reihe von Sicherheitsanforderungen, indem Sie von der umfassenden Interoperabilität und Anpassungsfähigkeit profitieren. Performance Schützen und befähigen Sie Mitarbeitende überall mit einem globalen Netzwerk, das etwa 50 ms von 95 % aller Internetnutzer entfernt ist. Bedrohungsdaten Verhindern Sie eine ganze Reihe von Cyberangriffen mit den Erkenntnissen, die durch die Beobachtung (Proxying) von ~20 % des Internets und die tägliche Blockierung von Milliarden Bedrohungen gewonnen werden. Einheitliche Schnittstelle Konsolidieren Sie Ihre Tools und Arbeitsabläufe. Ressourcen Slide 1 of 6 Kurzdarstellung der Lösung Erfahren Sie, wie Cloudflare mit E-Mail-Sicherheits- und Zero Trust- Services einen umfassenden Phishing-Schutz für Mitarbeiter und Anwendungen bietet. Kurzbeschreibung jetzt anfordern Erkenntnisse Entdecken Sie, wie Sie Nutzer präventiv vor Phishing, BEC-Angriffen und linkbasierten Angriffen mit Cloudflare Email Security schützen können. Website besuchen Erkenntnisse Identifizieren Sie die Phishing-Angriffe, die Ihren derzeitigen E-Mail-Schutz umgehen – ohne Kosten und ohne Auswirkungen auf Ihre Nutzer. Jetzt kostenlose Analyse anfordern Kurzdarstellung der Lösung Lesen Sie, wie Cloudflare das Phishing-Risiko durch die Anwendung von Schutzmaßnahmen und Kontrollen zur Browserisolierung verringern kann. Kurzdarstellung herunterladen Kundenreferenz Erfahren Sie, wie Cloudflare einen ausgeklügelten textbasierten Phishing-Angriff mit einer Multi-Faktor-Authentifizierung (MFA) vereitelt hat, die Hardware-Keys verwendet. Kundenreferenz lesen Berichte Untersuchen Sie die wichtigsten Angriffsmuster auf der Grundlage von etwa 13 Milliarden E-Mails, die Cloudflare über einen Zeitraum von einem Jahr verarbeitet hat. Bericht herunterladen Kurzdarstellung der Lösung Erfahren Sie, wie Cloudflare mit E-Mail-Sicherheits- und Zero Trust- Services einen umfassenden Phishing-Schutz für Mitarbeiter und Anwendungen bietet. Kurzbeschreibung jetzt anfordern Erkenntnisse Entdecken Sie, wie Sie Nutzer präventiv vor Phishing, BEC-Angriffen und linkbasierten Angriffen mit Cloudflare Email Security schützen können. Website besuchen Erkenntnisse Identifizieren Sie die Phishing-Angriffe, die Ihren derzeitigen E-Mail-Schutz umgehen – ohne Kosten und ohne Auswirkungen auf Ihre Nutzer. Jetzt kostenlose Analyse anfordern Kurzdarstellung der Lösung Lesen Sie, wie Cloudflare das Phishing-Risiko durch die Anwendung von Schutzmaßnahmen und Kontrollen zur Browserisolierung verringern kann. Kurzdarstellung herunterladen Kundenreferenz Erfahren Sie, wie Cloudflare einen ausgeklügelten textbasierten Phishing-Angriff mit einer Multi-Faktor-Authentifizierung (MFA) vereitelt hat, die Hardware-Keys verwendet. Kundenreferenz lesen Berichte Untersuchen Sie die wichtigsten Angriffsmuster auf der Grundlage von etwa 13 Milliarden E-Mails, die Cloudflare über einen Zeitraum von einem Jahr verarbeitet hat. Bericht herunterladen Kurzdarstellung der Lösung Erfahren Sie, wie Cloudflare mit E-Mail-Sicherheits- und Zero Trust- Services einen umfassenden Phishing-Schutz für Mitarbeiter und Anwendungen bietet. Kurzbeschreibung jetzt anfordern Erkenntnisse Entdecken Sie, wie Sie Nutzer präventiv vor Phishing, BEC-Angriffen und linkbasierten Angriffen mit Cloudflare Email Security schützen können. Website besuchen Erkenntnisse Identifizieren Sie die Phishing-Angriffe, die Ihren derzeitigen E-Mail-Schutz umgehen – ohne Kosten und ohne Auswirkungen auf Ihre Nutzer. Jetzt kostenlose Analyse anfordern Kurzdarstellung der Lösung Lesen Sie, wie Cloudflare das Phishing-Risiko durch die Anwendung von Schutzmaßnahmen und Kontrollen zur Browserisolierung verringern kann. Kurzdarstellung herunterladen Kundenreferenz Erfahren Sie, wie Cloudflare einen ausgeklügelten textbasierten Phishing-Angriff mit einer Multi-Faktor-Authentifizierung (MFA) vereitelt hat, die Hardware-Keys verwendet. Kundenreferenz lesen Berichte Untersuchen Sie die wichtigsten Angriffsmuster auf der Grundlage von etwa 13 Milliarden E-Mails, die Cloudflare über einen Zeitraum von einem Jahr verarbeitet hat. Bericht herunterladen ERSTE SCHRITTE Free-Tarife KMU-Tarife Für Unternehmen Empfehlung erhalten Demo anfragen Vertrieb kontaktieren LÖSUNGEN Connectivity Cloud Anwendungsdienste SASE- und Workspace-Sicherheit Netzwerkdienste Entwicklerplattform SUPPORT Hilfe-Center Kundensupport Community-Forum Entwickler-Discord Kein Kontozugang mehr? Cloudflare-Status COMPLIANCE Ressourcen rund um Compliance Vertrauen DSGVO Verantwortungsvolle KI Transparenzbericht Regelverstoß melden ÖFFENTLICHES INTERESSE Projekt Galileo Projekt Athenian Cloudflare for Campaigns Projekt „Fair Shot“ UNTERNEHMEN Über Cloudflare Netzwerkkarte Unser Team Logos und Pressekit Diversität, Gleichberechtigung und Inklusion Impact/ESG © 2026 Cloudflare, Inc. Datenschutzrichtlinie Nutzungsbedingungen Sicherheitsprobleme berichten Vertrauen und Sicherheit Cookie-Einstellungen Markenzeichen Impressum | 2026-01-13T09:29:33 |
https://giantrabbit.com/our-work?client=common-cause | Our Work | Giant Rabbit Skip to main content Menu Close Main navigation Our Services Our Work About Us Strategy Design Development CRM Selection & Data Migration Fundraising & User Analytics Drupal 7 Upgrades to Backdrop CMS Project Rescues Managed Hosting Support & Maintenance Security  All Arts & Culture Education Environment Health Human Rights Social Justice Technology & Privacy  About Giant Rabbit The Team Jobs Contact Us  Our Work Our clients are fighting for public health, access to abortion, and LGBTQ+ rights. They're going to court on behalf of asylum-seekers and promoting human rights around the world. We support organizations that fight climate change, work for environmental conservation, and warn people about the risks of avalanches. Our clients are also working theaters, performing arts organizations, museums, and cultural institutions. Defending human rights at home and abroad. Partner Since 2018 Center for Gender and Refugee Studies Partner Since 2022 Family Violence Appellate Project Partner Since 2013 Front Line Defenders Partner Since 2022 Human Rights First Partner Since 2022 Justice Action Center Partner Since 2016 National Network of Abortion Funds (NNAF) Partner Since 2020 Observatory for the Protection of Human Rights Defenders Partner Since 2022 Youth Law Center Working toward a healthier future. Partner Since 2019 American Academy of Pediatrics California Chapter 1 Partner Since 2022 Advancing New Standards in Reproductive Health (ANSIRH) Partner Since 2023 Beyond the Pill Partner Since 2015 Cutaneous Lymphoma Foundation Partner Since 2020 Farmers Market Coalition Partner Since 2021 HealthRIGHT 360 Partner Since 2019 Ibis Reproductive Health Services Partner Since 2020 Mandela Partners Protecting the environment and fighting climate change. Partner From 2022 To 2023 Audubon Canyon Ranch Partner Since 2017 Ecology Center Partner Since 2014 Edible Schoolyard Project Partner Since 2007 eLock Technologies Partner Since 2022 Environmental Grantmakers Association Partner Since 2019 Highstead Partner Since 2020 John Muir Land Trust Partner Since 2022 Just Zero Partner Since 2014 Leave No Trace Partner Since 2020 Northwest Avalanche Center (NWAC) Partner Since 2023 One Tree Planted Partner Since 2021 Payette Avalanche Center Partner Since 2022 Sempervirens Partner Since 2019 Sierra Avalanche Center Partner Since 2014 The Trust For Public Land Partner Since 2022 Utah Avalanche Center Working for social and economic justice for all. Partner Since 2021 A New Way of Life Partner Since 2022 Center for Constitutional Rights Partner Since 2021 Center for WorkLife Law Partner Since 2021 Common Cause Partner Since 2010 CompassPoint Partner Since 2021 Equality Action Center Partner Since 2018 Keshet Partner Since 2024 Labor Notes Partner Since 2022 Legal Link Partner Since 2022 Mirror Memoirs Partner Since 2013 Unbound Philanthropy Partner Since 2018 Migrant Justice Building connection through arts, culture, and food. Partner Since 2013 18 Reasons Partner Since 2021 Artists Communities Alliance Partner Since 2019 Authors Alliance Partner Since 2018 Company One Theatre Partner Since 2017 Howlround Theatre Commons Partner Since 2023 Lighthouse Writers Workshop Partner Since 2023 Museo de las Americas Partner Since 2013 Sacred Lands Film Project Improving the quality and accessibility of education. Partner Since 2022 Academy College Prep Partner From 2017 To 2022 Bellwether Education Partner Since 2020 California Community Colleges Transfer Guarantee Pathway to Historically Black Colleges and Universities Partner From 2019 To 2020 The College of Business at Oregon State University Partner Since 2011 Ignited Partner From 2018 To 2022 Maker Ed Partner Since 2014 myShakespeare Partner Since 2019 Umoja Community Education Foundation Using technology for good and defending digital rights and privacy. Partner Since 2014 Electronic Frontier Foundation Partner Since 2019 FreeBSD Foundation Partner From 2015 To 2016 Internet Archive Partner Since 2012 Society of Motion Picture & Television Engineers (SMPTE) Partner From 2013 To 2021 The TOR Project Partner Since 2014 USENIX Partner Since 2020 Women's Audio Mission Partner From 2013 To 2015 Wikimedia Foundation Non-profit Sectors Human Rights Health Environment Social Justice Arts & Culture Education Technology & Privacy ❮ How can we help? Get in touch Giant Rabbit LLC 415.355.4211 info@giantrabbit.com Copyright © 2018-2025 by Giant Rabbit LLC. Artwork by RBlack . | Read our privacy policy . | 2026-01-13T09:29:33 |
https://www.atlassian.com/nl/software/jira/guides/issues/tutorials | Tutorials over Jira Software-issues | Atlassian Close Deze pagina in jouw taal bekijken? Alle talen Kies je taal 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Ontvang het gratis Functies Alle functies Rovo in Jira Back Oplossingen Teams Usecases Bedrijfsomvang Teams Marketing Engineering Ontwerp Operations IT Usecases Aan de slag Planning Campagnebeheer Agile projectmanagement Programmabeheer Bedrijfsomvang Enterprise Back Producthandleiding Sjablonen Sjablonen Alle sjablonen Softwareontwikkeling Marketing Ontwerp Sales Operations Servicemanagement HR Juridische afdeling IT-activiteiten Finance Jira Service Management-sjablonen Back Prijzen Meer + Minder - Ontvang het gratis Back Ontvang het gratis Aan de slag Introductie tot Jira Jira voor teams 7 stappen om aan de slag te gaan met Jira Projecten Overzicht Tutorials Bronnen Borden Overzicht Tutorials Bronnen Werkitems/issues Overzicht Tutorials Bronnen Workflows Overzicht Tutorials Bronnen Integraties Overzicht Tutorials Bronnen Rapporten en dashboards Overzicht Tutorials Bronnen Inzichten Overzicht Tutorials Bronnen Toegangsrechten Overzicht Tutorials Bronnen JQL Overzicht Tutorials Spiekbriefje Bronnen Navigatie Overview Tutorials Resources Automatisering Overzicht Tutorials Bronnen Tijdlijn Overzicht Tutorials Bronnen Advanced Roadmaps Overzicht Tutorials Bronnen Jira mobile Overzicht Tutorials Bronnen Meer over Jira Versies van Jira Hostingopties Tutorials voor Jira-werkitems Een werkitem aanmaken Selecteer 'Aanmaken' in de navigatiebalk bovenaan. Je werkitem verschijnt in de backlog of op het bord van het project. Een werkitem zoeken Voer een globale zoekopdracht uit om een werkitem te zoeken binnen de gehele site Met de zoekbalk in de navigatiebalk bovenaan kun je snel zoeken naar werkitems in de gehele installatie, op werkitem-ID of trefwoorden. Je kunt je zoekopdracht verfijnen op project, uitvoerder en/of status. Voer een contextuele zoekopdracht uit om een werkitem te zoeken in het bord, de roadmap of backlogweergave van het project De zoekbalken zijn te vinden in de roadmap, backlog en bordweergave. Werkitems worden weergegeven in de zoekresultaten indien deze werkitems gevonden kunnen worden in de betreffende weergave. Zoek een werkitem in een bepaald project via de werkitemnavigator Navigeer naar 'Werkitems' in de zijbalknavigatie. Schakel tussen de modi 'Basic' of 'JQL' in de rechterbovenhoek van het scherm. In de basismodus kun je trefwoorden typen in de zoekbalk en/of de vervolgkeuzemenu's gebruiken om werkitems te filteren op project, werktype, status, uitvoerder en alle velden die een werkitem kan bevatten. In de JQL-modus moet je gestructureerde zoekopdrachten gebruiken met behulp van de Jira Query Language (JQL) om werkitems te zoeken. Houd er rekening mee dat de werkitemnavigator niet standaard beschikbaar is in teambeheerde projecten. Schakel deze functie in door naar Projectinstellingen > Functies > Werkitemnavigator te gaan. Een werktype aan een project toevoegen In teambeheerde projecten: Selecteer 'Projectinstellingen' in de zijbalknavigatie aan de linkerkant, selecteer vervolgens 'Werktypen' en klik ten slotte op + 'Werktype toevoegen'. Sleep en plaats de veldtypen die je in het werktype wilt gebruiken en geef elk veldtype een naam. Je kunt ook de standaardwaarden voor elk veld instellen als je dat wilt. In bedrijfsbeheerde projecten: Werkitems koppelen Open een werkitem. Selecteer Werkitem koppelen boven in de werkitem-modal. Kies het type werkitemkoppeling (bijvoorbeeld, 'dit werkitem wordt geblokkeerd door...') Specificeer de werkitems die je wilt koppelen door de volledige werkitemsleutel te typen (bijvoorbeeld ABC-123). Selecteer Koppelen . De lay-out van een werkitem configureren Selecteer een werkitem vanaf je bord. Selecteer in de rechteronderhoek van de werkitemweergave de optie Configureren . Sleep werkitemvelden naar de juiste plekken. Bedrijf Vacatures Evenementen Blogs Investeerders Atlassian Foundation Mediapakket Contact producten Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Alle gratis producten bekijken Bronnen Technische ondersteuning Aanschaf en licenties Atlassian Community Kennisdatabase Marketplace Mijn account Ondersteuningsticket maken Leren Partners Training en certificering Documentatie Voor ontwikkelaars Bedrijfsservices Alle bronnen tonen Copyright © 2025 Atlassian Privacybeleid Voorwaarden Impressum Taal kiezen Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:33 |
https://www.atlassian.com/ru/software/jira/guides/issues/tutorials | Обучающие материалы по задачам в Jira Software | Atlassian Close Хотите открыть эту страницу на своем языке ? Все языки Выберите язык 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Получить бесплатно Функции Все возможности Rovo в Jira Back Решения команды Примеры использования Размер компании команды Маркетинг Разработка Дизайн Операции ИТ Примеры использования Начало работы Планирование Управление кампаниями Управление проектами по гибкой методологии Agile Управление программами Размер компании Enterprise Back Руководство по продукту Шаблоны Шаблоны Все шаблоны Разработка программного обеспечения Маркетинг Дизайн Отдел продаж Операции Управление услугами HR Юриспруденция ИТ-операции Финансовый отдел Шаблоны Jira Service Management Back Цены Дополнительно + Меньше - Получить бесплатно Back Получить бесплатно Начало работы Знакомство с Jira Jira для команд Семь шагов для начала работы с Jira Проекты Обзор Обучающие материалы Ресурсы Доски Обзор Обучающие материалы Ресурсы Задачи Обзор Обучающие материалы Ресурсы Процессы Обзор Обучающие материалы Ресурсы Интеграции Обзор Обучающие материалы Ресурсы Отчеты и информационные панели Обзор Обучающие материалы Ресурсы Аналитика Обзор Обучающие материалы Ресурсы Права доступа Обзор Обучающие материалы Ресурсы JQL Обзор Обучающие материалы Шпаргалка Ресурсы Навигация Overview Tutorials Resources Автоматизация Обзор Обучающие материалы РЕСУРСЫ График Обзор Обучающие материалы Ресурсы Продвинутые дорожные карты Обзор Обучающие материалы Ресурсы Jira для мобильных устройств Обзор Обучающие материалы Ресурсы Подробнее о Jira Версии Jira Варианты размещения Обучающее руководство по задачам Jira Создание задачи Нажмите Create (Создать) на верхней панели навигации. Задача появится в бэклоге или на доске проекта. Поиск задач Глобальный поиск задач по всему сайту Строку поиска на верхней панели навигации можно использовать для быстрого поиска задач во всем экземпляре по идентификатору или ключевым словам. Область поиска можно сузить, указав проект, исполнителя и (или) статус. Контекстный поиск задач на доске проекта, дорожной карте или в представлении бэклога Строка поиска имеется на дорожной карте, в бэклоге и представлении доски. Задачи появятся в результатах поиска, если их удастся найти в соответствующем представлении. Поиск задачи в проекте с помощью навигатора задач Перейдите в раздел Work items (Задачи) на боковой панели навигации. Выберите режим Basic (Базовый) или JQL в правом верхнем углу экрана. В базовом режиме можно вводить в строке поиска ключевые слова и (или) использовать выпадающие меню для фильтрации задач по проекту, типу задачи, статусу, исполнителю и любым полям задачи. В режиме JQL можно создавать структурированные запросы на языке Jira Query Language (JQL) для поиска задач. Обратите внимание: в проектах команды навигатор задач по умолчанию недоступен. Перейдите в Project Settings > Features > Work item navigator (Настройки проекта > Возможности > Навигатор задач) и включите эту возможность. Добавление в проект типа задачи Для проектов команды: Перейдите в раздел Project Settings (Настройки проекта) на левой боковой панели навигации, выберите Work types (Типы задач) и нажмите + Add work type (+ Добавить тип задачи). Перетащите типы полей, которые вам понадобятся в этом типе задачи, и укажите имя для каждого типа поля. При желании можно задать для каждого поля значение по умолчанию. В проектах компании: Как связать задачи Откройте задачу. Выберите Link work item (Связать задачу) в верхней части модального окна задачи. Выберите тип ссылки на задачу (например, «эта задача блокируется задачами…»). Укажите одну или несколько задач, с которыми вы хотите связать данную задачу, введя их полные ключи (например, ABC-123). Выберите Link (Связать). Настройка макета задачи Выберите на доске любую задачу. Выберите Configure (Настроить) в правом нижнем углу представления задачи. Перетащите поля задачи в желаемые области. Компания Вакансии События Блоги Связи с инвесторами Atlassian Foundation Материалы для СМИ Свяжитесь с нами продукты Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Посмотреть все продукты Ресурсы Техническая поддержка Покупка и лицензирование Сообщество Atlassian База знаний Marketplace Мой аккаунт Заявка в поддержку Обучение Партнеры Обучение и сертификация Документация Ресурсы для разработчиков Сервисы Enterprise Смотреть все ресурсы © Atlassian, 2025 г. Политика конфиденциальности Условия использования Impressum Выберите язык Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:33 |
https://www.atlassian.com/software/jira/guides/issues/tutorials | Tutorials on Jira Work Items | Atlassian Close View this page in your language ? All languages Choose your language 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Get it free Features All Features Rovo in Jira Back Solutions Teams Use cases Company size Teams Marketing Engineering Design Operations IT Use cases Getting started Planning Campaign Management Agile Project Management Program Management Company size Enterprise Back Product guide Templates Templates All Templates Software Development Marketing Design Sales Operations Service Management HR Legal IT Operations Finance Jira Service Management templates Back Pricing More + Less - Get it free Back Get it free Getting started Introduction to Jira Jira for Teams 7 Steps to Get Started in Jira Projects Overview Tutorials Resources Boards Overview Tutorials Resources Work items/issues Overview Tutorials Resources Workflows Overview Tutorials Resources Integrations Overview Tutorials Resources Reports and Dashboards Overview Tutorials Resources Insights Overview Tutorials Resources Permissions Overview Tutorials Resources JQL Overview Tutorials Cheat sheet Resources Navigation Overview Tutorials Resources Automation Overview Tutorials Resources Timeline Overview Tutorials Resources Advanced planning Overview Tutorials Resources Jira Mobile Overview Tutorials Resources More about Jira Editions of Jira Hosting options Jira work items tutorials Create a work item Select “Create” in the top navigation. Your work item will appear in the backlog or board of the project. Find a work item Perform a global search and find a work item across the entire site The search bar in the top navigation enables you to quickly search for work items across the whole instance via work item ID or keywords. You can narrow down your search by project, assignee, and/or status. Perform a contextual search and find a work item in the project’s board, roadmap, or backlog view Search bars can be found in the roadmap, backlog, and board view. Work items would appear in the search results if these work items can be found that particular view. Find a work item in a given project via Work item Navigator Navigate to “Work items” in the sidebar navigation. Toggle between “Basic” or “JQL” modes in the top right of the screen. In Basic mode, you can type keywords in the search bar and/or use the dropdown menus to filter work items by project, work type, status, assignee, and any fields that a work item can have. In JQL mode, you to build structured queries using the Jira Query Language (JQL) to search for work items. Please note that the Work item Navigator is not available by default in team-managed projects. Enable this feature by going to Project Settings > Features > Work item navigator . Add an work type to a project In team-managed projects: Select “Project Settings” in the sidebar navigation on the left, then select “Work types”, then hit “+ Add work type”. Drag and drop the types of fields you’d like to have in the work type, and give each field type a name. You could also set the default values for each field if you’d like. In company-managed projects: How to link work items Open a work item. Select Link work item at the top of the work item modal. Choose the type of work item link (for example, "this work item is blocked by..."). Specify the work item(s) you want to link to by typing the full work item key (for example, ABC-123). Select Link . Configure a work item’s layout Select any work item from your board. In the bottom right of the work item view, select Configure . Drag and drop work item fields in the appropriate regions. Company Careers Events Blogs Investor Relations Atlassian Foundation Press kit Contact us products Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket See all products Resources Technical support Purchasing & licensing Atlassian Community Knowledge base Marketplace My account Create support ticket Learn Partners Training & certification Documentation Developer resources Enterprise services See all resources Copyright © 2025 Atlassian Privacy Policy Terms Impressum Choose language Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:33 |
https://www.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.threads.com%252F%26amp%253Bh%3DAT3MxmFOjrt9aYBchLGSKdPWPfqoZ8uVG0I8P68QD7mSg88iRNJ5L0erzaBuBAleA5IMC20JuDj-z-Oqq62-c2azKmDlWxvSkmqhyahLZ8nKqNZvqThtJ2lJViTfMFkgbIO1AoRKvSc2r498 | Facebook Facebook 이메일 또는 휴대폰 비밀번호 계정을 잊으셨나요? 새 계정 만들기 일시적으로 차단됨 일시적으로 차단됨 회원님의 이 기능 사용 속도가 너무 빠른 것 같습니다. 이 기능 사용에서 일시적으로 차단되었습니다. Back 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T09:29:33 |
https://cloudflare.com/es-la/events/ | Eventos de Cloudflare | Cloudflare Me interesa Idiomas English English (United Kingdom) Deutsch Español (Latinoamérica) Español (España) Français Italiano 日本語 한국어 Polski Português (Brasil) Русский 繁體中文 简体中文 Plataforma Conectividad cloud La conectividad cloud de Cloudflare ofrece más de 60 servicios de red, seguridad y rendimiento. Enterprise Para organizaciones grandes y medianas Pequeña empresa Para organizaciones pequeñas Socio Ser socio de Cloudflare Casos de uso Moderniza tus aplicaciones Acelera el rendimiento Protege la disponibilidad de tus aplicaciones Optimiza tu experiencia en la web Moderniza tu seguridad Reemplaza tu VPN Protégete contra el phishing Protege tu aplicaciones web y tus API Moderniza tus redes Red de cafeterías Moderniza tu WAN Simplifica tu red corporativa Temas de CXO Adopta la IA Incorpora IA a los equipos de trabajo y a las experiencias digitales Seguridad de IA Protege las aplicaciones de IA generativa y agéntica Cumplimiento de los datos Optimiza el cumplimiento normativo y minimiza el riesgo Criptografía poscuántica Protege los datos y cumple con los estándares de cumplimiento normativo Industrias Atención médica Banca Minoristas Videojuegos Sector público Recursos Guías de producto Arquitecturas de referencia Informes de analistas Eventos Eventos Demostraciones Seminarios web Talleres Solicitar una demo Productos Productos Seguridad del espacio de trabajo Acceso a la red Zero Trust Puerta de enlace web segura Seguridad del correo electrónico Agente de seguridad de acceso a la nube Seguridad para aplicaciones Protección DDoS a la capa 7 Firewall de aplicaciones web Seguridad de la API Gestión de bots Rendimiento de aplicaciones CDN DNS Enrutamiento inteligente Load balancing Redes y SASE Protección DDoS a las capas 3 - 4 NaaS/SD- WAN Firewall como servicio Interconexión de red Planes y precios Planes Enterprise Planes para pequeñas empresas Planes individuales Compara planes Servicios globales Paquetes de soporte para un rendimiento exitoso Experiencia optimizada de Cloudflare Servicios profesionales Implementación guiada por expertos Gestión de cuentas técnicas Gestión técnica enfocada Servicio de operaciones de seguridad Supervisión y respuesta de Cloudflare Registro de dominios Compra y gestiona dominios 1.1.1.1 Resolución de DNS gratuita Recursos Guías de producto Arquitecturas de referencia Informes de analistas Demos de productos y recorridos Ayúdame a elegir Desarrolladores Documentación Biblioteca para desarrolladores Documentación y guías Demos de aplicaciones Explora lo que puedes crear Tutoriales Tutoriales de creación paso a paso Arquitectura de referencia Diagramas y patrones de diseño Productos Inteligencia artificial AI Gateway Observa y controla las aplicaciones de IA Workers AI Ejecuta modelos de aprendizaje automático en nuestra red Proceso Observability Registros, métricas y seguimientos Workers Crea e implementa aplicaciones sin servidor Multimedia Images Transforma y optimiza imágenes Realtime Crea aplicaciones de audio y video en tiempo real Almacenamiento y base de datos D1 Desarrolla bases de datos SQL sin servidor R2 Almacena datos sin costosas tarifas de salida Planes y precios Workers Crea e implementa aplicaciones sin servidor Workers KV Almacén de clave-valor sin servidor para aplicaciones R2 Almacena datos sin costosas tarifas de salida Descubre proyectos Historias de nuestros clientes Demo de IA en 30 segundos Guía rápida para empezar Descubre Workers Playground Crea, prueba e implementa Discord para desarrolladores Únete a la comunidad Comienza a crear Socios Red de socios Crece, innova y satisface las necesidades de los clientes con Cloudflare Portal de socios Encuentra recursos y registra acuerdos Tipos de asociación Programa PowerUP Impulsa el crecimiento de tu negocio mientras garantizas la conexión y la seguridad de tus usuarios Socios de tecnología Explora nuestro ecosistema de asociaciones e integraciones tecnológicas Integradores de sistemas globales Apoyar la transformación digital eficiente a gran escala Proveedores de servicios Descubre nuestra red de valiosos proveedores de servicios Programa de agencias de autoservicio Gestiona las cuentas de autoservicio de tus clientes Portal punto a punto Información sobre el tráfico de tu red Encuentra un socio Impulsa tu negocio - conéctate con los socios de Cloudflare Powered+. Recursos Eventos Demos y recorridos por los productos Demostraciones de productos a pedido Casos prácticos Cloudflare, la clave del éxito Seminarios web Debates interesantes Talleres Foros virtuales Biblioteca Guías útiles, planes de desarrollo y mucho más Informes Información sobre investigaciones de Cloudflare Blog Análisis técnicos y novedades de productos Centro de aprendizaje Herramientas educativas y contenido práctico Desarrollar Arquitectura de referencia Guías técnicas Guías de soluciones y productos Documentación del producto Documentación Documentación para desarrolladores Explorar theNET Información estratégica para empresas digitales Cloudflare TV Series y eventos innovadores Cloudforce One Investigaciones y operaciones sobre amenazas Radar Tendencias del tráfico y la seguridad en Internet Informes de analistas Informes de investigación del sector Eventos Próximos eventos regionales Confianza, privacidad y cumplimiento normativo Información y políticas de cumplimiento normativo Soporte Te ayudamos Foro de la comunidad ¿Has perdido el acceso a tu cuenta? Discord para desarrolladores Te ayudamos Empresa información de la empresa Liderazgo Conoce a nuestros líderes Relaciones con inversores Información para inversores Prensa Consulta noticias recientes Empleo Explora las posiciones disponibles confianza, privacidad y seguridad Privacidad Política, datos y protección Confianza Política, proceso y seguridad Cumplimiento normativo Certificación y regulación Transparencia Política y divulgaciones INTERÉS PÚBLICO Asistencia humanitaria Proyecto Galileo Sector público Proyecto Athenian Elecciones Cloudflare para campañas Salud Project Fair Shot Red global Ubicaciones globales y estado Iniciar sesión Contacta con Ventas Reserva la fecha para Cloudflare Connect San Francisco 2026 19–22 de octubre de 2026 Únete a miles de líderes de la industria en una oportunidad única para impulsar la innovación y la colaboración en Cloudflare Connect 2025. Más información Todos los eventos programados América Europa, Oriente Medio y África APJC Washington, DC GovCIO AI Summit • Jan 9 Coming soon San Diego, CA AFCEA West • Feb 10 - Feb 12 Coming soon Dallas, TX Immerse Dallas • Feb 12 Learn more Bogota, CO Immerse Bogota, Colombia • Feb 19 Coming soon New York, NY NASTD East-West • Mar 2 - Mar 5 Coming soon Washington, DC Billington State & Local • Mar 9 - Mar 11 Coming soon Mexico City, MX Immerse CDMX, Mexico • Mar 12 Coming soon San Jose, CA NVIDIA GTC • Mar 16 - Mar 17 Coming soon San Francisco, CA RSAC • Mar 23 - Mar 24 Coming soon Houston, TX Immerse Houston • Apr 2 Coming soon New York, NY Immerse New York • Apr 14 Coming soon São Paulo, BR Immerse Sao Paulo, Brazil • Apr 15 Coming soon Boston, MA Immerse Boston • Apr 16 Coming soon Montreal, CA Immerse Montreal • Apr 22 Coming soon Las Vegas, NV Google Cloud Next • Apr 22 - Apr 23 Coming soon Minneapolis, MN Immerse Minneapolis • Apr 23 Coming soon Philadelphia, PA NASCIO Midyear • Apr 28 - May 1 Coming soon Buenos Aires, AR Immerse Buenos Aires, Argentina • May Coming soon Kansas City, MO NLIT • May 4 - May 6 Coming soon Anaheim, CA Immerse Anaheim/SoCal • May 6 Coming soon Tampa, FL SOF Week • May 18 - May 21 Coming soon Toronto, CA Immerse Toronto • May 20 Coming soon Chicago, IL Immerse Chicago • May 28 Coming soon National Harbor, MD Gartner Security & Risk Management Summit (USA) • Jun 1 - Jun 2 Coming soon Baltimore, MD TechNet Cyber • Jun 2 - Jun 4 Coming soon Austin, TX NASTD Midwest-South • Jun 8 - Jun 11 Coming soon Vancouver, CA Immerse Vancouver • Jun 10 Coming soon Seattle, WA Immerse Seattle • Jun 18 Coming soon Las Vegas, NV Black Hat USA • Aug 3 - Aug 6 Coming soon Denver, CO NASTD Annual • Aug 23 - Aug 26 Coming soon Las Vegas, NV Crowdstrike fal.con • Aug 31 - Sept 1 Coming soon San Diego, CA NASCIO Annual • Sept 27 - Sept 30 Coming soon Denver, CO EDUCAUSE Annual • Sept 29 - Oct 2 Coming soon Santiago, CL Immerse Santiago, Chile • Oct Coming soon San Francisco, CA Cloudflare Global Connect 2026 • Oct 19 - Oct 20 Coming soon Orlando, FL Gartner IT Symposium • Oct 19 - Oct 20 Coming soon Atlanta, GA Immerse Atlanta • Nov 12 Coming soon Las Vegas, NV AWS re:Invent • Nov 30 - Dec 4 Coming soon PRIMEROS PASOS Planes gratuitos Planes para pequeñas empresas Para empresas Sugerencias Solicitar demostración Contacta con Ventas SOLUCIONES Conectividad cloud Servicios de aplicación SASE y seguridad del espacio de trabajo Servicios de red Plataforma para desarrolladores SOPORTE Centro de ayuda Atención al cliente Foro de la comunidad Discord para desarrolladores ¿Has perdido el acceso a tu cuenta? Estado de Cloudflare CUMPLIMIENTO NORMATIVO Recursos de conformidad Confianza GDPR IA responsable Informe de transparencia Notificar abuso INTERÉS PÚBLICO Proyecto Galileo Proyecto Athenian Cloudflare para campañas Proyecto Fairshot EMPRESA Acerca de Cloudflare Mapa de red Nuestro equipo Logotipos y dossier de prensa Diversidad, equidad e inclusión Impact/ESG © 2026 Cloudflare, Inc. Política de privacidad Términos de uso Informar sobre problemas de seguridad Confianza y seguridad Preferencias de cookies Marca comercial | 2026-01-13T09:29:33 |
https://cn.chinadaily.com.cn/gtx/5d63917ba31099ab995dbb29/hepingli | 和评理 - 中国日报网 China Daily Homepage 中文网首页 时评 资讯 C财经 生活 视频 专栏 双语 --> 原创 观天下 地方 --> 登录 注册 观天下 移动新媒体 站内搜索 站内搜索 观天下 China Daily Homepage 中文网首页 时评 资讯 C财经 生活 视频 专栏 双语 --> 漫画 原创 观天下 地方 和评理 和评理 和评理｜有序扩大金融对外开放：为国内经济提供动力，为国际合作搭建桥梁 7 个月 前 和评理 | 美国增兵中东加剧紧张 对话协商方是正道 7 个月 前 和评理 | 阿斯塔纳峰会将为构建更加紧密的中国－中亚命运共同体注入新动力 7 个月 前 和评理 | 北约抹黑中国 意在染指亚太 7 个月 前 和评理｜从“蓝图愿景”到“落地生根” 中非合作论坛结出累累硕果 7 个月 前 和评理｜解决贸易争端，还需美国回归理性 7 个月 前 和评理｜中国稀土行业规范、有序、可持续发展，终将惠及全球 7 个月 前 和评理｜平等、尊重、互利，仍是中美关系走向的关键 7 个月 前 和评理｜用对话沟通妥处中欧经贸分歧：站在历史正确的一边，向新而行 7 个月 前 和评理 | 加强建设性对话 推动中美经贸关系健康发展 7 个月 前 和评理 | 排除各种干扰破坏 校正中美关系航向 7 个月 前 和评理 | 平等尊重是中美交往前提，对话合作是唯一正确选择 7 个月 前 和评理｜单边关税，注定让美国“无尽胜利”的梦想变幻想 7 个月 前 和评理｜严格落实日内瓦经贸会谈共识，切实维护中方权益 7 个月 前 和评理 | 部署武器煽风点火制造紧张 美国将亚太变成“火药桶” 7 个月 前 1 2 3 4 5 6 7 8 9 10 Next >>| 1/40 Next 热点 美联储风波叠加地缘政治不确定性 黄金白银期价再创新高 大型撞击造成月幔“蒸发”？嫦娥六号样品又有新发现 八部门发文助力培育养老服务经营主体 国际金价去年涨幅约70%金价持续上涨如何看 扩大内需 统一大市场建设 优化营商环境： 多地敲定今年发展改革工作重点 美国青年看“窑洞之问” CES现场观察 中美企业海外合作共赢 AdSame ShowCode: 新版中文1227 / 观天下频道首页19.7.17 / C1 Begin AdSame ShowCode: 新版中文1227 / 观天下频道首页19.7.17 / C1 End --> AdSame ShowCode: 新版中文1227 / 观天下频道首页19.7.17 / C2 Begin AdSame ShowCode: 新版中文1227 / 观天下频道首页19.7.17 / C2 End --> AdSame ShowCode: 新版中文1227 / 观天下频道首页19.7.17 / C3 Begin AdSame ShowCode: 新版中文1227 / 观天下频道首页19.7.17 / C3 End --> 为你推荐 换一批 神奇的中国 海外手记 和评理 中国那些事儿 世界说 中国观察 新华社 中国日报网评 侨一瞧 事事关心 每日一词 中国经济网 中国新闻网 环球时报 中央电视台 中央人民广播电台 解放军报 中国新闻周刊 人民日报海外版 中国青年网 经济日报 光明日报 中国军网 求是 中国侨网 消费日报网 中国警察网 参考消息网 中国搜索 海外网 法制网 环球网 中青在线 中工网 中国西藏网 中国台湾网 央广网 光明网 人民网 国际在线 中国网 未来网 每日一词 一财网 新华网 更多 美国贸易霸凌行径正在殃及全球 金沙滩 | 中美经贸摩擦的这些问题你真的清楚吗？（之六）——关于“制造业回流 连遮羞布都不要了！日本将恢复中断30余年的商业捕鲸活动 --> 关于我们 | 联系我们 首页 时评 资讯 财经 生活 视频 专栏 漫画 独家 招聘 地方频道： 北京 天津 河北 山西 辽宁 吉林 黑龙江 上海 江苏 浙江 福建 江西 山东 河南 湖北 湖南 广东 广西 海南 重庆 四川 贵州 云南 西藏 陕西 新疆 深圳 友情链接： 人民网 新华网 中国网 国际在线 央视网 中国青年网 中国经济网 中国台湾网 中国西藏网 央广网 光明网 中国军网 中国新闻网 人民政协网 法治网 网上有害信息举报专区 防范网络诈骗 --> 违法和不良信息举报 互联网新闻信息服务许可证10120170006 信息网络传播视听节目许可证0108263号 京公网安备11010502032503号 京网文[2011]0283-097号 京ICP备13028878号-6 12300电信用户申诉受理中心 12318全国文化市场举报 网站网络110报警网站 --> 中国日报网版权说明：凡注明来源为“中国日报网：XXX（署名）”，除与中国日报网签署内容授权协议的网站外，其他任何网站或单位未经允许禁止转载、使用，违者必究。如需使用，请与010-84883777联系；凡本网注明“来源：XXX（非中国日报网）”的作品，均转载自其它媒体，目的在于传播更多信息，其他媒体如需转载，请与稿件来源方联系，如产生任何问题与本网无关。 版权保护：本网登载的内容（包括文字、图片、多媒体资讯等）版权属中国日报网（中报国际文化传媒（北京）有限公司）独家所有使用。 未经中国日报网事先协议授权，禁止转载使用。给中国日报网提意见：rx@chinadaily.com.cn 首页 时评 资讯 财经 文化 漫画 视频 地方 中文 | English 中国日报版权所有 Content@chinadaily.com.cn | 2026-01-13T09:29:33 |
https://gitstar-ranking.com/fossasia | fossasia - Gitstar Ranking Gitstar Ranking Users Organizations Repositories Rankings Users Organizations Repositories Sign in with GitHub fossasia Star 364781 Rank 20 Go to GitHub Fetched on 2026/01/09 06:52 262 Repositories visdom 10209 open-event-server 2999 phimpme-android 2596 susi_server 2524 susi_android 2448 open-event-frontend 2353 pslab-app 2091 susi.ai 2072 open-event-droidgen 2069 open-event-wsgen 2028 open-event-attendee-android 1972 badgemagic-app 1971 star-me 1929 susi_iOS 1902 fossasia.org 1901 loklak_search 1840 badgeyay 1804 open-event-organizer-android 1802 meilix 1785 pslab-desktop 1774 susper.com 1747 open-event 1726 neurolab-android 1718 labs.fossasia.org 1687 query-server 1678 pslab-hardware 1676 gci16.fossasia.org 1663 pslab-python 1644 codeheat.org 1641 pslab-scripts 1618 flappy-svg 1616 susi_linux 1615 gci15.fossasia.org 1612 gci17.fossasia.org 1606 fossasia-communities 1594 2018.fossasia.org 1589 2017.fossasia.org 1589 susi_skill_cms 1585 knittingpattern 1583 gci14.fossasia.org 1583 open-event-attendee-ios 1581 pslab-firmware 1575 2012.fossasia.org 1575 2016.fossasia.org 1574 loklak_webclient 1568 eventyay 1568 loklak_wok_android 1567 badgemagic-firmware 1567 neurolab-hardware 1561 directory.api.fossasia.net 1560 1 2 3 4 5 … › Released by @k0kubun in December 2014. Fork me on GitHub . | 2026-01-13T09:29:33 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3ArepeatableProperty | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:33 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3AeditableComboBox | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:33 |
http://groovy-lang.org/syntax.html#_underscore_in_literals | The Apache Groovy programming language - Syntax Socialize Discuss on the mailing-list Groovy on X Groovy on Bluesky Groovy on Mastodon Groovy on LinkedIn Events and conferences Source code on GitHub Report issues in Jira Stack Overflow questions Slack Community You are using an outdated browser. Please upgrade your browser to improve your experience. Apache Groovy™ Learn Documentation Download Support Contribute Ecosystem Blog posts Socialize Table of contents 1. Comments 1.1. Single-line comment 1.2. Multiline comment 1.3. Groovydoc comment 1.4. Shebang line 2. Keywords 3. Identifiers 3.1. Normal identifiers 3.2. Quoted identifiers 4. Strings 4.1. Single-quoted string 4.2. String concatenation 4.3. Triple-single-quoted string 4.3.1. Escaping special characters 4.3.2. Unicode escape sequence 4.4. Double-quoted string 4.4.1. String interpolation 4.4.2. Special case of interpolating closure expressions 4.4.3. Interoperability with Java 4.4.4. GString and String hashCodes 4.5. Triple-double-quoted string 4.6. Slashy string 4.6.1. Special cases 4.7. Dollar slashy string 4.8. String summary table 4.9. Characters 5. Numbers 5.1. Integral literals 5.1.1. Alternative non-base 10 representations Binary literal Octal literal Hexadecimal literal 5.2. Decimal literals 5.3. Underscore in literals 5.4. Number type suffixes 5.5. Math operations 5.5.1. The case of the division operator 5.5.2. The case of the power operator 6. Booleans 7. Lists 8. Arrays 8.1. Java-style array initialization 9. Maps Syntax This chapter covers the syntax of the Groovy programming language. The grammar of the language derives from the Java grammar, but enhances it with specific constructs for Groovy, and allows certain simplifications. 1. Comments 1.1. Single-line comment Single-line comments start with // and can be found at any position in the line. The characters following // , until the end of the line, are considered part of the comment. // a standalone single line comment println "hello" // a comment till the end of the line 1.2. Multiline comment A multiline comment starts with /* and can be found at any position in the line. The characters following /* will be considered part of the comment, including new line characters, up to the first */ closing the comment. Multiline comments can thus be put at the end of a statement, or even inside a statement. /* a standalone multiline comment spanning two lines */ println "hello" /* a multiline comment starting at the end of a statement */ println 1 /* one */ + 2 /* two */ 1.3. Groovydoc comment Similarly to multiline comments, Groovydoc comments are multiline, but start with /** and end with */ . Lines following the first Groovydoc comment line can optionally start with a star * . Those comments are associated with: type definitions (classes, interfaces, enums, annotations), fields and properties definitions methods definitions Although the compiler will not complain about Groovydoc comments not being associated with the above language elements, you should prepend those constructs with the comment right before it. /** * A Class description */ class Person { /** the name of the person */ String name /** * Creates a greeting method for a certain person. * * @param otherPerson the person to greet * @return a greeting message */ String greet(String otherPerson) { "Hello ${otherPerson}" } } Groovydoc follows the same conventions as Java’s own Javadoc. So you’ll be able to use the same tags as with Javadoc. In addition, Groovy supports Runtime Groovydoc since 3.0.0, i.e. Groovydoc can be retained at runtime. Runtime Groovydoc is disabled by default. It can be enabled by adding JVM option -Dgroovy.attach.runtime.groovydoc=true The Runtime Groovydoc starts with /**@ and ends with */ , for example: /**@ * Some class groovydoc for Foo */ class Foo { /**@ * Some method groovydoc for bar */ void bar() { } } assert Foo.class.groovydoc.content.contains('Some class groovydoc for Foo') (1) assert Foo.class.getMethod('bar', new Class[0]).groovydoc.content.contains('Some method groovydoc for bar') (2) 1 Get the runtime groovydoc for class Foo 2 Get the runtime groovydoc for method bar 1.4. Shebang line Beside the single-line comment, there is a special line comment, often called the shebang line understood by UNIX systems which allows scripts to be run directly from the command-line, provided you have installed the Groovy distribution and the groovy command is available on the PATH . #!/usr/bin/env groovy println "Hello from the shebang line" The # character must be the first character of the file. Any indentation would yield a compilation error. 2. Keywords Groovy has the following reserved keywords: Table 1. Reserved Keywords abstract assert break case catch class const continue def default do else enum extends final finally for goto if implements import instanceof interface native new null non-sealed package public protected private return static strictfp super switch synchronized this threadsafe throw throws transient try while Of these, const , goto , strictfp , and threadsafe are not currently in use. The reserved keywords can’t in general be used for variable, field and method names. A trick allows methods to be defined having the same name as a keyword by surrounding the name in quotes as shown in the following example: // reserved keywords can be used for method names if quoted def "abstract"() { true } // when calling such methods, the name must be qualified using "this." this.abstract() Using such names might be confusing and is often best to avoid. The trick is primarily intended to enable certain Java integration scenarios and certain DSL scenarios where having "verbs" and "nouns" with the same name as keywords may be desirable. In addition, Groovy has the following contextual keywords: Table 2. Contextual Keywords as in permits record sealed trait var yields These words are only keywords in certain contexts and can be more freely used in some places, in particular for variables, fields and method names. This extra lenience allows using method or variable names that were not keywords in earlier versions of Groovy or are not keywords in Java. Examples are shown here: // contextual keywords can be used for field and variable names def as = true assert as // contextual keywords can be used for method names def in() { true } // when calling such methods, the name only needs to be qualified using "this." in scenarios which would be ambiguous this.in() Groovy programmers familiar with these contextual keywords may still wish to avoid using those names unless there is a good reason to use such a name. The restrictions on reserved keywords also apply for the primitive types, the boolean literals and the null literal (all of which are discussed later): Table 3. Other reserved words null true false boolean char byte short int long float double While not recommended, the same trick as for reserved keywords can be used: def "null"() { true } // not recommended; potentially confusing assert this.null() // must be qualified Using such words as method names is potentially confusing and is often best to avoid, however, it might be useful for certain kinds of DSLs . 3. Identifiers 3.1. Normal identifiers Identifiers start with a letter, a dollar or an underscore. They cannot start with a number. A letter can be in the following ranges: 'a' to 'z' (lowercase ascii letter) 'A' to 'Z' (uppercase ascii letter) '\u00C0' to '\u00D6' '\u00D8' to '\u00F6' '\u00F8' to '\u00FF' '\u0100' to '\uFFFE' Then following characters can contain letters and numbers. Here are a few examples of valid identifiers (here, variable names): def name def item3 def with_underscore def $dollarStart But the following ones are invalid identifiers: def 3tier def a+b def a#b All keywords are also valid identifiers when following a dot: foo.as foo.assert foo.break foo.case foo.catch 3.2. Quoted identifiers Quoted identifiers appear after the dot of a dotted expression. For instance, the name part of the person.name expression can be quoted with person."name" or person.'name' . This is particularly interesting when certain identifiers contain illegal characters that are forbidden by the Java Language Specification, but which are allowed by Groovy when quoted. For example, characters like a dash, a space, an exclamation mark, etc. def map = [:] map."an identifier with a space and double quotes" = "ALLOWED" map.'with-dash-signs-and-single-quotes' = "ALLOWED" assert map."an identifier with a space and double quotes" == "ALLOWED" assert map.'with-dash-signs-and-single-quotes' == "ALLOWED" As we shall see in the following section on strings , Groovy provides different string literals. All kind of strings are actually allowed after the dot: map.'single quote' map."double quote" map.'''triple single quote''' map."""triple double quote""" map./slashy string/ map.$/dollar slashy string/$ There’s a difference between plain character strings and Groovy’s GStrings (interpolated strings), as in that the latter case, the interpolated values are inserted in the final string for evaluating the whole identifier: def firstname = "Homer" map."Simpson-${firstname}" = "Homer Simpson" assert map.'Simpson-Homer' == "Homer Simpson" 4. Strings Text literals are represented in the form of chain of characters called strings. Groovy lets you instantiate java.lang.String objects, as well as GStrings ( groovy.lang.GString ) which are also called interpolated strings in other programming languages. 4.1. Single-quoted string Single-quoted strings are a series of characters surrounded by single quotes: 'a single-quoted string' Single-quoted strings are plain java.lang.String and don’t support interpolation. 4.2. String concatenation All the Groovy strings can be concatenated with the + operator: assert 'ab' == 'a' + 'b' 4.3. Triple-single-quoted string Triple-single-quoted strings are a series of characters surrounded by triplets of single quotes: '''a triple-single-quoted string''' Triple-single-quoted strings are plain java.lang.String and don’t support interpolation. Triple-single-quoted strings may span multiple lines. The content of the string can cross line boundaries without the need to split the string in several pieces and without concatenation or newline escape characters: def aMultilineString = '''line one line two line three''' If your code is indented, for example in the body of the method of a class, your string will contain the whitespace of the indentation. The Groovy Development Kit contains methods for stripping out the indentation with the String#stripIndent() method, and with the String#stripMargin() method that takes a delimiter character to identify the text to remove from the beginning of a string. When creating a string as follows: def startingAndEndingWithANewline = ''' line one line two line three ''' You will notice that the resulting string contains a newline character as first character. It is possible to strip that character by escaping the newline with a backslash: def strippedFirstNewline = '''\ line one line two line three ''' assert !strippedFirstNewline.startsWith('\n') 4.3.1. Escaping special characters You can escape single quotes with the backslash character to avoid terminating the string literal: 'an escaped single quote: \' needs a backslash' And you can escape the escape character itself with a double backslash: 'an escaped escape character: \\ needs a double backslash' Some special characters also use the backslash as escape character: Escape sequence Character \b backspace \f formfeed \n newline \r carriage return \s single space \t tabulation \\ backslash \' single quote within a single-quoted string (and optional for triple-single-quoted and double-quoted strings) \" double quote within a double-quoted string (and optional for triple-double-quoted and single-quoted strings) We’ll see some more escaping details when it comes to other types of strings discussed later. 4.3.2. Unicode escape sequence For characters that are not present on your keyboard, you can use unicode escape sequences: a backslash, followed by 'u', then 4 hexadecimal digits. For example, the Euro currency symbol can be represented with: 'The Euro currency symbol: \u20AC' 4.4. Double-quoted string Double-quoted strings are a series of characters surrounded by double quotes: "a double-quoted string" Double-quoted strings are plain java.lang.String if there’s no interpolated expression, but are groovy.lang.GString instances if interpolation is present. To escape a double quote, you can use the backslash character: "A double quote: \"". 4.4.1. String interpolation Any Groovy expression can be interpolated in all string literals, apart from single and triple-single-quoted strings. Interpolation is the act of replacing a placeholder in the string with its value upon evaluation of the string. The placeholder expressions are surrounded by ${} . The curly braces may be omitted for unambiguous dotted expressions, i.e. we can use just a $ prefix in those cases. If the GString is ever passed to a method taking a String, the expression value inside the placeholder is evaluated to its string representation (by calling toString() on that expression) and the resulting String is passed to the method. Here, we have a string with a placeholder referencing a local variable: def name = 'Guillaume' // a plain string def greeting = "Hello ${name}" assert greeting.toString() == 'Hello Guillaume' Any Groovy expression is valid, as we can see in this example with an arithmetic expression: def sum = "The sum of 2 and 3 equals ${2 + 3}" assert sum.toString() == 'The sum of 2 and 3 equals 5' Not only are expressions allowed in between the ${} placeholder, but so are statements. However, a statement’s value is just null . So if several statements are inserted in that placeholder, the last one should somehow return a meaningful value to be inserted. For instance, "The sum of 1 and 2 is equal to ${def a = 1; def b = 2; a + b}" is supported and works as expected but a good practice is usually to stick to simple expressions inside GString placeholders. In addition to ${} placeholders, we can also use a lone $ sign prefixing a dotted expression: def person = [name: 'Guillaume', age: 36] assert "$person.name is $person.age years old" == 'Guillaume is 36 years old' But only dotted expressions of the form a.b , a.b.c , etc, are valid. Expressions containing parentheses like method calls, curly braces for closures, dots which aren’t part of a property expression or arithmetic operators would be invalid. Given the following variable definition of a number: def number = 3.14 The following statement will throw a groovy.lang.MissingPropertyException because Groovy believes you’re trying to access the toString property of that number, which doesn’t exist: shouldFail(MissingPropertyException) { println "$number.toString()" } You can think of "$number.toString()" as being interpreted by the parser as "${number.toString}()" . Similarly, if the expression is ambiguous, you need to keep the curly braces: String thing = 'treasure' assert 'The x-coordinate of the treasure is represented by treasure.x' == "The x-coordinate of the $thing is represented by $thing.x" // <= Not allowed: ambiguous!! assert 'The x-coordinate of the treasure is represented by treasure.x' == "The x-coordinate of the $thing is represented by ${thing}.x" // <= Curly braces required If you need to escape the $ or ${} placeholders in a GString so they appear as is without interpolation, you just need to use a \ backslash character to escape the dollar sign: assert '$5' == "\$5" assert '${name}' == "\${name}" 4.4.2. Special case of interpolating closure expressions So far, we’ve seen we could interpolate arbitrary expressions inside the ${} placeholder, but there is a special case and notation for closure expressions. When the placeholder contains an arrow, ${→} , the expression is actually a closure expression — you can think of it as a closure with a dollar prepended in front of it: def sParameterLessClosure = "1 + 2 == ${-> 3}" (1) assert sParameterLessClosure == '1 + 2 == 3' def sOneParamClosure = "1 + 2 == ${ w -> w << 3}" (2) assert sOneParamClosure == '1 + 2 == 3' 1 The closure is a parameterless closure which doesn’t take arguments. 2 Here, the closure takes a single java.io.StringWriter argument, to which you can append content with the << leftShift operator. In either case, both placeholders are embedded closures. In appearance, it looks like a more verbose way of defining expressions to be interpolated, but closures have an interesting advantage over mere expressions: lazy evaluation. Let’s consider the following sample: def number = 1 (1) def eagerGString = "value == ${number}" def lazyGString = "value == ${ -> number }" assert eagerGString == "value == 1" (2) assert lazyGString == "value == 1" (3) number = 2 (4) assert eagerGString == "value == 1" (5) assert lazyGString == "value == 2" (6) 1 We define a number variable containing 1 that we then interpolate within two GStrings, as an expression in eagerGString and as a closure in lazyGString . 2 We expect the resulting string to contain the same string value of 1 for eagerGString . 3 Similarly for lazyGString 4 Then we change the value of the variable to a new number 5 With a plain interpolated expression, the value was actually bound at the time of creation of the GString. 6 But with a closure expression, the closure is called upon each coercion of the GString into String, resulting in an updated string containing the new number value. An embedded closure expression taking more than one parameter will generate an exception at runtime. Only closures with zero or one parameter are allowed. 4.4.3. Interoperability with Java When a method (whether implemented in Java or Groovy) expects a java.lang.String , but we pass a groovy.lang.GString instance, the toString() method of the GString is automatically and transparently called. String takeString(String message) { (4) assert message instanceof String (5) return message } def message = "The message is ${'hello'}" (1) assert message instanceof GString (2) def result = takeString(message) (3) assert result instanceof String assert result == 'The message is hello' 1 We create a GString variable 2 We double-check it’s an instance of the GString 3 We then pass that GString to a method taking a String as parameter 4 The signature of the takeString() method explicitly says its sole parameter is a String 5 We also verify that the parameter is indeed a String and not a GString. 4.4.4. GString and String hashCodes Although interpolated strings can be used in lieu of plain Java strings, they differ with strings in a particular way: their hashCodes are different. Plain Java strings are immutable, whereas the resulting String representation of a GString can vary, depending on its interpolated values. Even for the same resulting string, GStrings and Strings don’t have the same hashCode. assert "one: ${1}".hashCode() != "one: 1".hashCode() GString and Strings having different hashCode values, using GString as Map keys should be avoided, especially if we try to retrieve an associated value with a String instead of a GString. def key = "a" def m = ["${key}": "letter ${key}"] (1) assert m["a"] == null (2) 1 The map is created with an initial pair whose key is a GString 2 When we try to fetch the value with a String key, we will not find it, as Strings and GString have different hashCode values 4.5. Triple-double-quoted string Triple-double-quoted strings behave like double-quoted strings, with the addition that they are multiline, like the triple-single-quoted strings. def name = 'Groovy' def template = """ Dear Mr ${name}, You're the winner of the lottery! Yours sincerly, Dave """ assert template.toString().contains('Groovy') Neither double quotes nor single quotes need be escaped in triple-double-quoted strings. 4.6. Slashy string Beyond the usual quoted strings, Groovy offers slashy strings, which use / as the opening and closing delimiter. Slashy strings are particularly useful for defining regular expressions and patterns, as there is no need to escape backslashes. Example of a slashy string: def fooPattern = /.*foo.*/ assert fooPattern == '.*foo.*' Only forward slashes need to be escaped with a backslash: def escapeSlash = /The character \/ is a forward slash/ assert escapeSlash == 'The character / is a forward slash' Slashy strings are multiline: def multilineSlashy = /one two three/ assert multilineSlashy.contains('\n') Slashy strings can be thought of as just another way to define a GString but with different escaping rules. They hence support interpolation: def color = 'blue' def interpolatedSlashy = /a ${color} car/ assert interpolatedSlashy == 'a blue car' 4.6.1. Special cases An empty slashy string cannot be represented with a double forward slash, as it’s understood by the Groovy parser as a line comment. That’s why the following assert would actually not compile as it would look like a non-terminated statement: assert '' == // As slashy strings were mostly designed to make regexp easier so a few things that are errors in GStrings like $() or $5 will work with slashy strings. Remember that escaping backslashes is not required. An alternative way of thinking of this is that in fact escaping is not supported. The slashy string /\t/ won’t contain a tab but instead a backslash followed by the character 't'. Escaping is only allowed for the slash character, i.e. /\/folder/ will be a slashy string containing '/folder' . A consequence of slash escaping is that a slashy string can’t end with a backslash. Otherwise that will escape the slashy string terminator. You can instead use a special trick, /ends with slash ${'\\'}/ . But best just avoid using a slashy string in such a case. 4.7. Dollar slashy string Dollar slashy strings are multiline GStrings delimited with an opening $/ and a closing /$ . The escaping character is the dollar sign, and it can escape another dollar, or a forward slash. Escaping for the dollar and forward slash characters is only needed where conflicts arise with the special use of those characters. The characters $foo would normally indicate a GString placeholder, so those four characters can be entered into a dollar slashy string by escaping the dollar, i.e. $$foo . Similarly, you will need to escape a dollar slashy closing delimiter if you want it to appear in your string. Here are a few examples: def name = "Guillaume" def date = "April, 1st" def dollarSlashy = $/ Hello $name, today we're ${date}. $ dollar sign $$ escaped dollar sign \ backslash / forward slash $/ escaped forward slash $$$/ escaped opening dollar slashy $/$$ escaped closing dollar slashy /$ assert [ 'Guillaume', 'April, 1st', '$ dollar sign', '$ escaped dollar sign', '\\ backslash', '/ forward slash', '/ escaped forward slash', '$/ escaped opening dollar slashy', '/$ escaped closing dollar slashy' ].every { dollarSlashy.contains(it) } It was created to overcome some of the limitations of the slashy string escaping rules. Use it when its escaping rules suit your string contents (typically if it has some slashes you don’t want to escape). 4.8. String summary table String name String syntax Interpolated Multiline Escape character Single-quoted '…​' \ Triple-single-quoted '''…​''' \ Double-quoted "…​" \ Triple-double-quoted """…​""" \ Slashy /…​/ \ Dollar slashy $/…​/$ $ 4.9. Characters Unlike Java, Groovy doesn’t have an explicit character literal. However, you can be explicit about making a Groovy string an actual character, by three different means: char c1 = 'A' (1) assert c1 instanceof Character def c2 = 'B' as char (2) assert c2 instanceof Character def c3 = (char)'C' (3) assert c3 instanceof Character 1 by being explicit when declaring a variable holding the character by specifying the char type 2 by using type coercion with the as operator 3 by using a cast to char operation The first option 1 is interesting when the character is held in a variable, while the other two ( 2 and 3 ) are more interesting when a char value must be passed as argument of a method call. 5. Numbers Groovy supports different kinds of integral literals and decimal literals, backed by the usual Number types of Java. 5.1. Integral literals The integral literal types are the same as in Java: byte char short int long java.math.BigInteger You can create integral numbers of those types with the following declarations: // primitive types byte b = 1 char c = 2 short s = 3 int i = 4 long l = 5 // infinite precision BigInteger bi = 6 If you use optional typing by using the def keyword, the type of the integral number will vary: it’ll adapt to the capacity of the type that can hold that number. For positive numbers: def a = 1 assert a instanceof Integer // Integer.MAX_VALUE def b = 2147483647 assert b instanceof Integer // Integer.MAX_VALUE + 1 def c = 2147483648 assert c instanceof Long // Long.MAX_VALUE def d = 9223372036854775807 assert d instanceof Long // Long.MAX_VALUE + 1 def e = 9223372036854775808 assert e instanceof BigInteger As well as for negative numbers: def na = -1 assert na instanceof Integer // Integer.MIN_VALUE def nb = -2147483648 assert nb instanceof Integer // Integer.MIN_VALUE - 1 def nc = -2147483649 assert nc instanceof Long // Long.MIN_VALUE def nd = -9223372036854775808 assert nd instanceof Long // Long.MIN_VALUE - 1 def ne = -9223372036854775809 assert ne instanceof BigInteger 5.1.1. Alternative non-base 10 representations Numbers can also be represented in binary, octal, hexadecimal and decimal bases. Binary literal Binary numbers start with a 0b prefix: int xInt = 0b10101111 assert xInt == 175 short xShort = 0b11001001 assert xShort == 201 as short byte xByte = 0b11 assert xByte == 3 as byte long xLong = 0b101101101101 assert xLong == 2925l BigInteger xBigInteger = 0b111100100001 assert xBigInteger == 3873g int xNegativeInt = -0b10101111 assert xNegativeInt == -175 Octal literal Octal numbers are specified in the typical format of 0 followed by octal digits. int xInt = 077 assert xInt == 63 short xShort = 011 assert xShort == 9 as short byte xByte = 032 assert xByte == 26 as byte long xLong = 0246 assert xLong == 166l BigInteger xBigInteger = 01111 assert xBigInteger == 585g int xNegativeInt = -077 assert xNegativeInt == -63 Hexadecimal literal Hexadecimal numbers are specified in the typical format of 0x followed by hex digits. int xInt = 0x77 assert xInt == 119 short xShort = 0xaa assert xShort == 170 as short byte xByte = 0x3a assert xByte == 58 as byte long xLong = 0xffff assert xLong == 65535l BigInteger xBigInteger = 0xaaaa assert xBigInteger == 43690g Double xDouble = new Double('0x1.0p0') assert xDouble == 1.0d int xNegativeInt = -0x77 assert xNegativeInt == -119 5.2. Decimal literals The decimal literal types are the same as in Java: float double java.math.BigDecimal You can create decimal numbers of those types with the following declarations: // primitive types float f = 1.234 double d = 2.345 // infinite precision BigDecimal bd = 3.456 Decimals can use exponents, with the e or E exponent letter, followed by an optional sign, and an integral number representing the exponent: assert 1e3 == 1_000.0 assert 2E4 == 20_000.0 assert 3e+1 == 30.0 assert 4E-2 == 0.04 assert 5e-1 == 0.5 Conveniently for exact decimal number calculations, Groovy chooses java.math.BigDecimal as its decimal number type. In addition, both float and double are supported, but require an explicit type declaration, type coercion or suffix. Even if BigDecimal is the default for decimal numbers, such literals are accepted in methods or closures taking float or double as parameter types. Decimal numbers can’t be represented using a binary, octal or hexadecimal representation. 5.3. Underscore in literals When writing long literal numbers, it’s harder on the eye to figure out how some numbers are grouped together, for example with groups of thousands, of words, etc. By allowing you to place underscore in number literals, it’s easier to spot those groups: long creditCardNumber = 1234_5678_9012_3456L long socialSecurityNumbers = 999_99_9999L double monetaryAmount = 12_345_132.12 long hexBytes = 0xFF_EC_DE_5E long hexWords = 0xFFEC_DE5E long maxLong = 0x7fff_ffff_ffff_ffffL long alsoMaxLong = 9_223_372_036_854_775_807L long bytes = 0b11010010_01101001_10010100_10010010 5.4. Number type suffixes We can force a number (including binary, octals and hexadecimals) to have a specific type by giving a suffix (see table below), either uppercase or lowercase. Type Suffix BigInteger G or g Long L or l Integer I or i BigDecimal G or g Double D or d Float F or f Examples: assert 42I == Integer.valueOf('42') assert 42i == Integer.valueOf('42') // lowercase i more readable assert 123L == Long.valueOf("123") // uppercase L more readable assert 2147483648 == Long.valueOf('2147483648') // Long type used, value too large for an Integer assert 456G == new BigInteger('456') assert 456g == new BigInteger('456') assert 123.45 == new BigDecimal('123.45') // default BigDecimal type used assert .321 == new BigDecimal('.321') assert 1.200065D == Double.valueOf('1.200065') assert 1.234F == Float.valueOf('1.234') assert 1.23E23D == Double.valueOf('1.23E23') assert 0b1111L.class == Long // binary assert 0xFFi.class == Integer // hexadecimal assert 034G.class == BigInteger // octal 5.5. Math operations Although operators are covered in more detail elsewhere, it’s important to discuss the behavior of math operations and what their resulting types are. Division and power binary operations aside (covered below), binary operations between byte , char , short and int result in int binary operations involving long with byte , char , short and int result in long binary operations involving BigInteger and any other integral type result in BigInteger binary operations involving BigDecimal with byte , char , short , int and BigInteger result in BigDecimal binary operations between float , double and BigDecimal result in double binary operations between two BigDecimal result in BigDecimal The following table summarizes those rules: byte char short int long BigInteger float double BigDecimal byte int int int int long BigInteger double double BigDecimal char int int int long BigInteger double double BigDecimal short int int long BigInteger double double BigDecimal int int long BigInteger double double BigDecimal long long BigInteger double double BigDecimal BigInteger BigInteger double double BigDecimal float double double double double double double BigDecimal BigDecimal Thanks to Groovy’s operator overloading, the usual arithmetic operators work as well with BigInteger and BigDecimal , unlike in Java where you have to use explicit methods for operating on those numbers. 5.5.1. The case of the division operator The division operators / (and /= for division and assignment) produce a double result if either operand is a float or double , and a BigDecimal result otherwise (when both operands are any combination of an integral type short , char , byte , int , long , BigInteger or BigDecimal ). BigDecimal division is performed with the divide() method if the division is exact (i.e. yielding a result that can be represented within the bounds of the same precision and scale), or using a MathContext with a precision of the maximum of the two operands' precision plus an extra precision of 10, and a scale of the maximum of 10 and the maximum of the operands' scale. For integer division like in Java, you should use the intdiv() method, as Groovy doesn’t provide a dedicated integer division operator symbol. 5.5.2. The case of the power operator The power operation is represented by the ** operator, with two parameters: the base and the exponent. The result of the power operation depends on its operands, and the result of the operation (in particular if the result can be represented as an integral value). The following rules are used by Groovy’s power operation to determine the resulting type: If the exponent is a decimal value if the result can be represented as an Integer , then return an Integer else if the result can be represented as a Long , then return a Long otherwise return a Double If the exponent is an integral value if the exponent is strictly negative, then return an Integer , Long or Double if the result value fits in that type if the exponent is positive or zero if the base is a BigDecimal , then return a BigDecimal result value if the base is a BigInteger , then return a BigInteger result value if the base is an Integer , then return an Integer if the result value fits in it, otherwise a BigInteger if the base is a Long , then return a Long if the result value fits in it, otherwise a BigInteger We can illustrate those rules with a few examples: // base and exponent are ints and the result can be represented by an Integer assert 2 ** 3 instanceof Integer // 8 assert 10 ** 9 instanceof Integer // 1_000_000_000 // the base is a long, so fit the result in a Long // (although it could have fit in an Integer) assert 5L ** 2 instanceof Long // 25 // the result can't be represented as an Integer or Long, so return a BigInteger assert 100 ** 10 instanceof BigInteger // 10e20 assert 1234 ** 123 instanceof BigInteger // 170515806212727042875... // the base is a BigDecimal and the exponent a negative int // but the result can be represented as an Integer assert 0.5 ** -2 instanceof Integer // 4 // the base is an int, and the exponent a negative float // but again, the result can be represented as an Integer assert 1 ** -0.3f instanceof Integer // 1 // the base is an int, and the exponent a negative int // but the result will be calculated as a Double // (both base and exponent are actually converted to doubles) assert 10 ** -1 instanceof Double // 0.1 // the base is a BigDecimal, and the exponent is an int, so return a BigDecimal assert 1.2 ** 10 instanceof BigDecimal // 6.1917364224 // the base is a float or double, and the exponent is an int // but the result can only be represented as a Double value assert 3.4f ** 5 instanceof Double // 454.35430372146965 assert 5.6d ** 2 instanceof Double // 31.359999999999996 // the exponent is a decimal value // and the result can only be represented as a Double value assert 7.8 ** 1.9 instanceof Double // 49.542708423868476 assert 2 ** 0.1f instanceof Double // 1.0717734636432956 6. Booleans Boolean is a special data type that is used to represent truth values: true and false . Use this data type for simple flags that track true/false conditions . Boolean values can be stored in variables, assigned into fields, just like any other data type: def myBooleanVariable = true boolean untypedBooleanVar = false booleanField = true true and false are the only two primitive boolean values. But more complex boolean expressions can be represented using logical operators . In addition, Groovy has special rules (often referred to as Groovy Truth ) for coercing non-boolean objects to a boolean value. 7. Lists Groovy uses a comma-separated list of values, surrounded by square brackets, to denote lists. Groovy lists are plain JDK java.util.List , as Groovy doesn’t define its own collection classes. The concrete list implementation used when defining list literals are java.util.ArrayList by default, unless you decide to specify otherwise, as we shall see later on. def numbers = [1, 2, 3] (1) assert numbers instanceof List (2) assert numbers.size() == 3 (3) 1 We define a list numbers delimited by commas and surrounded by square brackets, and we assign that list into a variable 2 The list is an instance of Java’s java.util.List interface 3 The size of the list can be queried with the size() method, and shows our list contains 3 elements In the above example, we used a homogeneous list, but you can also create lists containing values of heterogeneous types: def heterogeneous = [1, "a", true] (1) 1 Our list here contains a number, a string and a boolean value We mentioned that by default, list literals are actually instances of java.util.ArrayList , but it is possible to use a different backing type for our lists, thanks to using type coercion with the as operator, or with explicit type declaration for your variables: def arrayList = [1, 2, 3] assert arrayList instanceof java.util.ArrayList def linkedList = [2, 3, 4] as LinkedList (1) assert linkedList instanceof java.util.LinkedList LinkedList otherLinked = [3, 4, 5] (2) assert otherLinked instanceof java.util.LinkedList 1 We use coercion with the as operator to explicitly request a java.util.LinkedList implementation 2 We can say that the variable holding the list literal is of type java.util.LinkedList You can access elements of the list with the [] subscript operator (both for reading and setting values) with positive indices or negative indices to access elements from the end of the list, as well as with ranges, and use the << leftShift operator to append elements to a list: def letters = ['a', 'b', 'c', 'd'] assert letters[0] == 'a' (1) assert letters[1] == 'b' assert letters[-1] == 'd' (2) assert letters[-2] == 'c' letters[2] = 'C' (3) assert letters[2] == 'C' letters << 'e' (4) assert letters[ 4] == 'e' assert letters[-1] == 'e' assert letters[1, 3] == ['b', 'd'] (5) assert letters[2..4] == ['C', 'd', 'e'] (6) 1 Access the first element of the list (zero-based counting) 2 Access the last element of the list with a negative index: -1 is the first element from the end of the list 3 Use an assignment to set a new value for the third element of the list 4 Use the << leftShift operator to append an element at the end of the list 5 Access two elements at once, returning a new list containing those two elements 6 Use a range to access a range of values from the list, from a start to an end element position As lists can be heterogeneous in nature, lists can also contain other lists to create multidimensional lists: def multi = [[0, 1], [2, 3]] (1) assert multi[1][0] == 2 (2) 1 Define a list of numbers 2 Access the second element of the top-most list, and the first element of the inner list 8. Arrays Groovy reuses the list notation for arrays, but to make such literals arrays, you need to explicitly define the type of the array through coercion or type declaration. String[] arrStr = ['Ananas', 'Banana', 'Kiwi'] (1) assert arrStr instanceof String[] (2) assert !(arrStr instanceof List) def numArr = [1, 2, 3] as int[] (3) assert numArr instanceof int[] (4) assert numArr.size() == 3 1 Define an array of strings using explicit variable type declaration 2 Assert that we created an array of strings 3 Create an array of ints with the as operator 4 Assert that we created an array of primitive ints You can also create multi-dimensional arrays: def matrix3 = new Integer[3][3] (1) assert matrix3.size() == 3 Integer[][] matrix2 (2) matrix2 = [[1, 2], [3, 4]] assert matrix2 instanceof Integer[][] 1 You can define the bounds of a new array 2 Or declare an array without specifying its bounds Access to elements of an array follows the same notation as for lists: String[] names = ['Cédric', 'Guillaume', 'Jochen', 'Paul'] assert names[0] == 'Cédric' (1) names[2] = 'Blackdrag' (2) assert names[2] == 'Blackdrag' 1 Retrieve the first element of the array 2 Set the value of the third element of the array to a new value 8.1. Java-style array initialization Groovy has always supported literal list/array definitions using square brackets and has avoided Java-style curly braces so as not to conflict with closure definitions. In the case where the curly braces come immediately after an array type declaration however, there is no ambiguity with closure definitions, so Groovy 3 and above support that variant of the Java array initialization expression. Examples: def primes = new int[] {2, 3, 5, 7, 11} assert primes.size() == 5 && primes.sum() == 28 assert primes.class.name == '[I' def pets = new String[] {'cat', 'dog'} assert pets.size() == 2 && pets.sum() == 'catdog' assert pets.class.name == '[Ljava.lang.String;' // traditional Groovy alternative still supported String[] groovyBooks = [ 'Groovy in Action', 'Making Java Groovy' ] assert groovyBooks.every{ it.contains('Groovy') } 9. Maps Sometimes called dictionaries or associative arrays in other languages, Groovy features maps. Maps associate keys to values, separating keys and values with colons, and each key/value pairs with commas, and the whole keys and values surrounded by square brackets. def colors = [red: '#FF0000', green: '#00FF00', blue: '#0000FF'] (1) assert colors['red'] == '#FF0000' (2) assert colors.green == '#00FF00' (3) colors['pink'] = '#FF00FF' (4) colors.yellow = '#FFFF00' (5) assert colors.pink == '#FF00FF' assert colors['yellow'] == '#FFFF00' assert colors instanceof java.util.LinkedHashMap 1 We define a map of string color names, associated with their hexadecimal-coded html colors 2 We use the subscript notation to check the content associated with the red key 3 We can also use the property notation to assert the color green’s hexadecimal representation 4 Similarly, we can use the subscript notation to add a new key/value pair 5 Or the property notation, to add the yellow color When using names for the keys, we actually define string keys in the map. Groovy creates maps that are actually instances of java.util.LinkedHashMap . If you try to access a key which is not present in the map: assert colors.unknown == null def emptyMap = [:] assert emptyMap.anyKey == null You will retrieve a null result. In the examples above, we used string keys, but you can also use values of other types as keys: def numbers = [1: 'one', 2: 'two'] assert numbers[1] == 'one' Here, we used numbers as keys, as numbers can unambiguously be recognized as numbers, so Groovy will not create a string key like in our previous examples. But consider the case you want to pass a variable in lieu of the key, to have the value of that variable become the key: def key = 'name' def person = [key: 'Guillaume'] (1) assert !person.containsKey('name') (2) assert person.containsKey('key') (3) 1 The key associated with the 'Guillaume' name will actually be the "key" string, not the value associated with the key variable 2 The map doesn’t contain the 'name' key 3 Instead, the map contains a 'key' key You can also pass quoted strings as well as keys: ["name": "Guillaume"]. This is mandatory if your key string isn’t a valid identifier, for example if you wanted to create a string key containing a dash like in: ["street-name": "Main street"]. When you need to pass variable values as keys in your map definitions, you must surround the variable or expression with parentheses: person = [(key): 'Guillaume'] (1) assert person.containsKey('name') (2) assert !person.containsKey('key') (3) 1 This time, we surround the key variable with parentheses, to instruct the parser we are passing a variable rather than defining a string key 2 The map does contain the name key 3 But the map doesn’t contain the key key as before Groovy Learn Documentation Download Support Contribute Ecosystem Blog posts About Source code Security Books Thanks Sponsorship FAQ Search Socialize Discuss on the mailing-list Groovy on X Groovy on Bluesky Groovy on Mastodon Groovy on LinkedIn Events and conferences Source code on GitHub Report issues in Jira Stack Overflow questions Slack Community The Groovy programming language is supported by the Apache Software Foundation and the Groovy community. Apache, Apache Groovy, Groovy, and the ASF logo are either registered trademarks or trademarks of The Apache Software Foundation. © 2003-2025 the Apache Groovy project — Groovy is Open Source: license , privacy policy . | 2026-01-13T09:29:33 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3AexpandableTextbox | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:33 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3Anested | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:33 |
http://groovy-lang.org/syntax.html#_gstring_and_string_hashcodes | The Apache Groovy programming language - Syntax Socialize Discuss on the mailing-list Groovy on X Groovy on Bluesky Groovy on Mastodon Groovy on LinkedIn Events and conferences Source code on GitHub Report issues in Jira Stack Overflow questions Slack Community You are using an outdated browser. Please upgrade your browser to improve your experience. Apache Groovy™ Learn Documentation Download Support Contribute Ecosystem Blog posts Socialize Table of contents 1. Comments 1.1. Single-line comment 1.2. Multiline comment 1.3. Groovydoc comment 1.4. Shebang line 2. Keywords 3. Identifiers 3.1. Normal identifiers 3.2. Quoted identifiers 4. Strings 4.1. Single-quoted string 4.2. String concatenation 4.3. Triple-single-quoted string 4.3.1. Escaping special characters 4.3.2. Unicode escape sequence 4.4. Double-quoted string 4.4.1. String interpolation 4.4.2. Special case of interpolating closure expressions 4.4.3. Interoperability with Java 4.4.4. GString and String hashCodes 4.5. Triple-double-quoted string 4.6. Slashy string 4.6.1. Special cases 4.7. Dollar slashy string 4.8. String summary table 4.9. Characters 5. Numbers 5.1. Integral literals 5.1.1. Alternative non-base 10 representations Binary literal Octal literal Hexadecimal literal 5.2. Decimal literals 5.3. Underscore in literals 5.4. Number type suffixes 5.5. Math operations 5.5.1. The case of the division operator 5.5.2. The case of the power operator 6. Booleans 7. Lists 8. Arrays 8.1. Java-style array initialization 9. Maps Syntax This chapter covers the syntax of the Groovy programming language. The grammar of the language derives from the Java grammar, but enhances it with specific constructs for Groovy, and allows certain simplifications. 1. Comments 1.1. Single-line comment Single-line comments start with // and can be found at any position in the line. The characters following // , until the end of the line, are considered part of the comment. // a standalone single line comment println "hello" // a comment till the end of the line 1.2. Multiline comment A multiline comment starts with /* and can be found at any position in the line. The characters following /* will be considered part of the comment, including new line characters, up to the first */ closing the comment. Multiline comments can thus be put at the end of a statement, or even inside a statement. /* a standalone multiline comment spanning two lines */ println "hello" /* a multiline comment starting at the end of a statement */ println 1 /* one */ + 2 /* two */ 1.3. Groovydoc comment Similarly to multiline comments, Groovydoc comments are multiline, but start with /** and end with */ . Lines following the first Groovydoc comment line can optionally start with a star * . Those comments are associated with: type definitions (classes, interfaces, enums, annotations), fields and properties definitions methods definitions Although the compiler will not complain about Groovydoc comments not being associated with the above language elements, you should prepend those constructs with the comment right before it. /** * A Class description */ class Person { /** the name of the person */ String name /** * Creates a greeting method for a certain person. * * @param otherPerson the person to greet * @return a greeting message */ String greet(String otherPerson) { "Hello ${otherPerson}" } } Groovydoc follows the same conventions as Java’s own Javadoc. So you’ll be able to use the same tags as with Javadoc. In addition, Groovy supports Runtime Groovydoc since 3.0.0, i.e. Groovydoc can be retained at runtime. Runtime Groovydoc is disabled by default. It can be enabled by adding JVM option -Dgroovy.attach.runtime.groovydoc=true The Runtime Groovydoc starts with /**@ and ends with */ , for example: /**@ * Some class groovydoc for Foo */ class Foo { /**@ * Some method groovydoc for bar */ void bar() { } } assert Foo.class.groovydoc.content.contains('Some class groovydoc for Foo') (1) assert Foo.class.getMethod('bar', new Class[0]).groovydoc.content.contains('Some method groovydoc for bar') (2) 1 Get the runtime groovydoc for class Foo 2 Get the runtime groovydoc for method bar 1.4. Shebang line Beside the single-line comment, there is a special line comment, often called the shebang line understood by UNIX systems which allows scripts to be run directly from the command-line, provided you have installed the Groovy distribution and the groovy command is available on the PATH . #!/usr/bin/env groovy println "Hello from the shebang line" The # character must be the first character of the file. Any indentation would yield a compilation error. 2. Keywords Groovy has the following reserved keywords: Table 1. Reserved Keywords abstract assert break case catch class const continue def default do else enum extends final finally for goto if implements import instanceof interface native new null non-sealed package public protected private return static strictfp super switch synchronized this threadsafe throw throws transient try while Of these, const , goto , strictfp , and threadsafe are not currently in use. The reserved keywords can’t in general be used for variable, field and method names. A trick allows methods to be defined having the same name as a keyword by surrounding the name in quotes as shown in the following example: // reserved keywords can be used for method names if quoted def "abstract"() { true } // when calling such methods, the name must be qualified using "this." this.abstract() Using such names might be confusing and is often best to avoid. The trick is primarily intended to enable certain Java integration scenarios and certain DSL scenarios where having "verbs" and "nouns" with the same name as keywords may be desirable. In addition, Groovy has the following contextual keywords: Table 2. Contextual Keywords as in permits record sealed trait var yields These words are only keywords in certain contexts and can be more freely used in some places, in particular for variables, fields and method names. This extra lenience allows using method or variable names that were not keywords in earlier versions of Groovy or are not keywords in Java. Examples are shown here: // contextual keywords can be used for field and variable names def as = true assert as // contextual keywords can be used for method names def in() { true } // when calling such methods, the name only needs to be qualified using "this." in scenarios which would be ambiguous this.in() Groovy programmers familiar with these contextual keywords may still wish to avoid using those names unless there is a good reason to use such a name. The restrictions on reserved keywords also apply for the primitive types, the boolean literals and the null literal (all of which are discussed later): Table 3. Other reserved words null true false boolean char byte short int long float double While not recommended, the same trick as for reserved keywords can be used: def "null"() { true } // not recommended; potentially confusing assert this.null() // must be qualified Using such words as method names is potentially confusing and is often best to avoid, however, it might be useful for certain kinds of DSLs . 3. Identifiers 3.1. Normal identifiers Identifiers start with a letter, a dollar or an underscore. They cannot start with a number. A letter can be in the following ranges: 'a' to 'z' (lowercase ascii letter) 'A' to 'Z' (uppercase ascii letter) '\u00C0' to '\u00D6' '\u00D8' to '\u00F6' '\u00F8' to '\u00FF' '\u0100' to '\uFFFE' Then following characters can contain letters and numbers. Here are a few examples of valid identifiers (here, variable names): def name def item3 def with_underscore def $dollarStart But the following ones are invalid identifiers: def 3tier def a+b def a#b All keywords are also valid identifiers when following a dot: foo.as foo.assert foo.break foo.case foo.catch 3.2. Quoted identifiers Quoted identifiers appear after the dot of a dotted expression. For instance, the name part of the person.name expression can be quoted with person."name" or person.'name' . This is particularly interesting when certain identifiers contain illegal characters that are forbidden by the Java Language Specification, but which are allowed by Groovy when quoted. For example, characters like a dash, a space, an exclamation mark, etc. def map = [:] map."an identifier with a space and double quotes" = "ALLOWED" map.'with-dash-signs-and-single-quotes' = "ALLOWED" assert map."an identifier with a space and double quotes" == "ALLOWED" assert map.'with-dash-signs-and-single-quotes' == "ALLOWED" As we shall see in the following section on strings , Groovy provides different string literals. All kind of strings are actually allowed after the dot: map.'single quote' map."double quote" map.'''triple single quote''' map."""triple double quote""" map./slashy string/ map.$/dollar slashy string/$ There’s a difference between plain character strings and Groovy’s GStrings (interpolated strings), as in that the latter case, the interpolated values are inserted in the final string for evaluating the whole identifier: def firstname = "Homer" map."Simpson-${firstname}" = "Homer Simpson" assert map.'Simpson-Homer' == "Homer Simpson" 4. Strings Text literals are represented in the form of chain of characters called strings. Groovy lets you instantiate java.lang.String objects, as well as GStrings ( groovy.lang.GString ) which are also called interpolated strings in other programming languages. 4.1. Single-quoted string Single-quoted strings are a series of characters surrounded by single quotes: 'a single-quoted string' Single-quoted strings are plain java.lang.String and don’t support interpolation. 4.2. String concatenation All the Groovy strings can be concatenated with the + operator: assert 'ab' == 'a' + 'b' 4.3. Triple-single-quoted string Triple-single-quoted strings are a series of characters surrounded by triplets of single quotes: '''a triple-single-quoted string''' Triple-single-quoted strings are plain java.lang.String and don’t support interpolation. Triple-single-quoted strings may span multiple lines. The content of the string can cross line boundaries without the need to split the string in several pieces and without concatenation or newline escape characters: def aMultilineString = '''line one line two line three''' If your code is indented, for example in the body of the method of a class, your string will contain the whitespace of the indentation. The Groovy Development Kit contains methods for stripping out the indentation with the String#stripIndent() method, and with the String#stripMargin() method that takes a delimiter character to identify the text to remove from the beginning of a string. When creating a string as follows: def startingAndEndingWithANewline = ''' line one line two line three ''' You will notice that the resulting string contains a newline character as first character. It is possible to strip that character by escaping the newline with a backslash: def strippedFirstNewline = '''\ line one line two line three ''' assert !strippedFirstNewline.startsWith('\n') 4.3.1. Escaping special characters You can escape single quotes with the backslash character to avoid terminating the string literal: 'an escaped single quote: \' needs a backslash' And you can escape the escape character itself with a double backslash: 'an escaped escape character: \\ needs a double backslash' Some special characters also use the backslash as escape character: Escape sequence Character \b backspace \f formfeed \n newline \r carriage return \s single space \t tabulation \\ backslash \' single quote within a single-quoted string (and optional for triple-single-quoted and double-quoted strings) \" double quote within a double-quoted string (and optional for triple-double-quoted and single-quoted strings) We’ll see some more escaping details when it comes to other types of strings discussed later. 4.3.2. Unicode escape sequence For characters that are not present on your keyboard, you can use unicode escape sequences: a backslash, followed by 'u', then 4 hexadecimal digits. For example, the Euro currency symbol can be represented with: 'The Euro currency symbol: \u20AC' 4.4. Double-quoted string Double-quoted strings are a series of characters surrounded by double quotes: "a double-quoted string" Double-quoted strings are plain java.lang.String if there’s no interpolated expression, but are groovy.lang.GString instances if interpolation is present. To escape a double quote, you can use the backslash character: "A double quote: \"". 4.4.1. String interpolation Any Groovy expression can be interpolated in all string literals, apart from single and triple-single-quoted strings. Interpolation is the act of replacing a placeholder in the string with its value upon evaluation of the string. The placeholder expressions are surrounded by ${} . The curly braces may be omitted for unambiguous dotted expressions, i.e. we can use just a $ prefix in those cases. If the GString is ever passed to a method taking a String, the expression value inside the placeholder is evaluated to its string representation (by calling toString() on that expression) and the resulting String is passed to the method. Here, we have a string with a placeholder referencing a local variable: def name = 'Guillaume' // a plain string def greeting = "Hello ${name}" assert greeting.toString() == 'Hello Guillaume' Any Groovy expression is valid, as we can see in this example with an arithmetic expression: def sum = "The sum of 2 and 3 equals ${2 + 3}" assert sum.toString() == 'The sum of 2 and 3 equals 5' Not only are expressions allowed in between the ${} placeholder, but so are statements. However, a statement’s value is just null . So if several statements are inserted in that placeholder, the last one should somehow return a meaningful value to be inserted. For instance, "The sum of 1 and 2 is equal to ${def a = 1; def b = 2; a + b}" is supported and works as expected but a good practice is usually to stick to simple expressions inside GString placeholders. In addition to ${} placeholders, we can also use a lone $ sign prefixing a dotted expression: def person = [name: 'Guillaume', age: 36] assert "$person.name is $person.age years old" == 'Guillaume is 36 years old' But only dotted expressions of the form a.b , a.b.c , etc, are valid. Expressions containing parentheses like method calls, curly braces for closures, dots which aren’t part of a property expression or arithmetic operators would be invalid. Given the following variable definition of a number: def number = 3.14 The following statement will throw a groovy.lang.MissingPropertyException because Groovy believes you’re trying to access the toString property of that number, which doesn’t exist: shouldFail(MissingPropertyException) { println "$number.toString()" } You can think of "$number.toString()" as being interpreted by the parser as "${number.toString}()" . Similarly, if the expression is ambiguous, you need to keep the curly braces: String thing = 'treasure' assert 'The x-coordinate of the treasure is represented by treasure.x' == "The x-coordinate of the $thing is represented by $thing.x" // <= Not allowed: ambiguous!! assert 'The x-coordinate of the treasure is represented by treasure.x' == "The x-coordinate of the $thing is represented by ${thing}.x" // <= Curly braces required If you need to escape the $ or ${} placeholders in a GString so they appear as is without interpolation, you just need to use a \ backslash character to escape the dollar sign: assert '$5' == "\$5" assert '${name}' == "\${name}" 4.4.2. Special case of interpolating closure expressions So far, we’ve seen we could interpolate arbitrary expressions inside the ${} placeholder, but there is a special case and notation for closure expressions. When the placeholder contains an arrow, ${→} , the expression is actually a closure expression — you can think of it as a closure with a dollar prepended in front of it: def sParameterLessClosure = "1 + 2 == ${-> 3}" (1) assert sParameterLessClosure == '1 + 2 == 3' def sOneParamClosure = "1 + 2 == ${ w -> w << 3}" (2) assert sOneParamClosure == '1 + 2 == 3' 1 The closure is a parameterless closure which doesn’t take arguments. 2 Here, the closure takes a single java.io.StringWriter argument, to which you can append content with the << leftShift operator. In either case, both placeholders are embedded closures. In appearance, it looks like a more verbose way of defining expressions to be interpolated, but closures have an interesting advantage over mere expressions: lazy evaluation. Let’s consider the following sample: def number = 1 (1) def eagerGString = "value == ${number}" def lazyGString = "value == ${ -> number }" assert eagerGString == "value == 1" (2) assert lazyGString == "value == 1" (3) number = 2 (4) assert eagerGString == "value == 1" (5) assert lazyGString == "value == 2" (6) 1 We define a number variable containing 1 that we then interpolate within two GStrings, as an expression in eagerGString and as a closure in lazyGString . 2 We expect the resulting string to contain the same string value of 1 for eagerGString . 3 Similarly for lazyGString 4 Then we change the value of the variable to a new number 5 With a plain interpolated expression, the value was actually bound at the time of creation of the GString. 6 But with a closure expression, the closure is called upon each coercion of the GString into String, resulting in an updated string containing the new number value. An embedded closure expression taking more than one parameter will generate an exception at runtime. Only closures with zero or one parameter are allowed. 4.4.3. Interoperability with Java When a method (whether implemented in Java or Groovy) expects a java.lang.String , but we pass a groovy.lang.GString instance, the toString() method of the GString is automatically and transparently called. String takeString(String message) { (4) assert message instanceof String (5) return message } def message = "The message is ${'hello'}" (1) assert message instanceof GString (2) def result = takeString(message) (3) assert result instanceof String assert result == 'The message is hello' 1 We create a GString variable 2 We double-check it’s an instance of the GString 3 We then pass that GString to a method taking a String as parameter 4 The signature of the takeString() method explicitly says its sole parameter is a String 5 We also verify that the parameter is indeed a String and not a GString. 4.4.4. GString and String hashCodes Although interpolated strings can be used in lieu of plain Java strings, they differ with strings in a particular way: their hashCodes are different. Plain Java strings are immutable, whereas the resulting String representation of a GString can vary, depending on its interpolated values. Even for the same resulting string, GStrings and Strings don’t have the same hashCode. assert "one: ${1}".hashCode() != "one: 1".hashCode() GString and Strings having different hashCode values, using GString as Map keys should be avoided, especially if we try to retrieve an associated value with a String instead of a GString. def key = "a" def m = ["${key}": "letter ${key}"] (1) assert m["a"] == null (2) 1 The map is created with an initial pair whose key is a GString 2 When we try to fetch the value with a String key, we will not find it, as Strings and GString have different hashCode values 4.5. Triple-double-quoted string Triple-double-quoted strings behave like double-quoted strings, with the addition that they are multiline, like the triple-single-quoted strings. def name = 'Groovy' def template = """ Dear Mr ${name}, You're the winner of the lottery! Yours sincerly, Dave """ assert template.toString().contains('Groovy') Neither double quotes nor single quotes need be escaped in triple-double-quoted strings. 4.6. Slashy string Beyond the usual quoted strings, Groovy offers slashy strings, which use / as the opening and closing delimiter. Slashy strings are particularly useful for defining regular expressions and patterns, as there is no need to escape backslashes. Example of a slashy string: def fooPattern = /.*foo.*/ assert fooPattern == '.*foo.*' Only forward slashes need to be escaped with a backslash: def escapeSlash = /The character \/ is a forward slash/ assert escapeSlash == 'The character / is a forward slash' Slashy strings are multiline: def multilineSlashy = /one two three/ assert multilineSlashy.contains('\n') Slashy strings can be thought of as just another way to define a GString but with different escaping rules. They hence support interpolation: def color = 'blue' def interpolatedSlashy = /a ${color} car/ assert interpolatedSlashy == 'a blue car' 4.6.1. Special cases An empty slashy string cannot be represented with a double forward slash, as it’s understood by the Groovy parser as a line comment. That’s why the following assert would actually not compile as it would look like a non-terminated statement: assert '' == // As slashy strings were mostly designed to make regexp easier so a few things that are errors in GStrings like $() or $5 will work with slashy strings. Remember that escaping backslashes is not required. An alternative way of thinking of this is that in fact escaping is not supported. The slashy string /\t/ won’t contain a tab but instead a backslash followed by the character 't'. Escaping is only allowed for the slash character, i.e. /\/folder/ will be a slashy string containing '/folder' . A consequence of slash escaping is that a slashy string can’t end with a backslash. Otherwise that will escape the slashy string terminator. You can instead use a special trick, /ends with slash ${'\\'}/ . But best just avoid using a slashy string in such a case. 4.7. Dollar slashy string Dollar slashy strings are multiline GStrings delimited with an opening $/ and a closing /$ . The escaping character is the dollar sign, and it can escape another dollar, or a forward slash. Escaping for the dollar and forward slash characters is only needed where conflicts arise with the special use of those characters. The characters $foo would normally indicate a GString placeholder, so those four characters can be entered into a dollar slashy string by escaping the dollar, i.e. $$foo . Similarly, you will need to escape a dollar slashy closing delimiter if you want it to appear in your string. Here are a few examples: def name = "Guillaume" def date = "April, 1st" def dollarSlashy = $/ Hello $name, today we're ${date}. $ dollar sign $$ escaped dollar sign \ backslash / forward slash $/ escaped forward slash $$$/ escaped opening dollar slashy $/$$ escaped closing dollar slashy /$ assert [ 'Guillaume', 'April, 1st', '$ dollar sign', '$ escaped dollar sign', '\\ backslash', '/ forward slash', '/ escaped forward slash', '$/ escaped opening dollar slashy', '/$ escaped closing dollar slashy' ].every { dollarSlashy.contains(it) } It was created to overcome some of the limitations of the slashy string escaping rules. Use it when its escaping rules suit your string contents (typically if it has some slashes you don’t want to escape). 4.8. String summary table String name String syntax Interpolated Multiline Escape character Single-quoted '…​' \ Triple-single-quoted '''…​''' \ Double-quoted "…​" \ Triple-double-quoted """…​""" \ Slashy /…​/ \ Dollar slashy $/…​/$ $ 4.9. Characters Unlike Java, Groovy doesn’t have an explicit character literal. However, you can be explicit about making a Groovy string an actual character, by three different means: char c1 = 'A' (1) assert c1 instanceof Character def c2 = 'B' as char (2) assert c2 instanceof Character def c3 = (char)'C' (3) assert c3 instanceof Character 1 by being explicit when declaring a variable holding the character by specifying the char type 2 by using type coercion with the as operator 3 by using a cast to char operation The first option 1 is interesting when the character is held in a variable, while the other two ( 2 and 3 ) are more interesting when a char value must be passed as argument of a method call. 5. Numbers Groovy supports different kinds of integral literals and decimal literals, backed by the usual Number types of Java. 5.1. Integral literals The integral literal types are the same as in Java: byte char short int long java.math.BigInteger You can create integral numbers of those types with the following declarations: // primitive types byte b = 1 char c = 2 short s = 3 int i = 4 long l = 5 // infinite precision BigInteger bi = 6 If you use optional typing by using the def keyword, the type of the integral number will vary: it’ll adapt to the capacity of the type that can hold that number. For positive numbers: def a = 1 assert a instanceof Integer // Integer.MAX_VALUE def b = 2147483647 assert b instanceof Integer // Integer.MAX_VALUE + 1 def c = 2147483648 assert c instanceof Long // Long.MAX_VALUE def d = 9223372036854775807 assert d instanceof Long // Long.MAX_VALUE + 1 def e = 9223372036854775808 assert e instanceof BigInteger As well as for negative numbers: def na = -1 assert na instanceof Integer // Integer.MIN_VALUE def nb = -2147483648 assert nb instanceof Integer // Integer.MIN_VALUE - 1 def nc = -2147483649 assert nc instanceof Long // Long.MIN_VALUE def nd = -9223372036854775808 assert nd instanceof Long // Long.MIN_VALUE - 1 def ne = -9223372036854775809 assert ne instanceof BigInteger 5.1.1. Alternative non-base 10 representations Numbers can also be represented in binary, octal, hexadecimal and decimal bases. Binary literal Binary numbers start with a 0b prefix: int xInt = 0b10101111 assert xInt == 175 short xShort = 0b11001001 assert xShort == 201 as short byte xByte = 0b11 assert xByte == 3 as byte long xLong = 0b101101101101 assert xLong == 2925l BigInteger xBigInteger = 0b111100100001 assert xBigInteger == 3873g int xNegativeInt = -0b10101111 assert xNegativeInt == -175 Octal literal Octal numbers are specified in the typical format of 0 followed by octal digits. int xInt = 077 assert xInt == 63 short xShort = 011 assert xShort == 9 as short byte xByte = 032 assert xByte == 26 as byte long xLong = 0246 assert xLong == 166l BigInteger xBigInteger = 01111 assert xBigInteger == 585g int xNegativeInt = -077 assert xNegativeInt == -63 Hexadecimal literal Hexadecimal numbers are specified in the typical format of 0x followed by hex digits. int xInt = 0x77 assert xInt == 119 short xShort = 0xaa assert xShort == 170 as short byte xByte = 0x3a assert xByte == 58 as byte long xLong = 0xffff assert xLong == 65535l BigInteger xBigInteger = 0xaaaa assert xBigInteger == 43690g Double xDouble = new Double('0x1.0p0') assert xDouble == 1.0d int xNegativeInt = -0x77 assert xNegativeInt == -119 5.2. Decimal literals The decimal literal types are the same as in Java: float double java.math.BigDecimal You can create decimal numbers of those types with the following declarations: // primitive types float f = 1.234 double d = 2.345 // infinite precision BigDecimal bd = 3.456 Decimals can use exponents, with the e or E exponent letter, followed by an optional sign, and an integral number representing the exponent: assert 1e3 == 1_000.0 assert 2E4 == 20_000.0 assert 3e+1 == 30.0 assert 4E-2 == 0.04 assert 5e-1 == 0.5 Conveniently for exact decimal number calculations, Groovy chooses java.math.BigDecimal as its decimal number type. In addition, both float and double are supported, but require an explicit type declaration, type coercion or suffix. Even if BigDecimal is the default for decimal numbers, such literals are accepted in methods or closures taking float or double as parameter types. Decimal numbers can’t be represented using a binary, octal or hexadecimal representation. 5.3. Underscore in literals When writing long literal numbers, it’s harder on the eye to figure out how some numbers are grouped together, for example with groups of thousands, of words, etc. By allowing you to place underscore in number literals, it’s easier to spot those groups: long creditCardNumber = 1234_5678_9012_3456L long socialSecurityNumbers = 999_99_9999L double monetaryAmount = 12_345_132.12 long hexBytes = 0xFF_EC_DE_5E long hexWords = 0xFFEC_DE5E long maxLong = 0x7fff_ffff_ffff_ffffL long alsoMaxLong = 9_223_372_036_854_775_807L long bytes = 0b11010010_01101001_10010100_10010010 5.4. Number type suffixes We can force a number (including binary, octals and hexadecimals) to have a specific type by giving a suffix (see table below), either uppercase or lowercase. Type Suffix BigInteger G or g Long L or l Integer I or i BigDecimal G or g Double D or d Float F or f Examples: assert 42I == Integer.valueOf('42') assert 42i == Integer.valueOf('42') // lowercase i more readable assert 123L == Long.valueOf("123") // uppercase L more readable assert 2147483648 == Long.valueOf('2147483648') // Long type used, value too large for an Integer assert 456G == new BigInteger('456') assert 456g == new BigInteger('456') assert 123.45 == new BigDecimal('123.45') // default BigDecimal type used assert .321 == new BigDecimal('.321') assert 1.200065D == Double.valueOf('1.200065') assert 1.234F == Float.valueOf('1.234') assert 1.23E23D == Double.valueOf('1.23E23') assert 0b1111L.class == Long // binary assert 0xFFi.class == Integer // hexadecimal assert 034G.class == BigInteger // octal 5.5. Math operations Although operators are covered in more detail elsewhere, it’s important to discuss the behavior of math operations and what their resulting types are. Division and power binary operations aside (covered below), binary operations between byte , char , short and int result in int binary operations involving long with byte , char , short and int result in long binary operations involving BigInteger and any other integral type result in BigInteger binary operations involving BigDecimal with byte , char , short , int and BigInteger result in BigDecimal binary operations between float , double and BigDecimal result in double binary operations between two BigDecimal result in BigDecimal The following table summarizes those rules: byte char short int long BigInteger float double BigDecimal byte int int int int long BigInteger double double BigDecimal char int int int long BigInteger double double BigDecimal short int int long BigInteger double double BigDecimal int int long BigInteger double double BigDecimal long long BigInteger double double BigDecimal BigInteger BigInteger double double BigDecimal float double double double double double double BigDecimal BigDecimal Thanks to Groovy’s operator overloading, the usual arithmetic operators work as well with BigInteger and BigDecimal , unlike in Java where you have to use explicit methods for operating on those numbers. 5.5.1. The case of the division operator The division operators / (and /= for division and assignment) produce a double result if either operand is a float or double , and a BigDecimal result otherwise (when both operands are any combination of an integral type short , char , byte , int , long , BigInteger or BigDecimal ). BigDecimal division is performed with the divide() method if the division is exact (i.e. yielding a result that can be represented within the bounds of the same precision and scale), or using a MathContext with a precision of the maximum of the two operands' precision plus an extra precision of 10, and a scale of the maximum of 10 and the maximum of the operands' scale. For integer division like in Java, you should use the intdiv() method, as Groovy doesn’t provide a dedicated integer division operator symbol. 5.5.2. The case of the power operator The power operation is represented by the ** operator, with two parameters: the base and the exponent. The result of the power operation depends on its operands, and the result of the operation (in particular if the result can be represented as an integral value). The following rules are used by Groovy’s power operation to determine the resulting type: If the exponent is a decimal value if the result can be represented as an Integer , then return an Integer else if the result can be represented as a Long , then return a Long otherwise return a Double If the exponent is an integral value if the exponent is strictly negative, then return an Integer , Long or Double if the result value fits in that type if the exponent is positive or zero if the base is a BigDecimal , then return a BigDecimal result value if the base is a BigInteger , then return a BigInteger result value if the base is an Integer , then return an Integer if the result value fits in it, otherwise a BigInteger if the base is a Long , then return a Long if the result value fits in it, otherwise a BigInteger We can illustrate those rules with a few examples: // base and exponent are ints and the result can be represented by an Integer assert 2 ** 3 instanceof Integer // 8 assert 10 ** 9 instanceof Integer // 1_000_000_000 // the base is a long, so fit the result in a Long // (although it could have fit in an Integer) assert 5L ** 2 instanceof Long // 25 // the result can't be represented as an Integer or Long, so return a BigInteger assert 100 ** 10 instanceof BigInteger // 10e20 assert 1234 ** 123 instanceof BigInteger // 170515806212727042875... // the base is a BigDecimal and the exponent a negative int // but the result can be represented as an Integer assert 0.5 ** -2 instanceof Integer // 4 // the base is an int, and the exponent a negative float // but again, the result can be represented as an Integer assert 1 ** -0.3f instanceof Integer // 1 // the base is an int, and the exponent a negative int // but the result will be calculated as a Double // (both base and exponent are actually converted to doubles) assert 10 ** -1 instanceof Double // 0.1 // the base is a BigDecimal, and the exponent is an int, so return a BigDecimal assert 1.2 ** 10 instanceof BigDecimal // 6.1917364224 // the base is a float or double, and the exponent is an int // but the result can only be represented as a Double value assert 3.4f ** 5 instanceof Double // 454.35430372146965 assert 5.6d ** 2 instanceof Double // 31.359999999999996 // the exponent is a decimal value // and the result can only be represented as a Double value assert 7.8 ** 1.9 instanceof Double // 49.542708423868476 assert 2 ** 0.1f instanceof Double // 1.0717734636432956 6. Booleans Boolean is a special data type that is used to represent truth values: true and false . Use this data type for simple flags that track true/false conditions . Boolean values can be stored in variables, assigned into fields, just like any other data type: def myBooleanVariable = true boolean untypedBooleanVar = false booleanField = true true and false are the only two primitive boolean values. But more complex boolean expressions can be represented using logical operators . In addition, Groovy has special rules (often referred to as Groovy Truth ) for coercing non-boolean objects to a boolean value. 7. Lists Groovy uses a comma-separated list of values, surrounded by square brackets, to denote lists. Groovy lists are plain JDK java.util.List , as Groovy doesn’t define its own collection classes. The concrete list implementation used when defining list literals are java.util.ArrayList by default, unless you decide to specify otherwise, as we shall see later on. def numbers = [1, 2, 3] (1) assert numbers instanceof List (2) assert numbers.size() == 3 (3) 1 We define a list numbers delimited by commas and surrounded by square brackets, and we assign that list into a variable 2 The list is an instance of Java’s java.util.List interface 3 The size of the list can be queried with the size() method, and shows our list contains 3 elements In the above example, we used a homogeneous list, but you can also create lists containing values of heterogeneous types: def heterogeneous = [1, "a", true] (1) 1 Our list here contains a number, a string and a boolean value We mentioned that by default, list literals are actually instances of java.util.ArrayList , but it is possible to use a different backing type for our lists, thanks to using type coercion with the as operator, or with explicit type declaration for your variables: def arrayList = [1, 2, 3] assert arrayList instanceof java.util.ArrayList def linkedList = [2, 3, 4] as LinkedList (1) assert linkedList instanceof java.util.LinkedList LinkedList otherLinked = [3, 4, 5] (2) assert otherLinked instanceof java.util.LinkedList 1 We use coercion with the as operator to explicitly request a java.util.LinkedList implementation 2 We can say that the variable holding the list literal is of type java.util.LinkedList You can access elements of the list with the [] subscript operator (both for reading and setting values) with positive indices or negative indices to access elements from the end of the list, as well as with ranges, and use the << leftShift operator to append elements to a list: def letters = ['a', 'b', 'c', 'd'] assert letters[0] == 'a' (1) assert letters[1] == 'b' assert letters[-1] == 'd' (2) assert letters[-2] == 'c' letters[2] = 'C' (3) assert letters[2] == 'C' letters << 'e' (4) assert letters[ 4] == 'e' assert letters[-1] == 'e' assert letters[1, 3] == ['b', 'd'] (5) assert letters[2..4] == ['C', 'd', 'e'] (6) 1 Access the first element of the list (zero-based counting) 2 Access the last element of the list with a negative index: -1 is the first element from the end of the list 3 Use an assignment to set a new value for the third element of the list 4 Use the << leftShift operator to append an element at the end of the list 5 Access two elements at once, returning a new list containing those two elements 6 Use a range to access a range of values from the list, from a start to an end element position As lists can be heterogeneous in nature, lists can also contain other lists to create multidimensional lists: def multi = [[0, 1], [2, 3]] (1) assert multi[1][0] == 2 (2) 1 Define a list of numbers 2 Access the second element of the top-most list, and the first element of the inner list 8. Arrays Groovy reuses the list notation for arrays, but to make such literals arrays, you need to explicitly define the type of the array through coercion or type declaration. String[] arrStr = ['Ananas', 'Banana', 'Kiwi'] (1) assert arrStr instanceof String[] (2) assert !(arrStr instanceof List) def numArr = [1, 2, 3] as int[] (3) assert numArr instanceof int[] (4) assert numArr.size() == 3 1 Define an array of strings using explicit variable type declaration 2 Assert that we created an array of strings 3 Create an array of ints with the as operator 4 Assert that we created an array of primitive ints You can also create multi-dimensional arrays: def matrix3 = new Integer[3][3] (1) assert matrix3.size() == 3 Integer[][] matrix2 (2) matrix2 = [[1, 2], [3, 4]] assert matrix2 instanceof Integer[][] 1 You can define the bounds of a new array 2 Or declare an array without specifying its bounds Access to elements of an array follows the same notation as for lists: String[] names = ['Cédric', 'Guillaume', 'Jochen', 'Paul'] assert names[0] == 'Cédric' (1) names[2] = 'Blackdrag' (2) assert names[2] == 'Blackdrag' 1 Retrieve the first element of the array 2 Set the value of the third element of the array to a new value 8.1. Java-style array initialization Groovy has always supported literal list/array definitions using square brackets and has avoided Java-style curly braces so as not to conflict with closure definitions. In the case where the curly braces come immediately after an array type declaration however, there is no ambiguity with closure definitions, so Groovy 3 and above support that variant of the Java array initialization expression. Examples: def primes = new int[] {2, 3, 5, 7, 11} assert primes.size() == 5 && primes.sum() == 28 assert primes.class.name == '[I' def pets = new String[] {'cat', 'dog'} assert pets.size() == 2 && pets.sum() == 'catdog' assert pets.class.name == '[Ljava.lang.String;' // traditional Groovy alternative still supported String[] groovyBooks = [ 'Groovy in Action', 'Making Java Groovy' ] assert groovyBooks.every{ it.contains('Groovy') } 9. Maps Sometimes called dictionaries or associative arrays in other languages, Groovy features maps. Maps associate keys to values, separating keys and values with colons, and each key/value pairs with commas, and the whole keys and values surrounded by square brackets. def colors = [red: '#FF0000', green: '#00FF00', blue: '#0000FF'] (1) assert colors['red'] == '#FF0000' (2) assert colors.green == '#00FF00' (3) colors['pink'] = '#FF00FF' (4) colors.yellow = '#FFFF00' (5) assert colors.pink == '#FF00FF' assert colors['yellow'] == '#FFFF00' assert colors instanceof java.util.LinkedHashMap 1 We define a map of string color names, associated with their hexadecimal-coded html colors 2 We use the subscript notation to check the content associated with the red key 3 We can also use the property notation to assert the color green’s hexadecimal representation 4 Similarly, we can use the subscript notation to add a new key/value pair 5 Or the property notation, to add the yellow color When using names for the keys, we actually define string keys in the map. Groovy creates maps that are actually instances of java.util.LinkedHashMap . If you try to access a key which is not present in the map: assert colors.unknown == null def emptyMap = [:] assert emptyMap.anyKey == null You will retrieve a null result. In the examples above, we used string keys, but you can also use values of other types as keys: def numbers = [1: 'one', 2: 'two'] assert numbers[1] == 'one' Here, we used numbers as keys, as numbers can unambiguously be recognized as numbers, so Groovy will not create a string key like in our previous examples. But consider the case you want to pass a variable in lieu of the key, to have the value of that variable become the key: def key = 'name' def person = [key: 'Guillaume'] (1) assert !person.containsKey('name') (2) assert person.containsKey('key') (3) 1 The key associated with the 'Guillaume' name will actually be the "key" string, not the value associated with the key variable 2 The map doesn’t contain the 'name' key 3 Instead, the map contains a 'key' key You can also pass quoted strings as well as keys: ["name": "Guillaume"]. This is mandatory if your key string isn’t a valid identifier, for example if you wanted to create a string key containing a dash like in: ["street-name": "Main street"]. When you need to pass variable values as keys in your map definitions, you must surround the variable or expression with parentheses: person = [(key): 'Guillaume'] (1) assert person.containsKey('name') (2) assert !person.containsKey('key') (3) 1 This time, we surround the key variable with parentheses, to instruct the parser we are passing a variable rather than defining a string key 2 The map does contain the name key 3 But the map doesn’t contain the key key as before Groovy Learn Documentation Download Support Contribute Ecosystem Blog posts About Source code Security Books Thanks Sponsorship FAQ Search Socialize Discuss on the mailing-list Groovy on X Groovy on Bluesky Groovy on Mastodon Groovy on LinkedIn Events and conferences Source code on GitHub Report issues in Jira Stack Overflow questions Slack Community The Groovy programming language is supported by the Apache Software Foundation and the Groovy community. Apache, Apache Groovy, Groovy, and the ASF logo are either registered trademarks or trademarks of The Apache Software Foundation. © 2003-2025 the Apache Groovy project — Groovy is Open Source: license , privacy policy . | 2026-01-13T09:29:33 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3Aentry | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:33 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3AdropdownList | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:33 |
https://gitstar-ranking.com/facebookarchive | facebookarchive - Gitstar Ranking Gitstar Ranking Users Organizations Repositories Rankings Users Organizations Repositories Sign in with GitHub facebookarchive Star 351781 Rank 22 Go to GitHub Fetched on 2026/01/09 07:27 495 Repositories draft-js 22919 pop 19627 flux 17495 prepack 14154 AsyncDisplayKit 13380 Shimmer 9359 react-360 8737 caffe2 8400 nuclide 7746 KVOController 7325 three20 7181 xctool 6888 fbctf 6571 rebound 5407 shimmer-android 5369 Keyframes 5311 grace 4899 Tweaks 4725 augmented-traffic-control 4325 fixed-data-table 4284 WebDriverAgent 4216 codemod 4129 huxley 4053 scribe 3918 RakNet 3407 FBMemoryProfiler 3397 mention-bot 3350 facebook-php-sdk 3295 origami 3250 php-graph-sdk 3205 network-connection-class 3185 beringei 3167 python-instagram 3049 react-native-fbsdk 2982 conceal 2948 webscalesql-5.6 2925 ios-snapshot-test-case 2653 device-year-class 2584 BOLT 2531 pfff 2440 fb.resnet.torch 2361 Surround360 2182 redux-react-hook 2151 xcbuild 2006 LogDevice 1905 redis-faina 1782 MemNN 1756 rebound-js 1750 planout 1693 fb-flo 1686 1 2 3 4 5 … › Released by @k0kubun in December 2014. Fork me on GitHub . | 2026-01-13T09:29:34 |
https://wiki.documentfoundation.org/Marketing | Marketing - The Document Foundation Wiki Jump to content Main menu Main menu move to sidebar hide Navigation Main page Get Involved Recent changes Random page Support LibreOffice! Editing the wiki Help resources The Document Foundation Wiki Search Search English Appearance Log in Personal tools Log in Marketing Page Discussion English Read View source View history Tools Tools move to sidebar hide Actions Read View source View history General What links here Related changes Special pages Printable version Permanent link Page information Appearance move to sidebar hide From The Document Foundation Wiki TDF LibreOffice Document Liberation Project Community Blogs Weblate Nextcloud Redmine Ask LibreOffice Donate Wiki Home Development Design QA Events Documentation Website Localization Accessibility Marketing Diversity Wiki Help The foundation Events Work Items Slogan Ideas US Marketing Branding Marketing Logo/Artwork Resources Other languages: Bahasa Indonesia Deutsch English Jawa Nederlands Türkçe español français italiano polski português do Brasil română монгол українська العربية سرائیکی فارسی नेपाली 中文（中国大陆） 中文（臺灣） 日本語 한국어 Communicating inside and outside the LibreOffice project The Marketing Team is responsible for spreading the word about LibreOffice, talking to the press, making sure communication runs smoothly between different teams, and presenting the software in a fresh and compelling way. We're always looking for volunteers, so feel free to lend a hand -- for global/general marketing, we communicate via the Marketing/Mailing List . Management First Steps : Join the marketing project - it's quick and easy! Conference Calls : Lists the agenda and the dial-in instructions for the regular Marketing Team conference calls General Release Meeting : Meeting to organize the different tasks to be done before a release LibreOffice Release Plan : Release schedule for upcoming versions of LibreOffice Follow up on booth material : Flyers, T-shirts, banners etc. for use at conferences and shows Work Items : Lists the Marketing Team work items and their current status Announcements For all announcements, please see our blog Events Events with LibreOffice participation List of Events in this wiki, including a calendar. Leave a note on the marketing mailing list if you are organising or attending an event on behalf of the LibreOffice community or The Document Foundation, and it will be added to the calendar LibreOffice Conferences Official LibreOffice Conference 2021 Online, September 23-25 Official LibreOffice Conference 2020 Online, October 15-17 Official LibreOffice Conference 2019 in Almería, September 10-13 Official LibreOffice Conference 2018 in Tirana, September 27-28 Official LibreOffice Conference 2017 in Rome, October 11-13 Official LibreOffice Conference 2016 in Brno, September 7-9 Official LibreOffice Conference 2015 in Aarhus, September 22-25 Official LibreOffice Conference 2014 in Bern, September 2-5 Official LibreOffice Conference 2013 in Milan, September 25-27 Official LibreOffice Conference 2012 in Berlin, October 17-19 Official LibreOffice Conference 2011 in Paris, October 12-15 Ideas and in-work topics Ideas : Page for marketing ideas and marketing material drafts. Add your ideas! LibreOffice slogan : Suggested slogans for the LibreOffice Suite. Be creative. Add your slogan! LibreOffice Release Party : A party organiser for the forthcoming LibreOffice release. Reference Cards: Simple tri-fold alternate-Keys reference cards for LibreOffice Applications. LibreOffice in Academia : Marketing LibreOffice in the academic world. Brochuretypes: Doing some brochures for different groups. Materials Useful resources Branding Guidelines : Branding material and information to ensure both consistent and fresh appearance; official logo and external logo (SVG, PNG) LibreOffice Videos : List of videos about LibreOffice Video how-to : Tips for making LibreOffice videos Video equipment : TDF's camera and microphone, that can be borrowed LibreOffice Flyers : Attractive flyers that can be printed and handed out Marketing Style guide : General guidelines to be observed when writing marketing materials such as press releases, flyers and blog posts TDF/LibreOffice Website & Web Sites Services : Addresses of all TDF/LibreOffice websites and services with their site maintainer name(s) Release coordination tasks : Table grouping the tasks that need to be coordinated for the release Press Kit: List of documents/tools available for press releases and all related LibreOffice Magazine : List for "LibreOffice Magazine International" and all other "LibreOffice Magazine [Language]" publications Special:MyLanguage/LibreOffice In The Press : List of earliest and old news and review articles about LibreOffice LibreOffice in Print : List of LibreOffice documents available in print or in downloadable format Marketing materials Marketing Material : Official marketing material for both The Document Foundation and LibreOffice LibreOffice Application Icon Sets: Set of icons available for marketing purposes LibreOffice Funding Challenge Resources wiki page: Banners, Clip Art etc. (TBA) LibreOffice-themed Wallpapers Paper Airplane : LibreOffice paper airplane and different designs Conference Kit : List of documents/tools available for conferences and all related LibreOffice 10/20 Campaign : Marketing materials for 10/20 campaign in 2020 Regional groups US Marketing : Pages devoted to US market (Canada junior partner) North American Community : Pages devoted to the (North American) NA Community - including ISO files for DVD install of LibreOffice and related items. Retrieved from " https://wiki.documentfoundation.org/index.php?title=Marketing&oldid=650278 " Category : Marketing This page was last edited 18:55, 24 March 2023 by Ilmari Lauhakangas . Based on work by Mike Saunders , The Document Foundation Wiki user Eddy and others . Please note that all contributions to The Document Foundation Wiki are considered to be released under the Creative Commons Attribution-ShareAlike 3.0 Unported License , unless otherwise specified. This does not include the source code of LibreOffice, which is licensed under the GNU Lesser General Public License ( LGPLv3 ). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy (see Project:Copyrights for details). LibreOffice was based on OpenOffice.org. If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here. Privacy policy About The Document Foundation Wiki Imprint | 2026-01-13T09:29:34 |
https://cloudflare.com/es-la/banking-and-financial-services/ | Transformación digital en servicios bancarios y financieros | Cloudflare Me interesa Idiomas English English (United Kingdom) Deutsch Español (Latinoamérica) Español (España) Français Italiano 日本語 한국어 Polski Português (Brasil) Русский 繁體中文 简体中文 Plataforma Conectividad cloud La conectividad cloud de Cloudflare ofrece más de 60 servicios de red, seguridad y rendimiento. Enterprise Para organizaciones grandes y medianas Pequeña empresa Para organizaciones pequeñas Socio Ser socio de Cloudflare Casos de uso Moderniza tus aplicaciones Acelera el rendimiento Protege la disponibilidad de tus aplicaciones Optimiza tu experiencia en la web Moderniza tu seguridad Reemplaza tu VPN Protégete contra el phishing Protege tu aplicaciones web y tus API Moderniza tus redes Red de cafeterías Moderniza tu WAN Simplifica tu red corporativa Temas de CXO Adopta la IA Incorpora IA a los equipos de trabajo y a las experiencias digitales Seguridad de IA Protege las aplicaciones de IA generativa y agéntica Cumplimiento de los datos Optimiza el cumplimiento normativo y minimiza el riesgo Criptografía poscuántica Protege los datos y cumple con los estándares de cumplimiento normativo Industrias Atención médica Banca Minoristas Videojuegos Sector público Recursos Guías de producto Arquitecturas de referencia Informes de analistas Eventos Eventos Demostraciones Seminarios web Talleres Solicitar una demo Productos Productos Seguridad del espacio de trabajo Acceso a la red Zero Trust Puerta de enlace web segura Seguridad del correo electrónico Agente de seguridad de acceso a la nube Seguridad para aplicaciones Protección DDoS a la capa 7 Firewall de aplicaciones web Seguridad de la API Gestión de bots Rendimiento de aplicaciones CDN DNS Enrutamiento inteligente Load balancing Redes y SASE Protección DDoS a las capas 3 - 4 NaaS/SD- WAN Firewall como servicio Interconexión de red Planes y precios Planes Enterprise Planes para pequeñas empresas Planes individuales Compara planes Servicios globales Paquetes de soporte para un rendimiento exitoso Experiencia optimizada de Cloudflare Servicios profesionales Implementación guiada por expertos Gestión de cuentas técnicas Gestión técnica enfocada Servicio de operaciones de seguridad Supervisión y respuesta de Cloudflare Registro de dominios Compra y gestiona dominios 1.1.1.1 Resolución de DNS gratuita Recursos Guías de producto Arquitecturas de referencia Informes de analistas Demos de productos y recorridos Ayúdame a elegir Desarrolladores Documentación Biblioteca para desarrolladores Documentación y guías Demos de aplicaciones Explora lo que puedes crear Tutoriales Tutoriales de creación paso a paso Arquitectura de referencia Diagramas y patrones de diseño Productos Inteligencia artificial AI Gateway Observa y controla las aplicaciones de IA Workers AI Ejecuta modelos de aprendizaje automático en nuestra red Proceso Observability Registros, métricas y seguimientos Workers Crea e implementa aplicaciones sin servidor Multimedia Images Transforma y optimiza imágenes Realtime Crea aplicaciones de audio y video en tiempo real Almacenamiento y base de datos D1 Desarrolla bases de datos SQL sin servidor R2 Almacena datos sin costosas tarifas de salida Planes y precios Workers Crea e implementa aplicaciones sin servidor Workers KV Almacén de clave-valor sin servidor para aplicaciones R2 Almacena datos sin costosas tarifas de salida Descubre proyectos Historias de nuestros clientes Demo de IA en 30 segundos Guía rápida para empezar Descubre Workers Playground Crea, prueba e implementa Discord para desarrolladores Únete a la comunidad Comienza a crear Socios Red de socios Crece, innova y satisface las necesidades de los clientes con Cloudflare Portal de socios Encuentra recursos y registra acuerdos Tipos de asociación Programa PowerUP Impulsa el crecimiento de tu negocio mientras garantizas la conexión y la seguridad de tus usuarios Socios de tecnología Explora nuestro ecosistema de asociaciones e integraciones tecnológicas Integradores de sistemas globales Apoyar la transformación digital eficiente a gran escala Proveedores de servicios Descubre nuestra red de valiosos proveedores de servicios Programa de agencias de autoservicio Gestiona las cuentas de autoservicio de tus clientes Portal punto a punto Información sobre el tráfico de tu red Encuentra un socio Impulsa tu negocio - conéctate con los socios de Cloudflare Powered+. Recursos Eventos Demos y recorridos por los productos Demostraciones de productos a pedido Casos prácticos Cloudflare, la clave del éxito Seminarios web Debates interesantes Talleres Foros virtuales Biblioteca Guías útiles, planes de desarrollo y mucho más Informes Información sobre investigaciones de Cloudflare Blog Análisis técnicos y novedades de productos Centro de aprendizaje Herramientas educativas y contenido práctico Desarrollar Arquitectura de referencia Guías técnicas Guías de soluciones y productos Documentación del producto Documentación Documentación para desarrolladores Explorar theNET Información estratégica para empresas digitales Cloudflare TV Series y eventos innovadores Cloudforce One Investigaciones y operaciones sobre amenazas Radar Tendencias del tráfico y la seguridad en Internet Informes de analistas Informes de investigación del sector Eventos Próximos eventos regionales Confianza, privacidad y cumplimiento normativo Información y políticas de cumplimiento normativo Soporte Te ayudamos Foro de la comunidad ¿Has perdido el acceso a tu cuenta? Discord para desarrolladores Te ayudamos Empresa información de la empresa Liderazgo Conoce a nuestros líderes Relaciones con inversores Información para inversores Prensa Consulta noticias recientes Empleo Explora las posiciones disponibles confianza, privacidad y seguridad Privacidad Política, datos y protección Confianza Política, proceso y seguridad Cumplimiento normativo Certificación y regulación Transparencia Política y divulgaciones INTERÉS PÚBLICO Asistencia humanitaria Proyecto Galileo Sector público Proyecto Athenian Elecciones Cloudflare para campañas Salud Project Fair Shot Red global Ubicaciones globales y estado Iniciar sesión Contacta con Ventas Protege la modernización digital de los bancos globales Con Cloudflare, los bancos pueden proporcionar experiencias digitales seguras y fluidas que cumplan con los requisitos relacionados con la soberanía de datos, la normativa y la resiliencia. Esto impulsa la innovación y la eficiencia operativa. Regístrate para la demostración Obtener el resumen de la solución Seguridad mejorada en un panorama de amenazas más amplio Cloudflare proporciona una eficaz protección contra las amenazas emergentes, como las vulnerabilidades web, de las API y de red, con cifrado de última generación y capacidades basadas en IA para la detección y respuesta a las amenazas. Desarrollo de aplicaciones modernas e innovación en la nube Impulsa la modernización digital gracias al desarrollo seguro de aplicaciones en la nube y la incorporación de IA avanzada y aprendizaje automático para mejorar las experiencias de los clientes. Resiliencia y rendimiento a gran escala Garantiza la resiliencia y el rendimiento de la red con alta prioridad y un alcance global, al mismo tiempo que cumples con los requisitos de soberanía de datos y logras una mejor experiencia para el cliente. Cumplimiento normativo simplificado Aborda los requisitos relacionados con las normativas a nivel mundial, como PCI, GDPR, DORA y NIS2, para asegurar el cumplimiento normativo y al mismo tiempo proteger los datos confidenciales y garantizar la eficiencia operativa. Transforma la banca con soluciones digitales seguras, escalables y conformes a la normativa Protección contra las amenazas de ciberseguridad emergentes Los bancos afrontan un panorama de amenazas en evolución y demandas normativas más estrictas. La información sobre amenazas avanzada y la obtención de datos en tiempo real ayudaron a los bancos a proteger proactivamente sus activos digitales. Servimos y analizamos el 20 % del tráfico web global, por lo que disponemos de una visibilidad inigualable. Esto nos permite bloquear cientos de miles de millones de amenazas al día y proteger tus entornos. Además, te ayudamos a proteger los vectores de fuga más comunes, y detener el ransomware, el phishing y shadow IT con nuestra seguridad Zero Trust así como los ataques a la cadena de suministro o a las aplicaciones web con cifrado de última generación y nuestra protección DDoS y del lado del cliente. Más información Impulsa la innovación con el desarrollo de aplicaciones modernas en la nube Acelera el futuro y la innovación digitales con el desarrollo de aplicaciones modernas en la nube. Integra de forma segura la IA, el aprendizaje automático y el análisis de los macrodatos en sus operaciones para impulsar servicios personalizados y procesos optimizados. Moderniza los sistemas esenciales y lanza nuevos productos financieros (p. ej., carteras digitales) para aumentar el interés de los clientes en todas las interacciones. Más información Resiliencia, rendimiento y alcance global inigualables Garantiza la resiliencia y un rendimiento optimizado de tus operaciones con una capacidad de red de 280 TB/s y conexiones de baja latencia (a aproximadamente 50 ms del 95 % de los usuarios de Internet). Proporciona redundancia global con nuestro enrutamiento de red anycast, que permite que varios servidores ejecuten todos nuestros servicios al mismo tiempo a la vez que comparten la misma dirección IP y enrutan las solicitudes al servidor más cercano. Admite requisitos de proveedor dual con nuestra configuración activo/en espera multiproveedor para la protección del tráfico de red en la capa 3. Este punto fuerte de la red garantiza un servicio coherente y fiable (incluso durante los picos de tráfico) para una experiencia sin interrupciones de los cliente. Más información Aborda el cumplimiento normativo a nivel mundial Cumple las normativas fundamentales como PCI DSS 4.0, GDPR, DORA y NIS2. Un enfoque de seguridad Zero Trust garantiza una verificación de identidad continua y estrictos controles de acceso, mientras que la seguridad de las aplicaciones, el cifrado eficiente y el enmascaramiento de datos protegen la información confidencial. Te ayudamos a prepararte para las auditorías, a minimizar el riesgo y a garantizar el cumplimiento normativo sin problemas. Más información Aumenta la fidelización de los clientes, reduce el riesgo y mejora los tiempos de respuesta con la conectividad cloud de Cloudflare 49 % Aumenta hasta un 49 % la fidelización de clientes gracias al rendimiento de las aplicaciones 1 50 % Reduce hasta un 50 % los riesgos relacionados con las políticas y la conformidad normativa 2 75 % Acelera hasta un 75 % los tiempos de respuesta a los ataques DDoS 3 Reconocimientos de analistas Cloudflare obtuvo un reconocimiento en Gartner® Magic Quadrant™ for SSE Creemos que este reconocimiento evidencia la arquitectura "filial ligera, nube pesada" de Cloudflare y su capacidad para ayudar a las empresas globales, orientadas a la nube, a acelerar la modernización de sus redes. Leer informe Cloudflare, reconocida como empresa líder en el informe The Forrester Wave™: Edge Development Platforms, 4.º trimestre de 2023 Forrester Research, Inc. evaluó los proveedores más importantes del mercado de plataformas para desarrolladores en el perímetro en función de 33 categorías: experiencia del desarrollador, seguridad y flexibilidad y transparencia de precios, y más. Leer informe Cloudflare es reconocida como empresa líder en el informe "2024 GigaOm Radar for CDN" Cloudflare ha sido reconocida como empresa "líder" y "empresa con un rendimiento sobresaliente" en el informe "2023 GigaOm Radar for CDN". El informe GigaOm Radar evaluó 19 soluciones de proveedores en una serie de anillos concéntricos, en los que las empresas más cercanas al centro se consideraron de mayor valor global. Leer informe SoFi logra lidiar con el tráfico malicioso gracias a Cloudflare En 2018, el equipo de seguridad de SoFi afrontaba constantemente amenazas de ciberataques, por lo que empezaron a buscar una firewall de aplicaciones web (WAF). Querían una solución fácil de usar que no solo bloqueara el tráfico malicioso sino que conforme surgían nuevas amenazas también mejorara sus conocimientos con el tiempo. Con el WAF de Cloudflare, los ingenieros de SoFi pudieron desarrollar e implementar casi al instante conjuntos de reglas granulares y reducir en más de un 60 % el tráfico malicioso, con un índice de falsos positivos realmente bajo. Lo más sorprendente fue que el uso del WAF de Cloudflare era muy fácil e intuitivo. Nuestros ingenieros enseguida se pusieron al día. Cloudflare solucionó en horas los problemas que otros proveedores de nube tardaban días en resolver. Ahora hemos empezado a usar otros productos de la cartera de Cloudflare. La integración de todas las soluciones de Cloudflare fue muy sencilla y no presentó dificultades". Con la confianza del 35 % de las empresas de la lista Fortune 500 Ver todos los casos prácticos Primeros pasos con Cloudflare Nuestros expertos te ayudarán a elegir la solución más adecuada para tu negocio. Te ayudamos Regístrate para la demostración Fuentes: TechValidate by Survey Monkey, un estudio TechValidate sobre Cloudflare Ibid Ibid PRIMEROS PASOS Planes gratuitos Planes para pequeñas empresas Para empresas Sugerencias Solicitar demostración Contacta con Ventas SOLUCIONES Conectividad cloud Servicios de aplicación SASE y seguridad del espacio de trabajo Servicios de red Plataforma para desarrolladores SOPORTE Centro de ayuda Atención al cliente Foro de la comunidad Discord para desarrolladores ¿Has perdido el acceso a tu cuenta? Estado de Cloudflare CUMPLIMIENTO NORMATIVO Recursos de conformidad Confianza GDPR IA responsable Informe de transparencia Notificar abuso INTERÉS PÚBLICO Proyecto Galileo Proyecto Athenian Cloudflare para campañas Proyecto Fairshot EMPRESA Acerca de Cloudflare Mapa de red Nuestro equipo Logotipos y dossier de prensa Diversidad, equidad e inclusión Impact/ESG © 2026 Cloudflare, Inc. Política de privacidad Términos de uso Informar sobre problemas de seguridad Confianza y seguridad Preferencias de cookies Marca comercial | 2026-01-13T09:29:34 |
https://wordpress.com/he/support/github-deployments/ | להשתמש בפריסות של GitHub בפלטפורמת WordPress.com – תמיכה מוצרים אפשרויות משאבים תוכניות ומחירים להתחבר להתחיל תפריט אחסון ב-WordPress WordPress לסוכנויות הצטרפות כשותף מממן שם דומיין בונה אתרים באמצעות בינה מלאכותית בונה אתרים יצירת בלוג ניוזלטר Professional Email שירותי עיצוב לאתרים Commerce WordPress Studio WordPress לארגונים סקירה ערכות עיצוב של WordPress תוספים של WordPress מקבצי בלוקים של WordPress Google Apps מרכז תמיכה חדשות וורדפרס יוצר השמות לעסקים יצירת לוגו לגלות פוסטים חדשים תגיות פופולריות חיפוש בלוג לסגור את תפריט הניווט להתחיל הרשמה להתחבר אודות תוכניות ומחירים מוצרים אחסון ב-WordPress WordPress לסוכנויות הצטרפות כשותף מממן שם דומיין בונה אתרים באמצעות בינה מלאכותית בונה אתרים יצירת בלוג ניוזלטר Professional Email שירותי עיצוב לאתרים Commerce WordPress Studio WordPress לארגונים אפשרויות סקירה ערכות עיצוב של WordPress תוספים של WordPress מקבצי בלוקים של WordPress Google Apps משאבים מרכז תמיכה חדשות וורדפרס יוצר השמות לעסקים יצירת לוגו לגלות פוסטים חדשים תגיות פופולריות חיפוש בלוג האפליקציה של Jetpack פרטים נוספים מרכז תמיכה מדריכים קורסים פורומים טופס יצירת קשר חיפוש מרכז תמיכה / מדריכים מרכז תמיכה מדריכים קורסים פורומים טופס יצירת קשר מדריכים / ניהול החשבון שלך / כלים / להשתמש בפריסות של GitHub בפלטפורמת WordPress.com להשתמש בפריסות של GitHub בפלטפורמת WordPress.com הפריסות של GitHub משלבות את המאגרים ב-GitHub ישירות עם האתר בפלטפורמת WordPress.com ומספקות לך תהליך עבודה אוטומטי שנשלט על ידי גרסה לפריסת תוספים, תבניות או שינויים מלאים באתר. מדריך זה מכסה את תהליך ההגדרה והדרך לנהל את המאגרים המחוברים. כלי זה זמין באתרים עם התוכניות Business ו-Commerce של WordPress.com. אם רכשת את התוכנית Business, יש לוודא שהיא הופעלה . באתרים חינמיים ובאתרים בתוכניות Personal ו-Premium, ניתן לשדרג את התוכנית כדי לגשת לכלי זה. במדריך הזה סרטון וידאו להדרכה להתחבר למאגר לנהל הגדרות פריסה פריסה מתקדמת לפרוס את הקוד לנהל חיבורים קיימים יומני הפעלת פריסות להתנתק ממאגר לנתק את WordPress.com מ-GitHub יש לך שאלה? להיעזר בסייען הבינה המלאכותית חזרה למעלה סרטון וידאו להדרכה סרטון זה הוא למנויים בלבד. ל-YouTube יש אפשרויות תרגום אוטומטי שיאפשרו לך לצפות בו בשפה שלך: כדי להפעיל כתוביות מתורגמות אוטומטית: נגן את הסרטון. לחץ על ⚙️ הגדרות (בפינה הימנית התחתונה של הסרטון). בחר Subtitles/CC (כתוביות) . בחר Auto-translate (תרגום אוטומטי) . בחר את השפה המועדפת עליך. כדי להאזין לדיבוב אוטומטי (ניסיוני): לחץ על ⚙️ הגדרות . בחר רצועת שמע . בחר את השפה שבה תרצה לשמוע את הסרטון. ℹ️ התרגומים והדיבובים נוצרים אוטומטית על ידי Google, ייתכן שיהיו בהם טעויות, והאפשרות לדיבוב אוטומטי עדיין בניסוי ואינה זמינה בכל השפות. להתחבר למאגר לפני שיהיה אפשר לפרוס מאגר של GitHub באתר בפלטפורמת WordPress.com, עליך ראשית להגדיר את החיבור בין השניים לפי השלבים הבאים: יש לעבור אל העמוד 'אתרים': https://wordpress.com/sites/ יש ללחוץ על שם האתר כדי להציג את סקירה האתר. יש ללחוץ על הכרטיסייה פריסות . יש ללחוץ על הכפתור " להתחבר למאגר ". לאחר מכן, אם מאגרים פורסמו ברשימה, כבר חיברת את החשבון GitHub. יש להמשיך לשלב 11. יש ללחוץ על הכפתור " להתקין את האפליקציה של WordPress.com ". חלון חדש ייפתח, ואם טרם עשית זאת, תופיע בקשה להתחבר לחשבון ב-GitHub. לאחר מכן, יוצג מסך זה: יש ללחוץ על הכפתור " לאשר WordPress.com למפתחים ". יש לבחור את הארגון או החשבון של GitHub שבהם המאגר ממוקם. יש לבחור את המאגר/מאגרים שברצונך להתחבר אליהם: כל המאגרים: בחירה באפשרות זו תעניק לפלטפורמה WordPress.com גישה לכל המאגרים הנוכחיים וגם העתידיים בבעלות חשבון GitHub הנבחר. דבר זה חל גם על מאגרים ציבוריים שהם לקריאה בלבד. רק מאגרים נבחרים : בחירת האפשרות הזו תאפשר לך לבחור לאילו מאגרים לפלטפורמה WordPress.com יש גישה בחשבון GitHub שנבחר. לאחר שבחרת אפשרות, יש ללחוץ על הכפתור להתקין . החלון החדש ייסגר ואנחנו נפנה אותך חזרה אל WordPress.com. יש לרשום את המאגר/המאגרים שבחרת יחד עם החשבון של GitHub שמשויך למאגר זה: יש ללחוץ על לבחור ליד המאגר שברצונך להתחבר אליו. בנקודה זו, כדאי לקרוא את WordPress.com למפתחים תחת האפליקציות המורשות של GitHub ותחת האפליקציות המותקנות של GitHub . לנהל הגדרות פריסה לאחר בחירת מאגר, יהיה עליך להתאים את הגדרות הפריסה: ענף הפריסה: חוזר לענף ברירת המחדל של המאגר (בדרך כלל ראשי ), אבל ניתן לשנות אותו לענף שבו ברצונך להשתמש. ספריית היעד: תיקיית השרת שבה ברצונך לפרוס את הקבצים. עבור תוספים, היא תהיה /wp-content/plugins/my-plugin-name . עבור תבניות, היא תהיה /wp-content/themes/my-theme-name . לפריסה חלקית של האתר (כלומר, מספר תוספים או תבניות), אפשר להשתמש בספרייה /wp-content . התכנים של מאגר יתמזגו עם התכנים הקיימים של האתר ב-WordPress בספרייה ספציפית. פריסות אוטומטיות: ישנן שתי דרכים שבהן אפשר לפרוס אל WordPress.com: אוטומטי: לאחר שהקוד יופעל, הוא ייפרס באתר בפלפורמת WordPress.com. פריסות אוטומטיות מומלצות עבור אתרי אחסון זמני. ידני: הקוד ייפרס לאחר בקשת פריסה . פריסות ידניות מומלצות עבור אתרי ייצור. מצב פריסה: ישנם שני סוגים של פריסות: פשוט: מצב זה יעתיק את כל הקבצים מענף של המאגר אל האתר ויפרוס אותם ללא שינוי לאחר עיבוד. מתקדם: עם מצב זה, אפשר להיעזר בקובץ Script של תהליכי עבודה ולבנות שלבים בהתאמה אישית, כגון התקנת יחסי תלות של Composer, בדיקת קוד לפני פריסתו ושליטה בפריסת קבצים. מומלץ עבור מאגרים שדורשים תוכנת Composer או Node. ניתן לעיין בפריסה מתקדמת למטה לקבלת מידע נוסף . לאחר שכל ההגדרות נקבעו, יש ללחוץ על הכפתור להתחבר . למאגר יתווספו: לתשומת ליבך, עליך להפעיל את הפריסה הראשונה, באופן אוטומטי או באופן ידני .לאחר מכן, אפשר להתחבר למאגר אחר בכל עת על ידי לחיצה על הכפתור " להתחבר למאגר ". פריסה מתקדמת עם 'פריסה מתקדמת', אפשר לספק קובץ Script של תהליך עבודה כדי לעבד קבצים במאגר לפני הפריסה. פעולה זו פותחת אפשרויות רבות, כגון בדיקת הקוד כדי לוודא שהוא עומד בתקני הקידוד של הצוות, הפעלת בדיקות של יחידות, לא כולל קבצים מפריסה, התקנת יחסי תלות ועוד. כדי להתחיל, אפשר להתרשם מהמתכונים לתהליכי עבודה שיצרנו . כדי להגדיר פריסה מתקדמת: יופיע טופס שבו אפשר להגדיר את הפריסה. יש ללחוץ על שם המאגר כדי לנהל את החיבור. בצד ימין, תחת " לבחור את מצב הפריסה ", יש לבחור מתקדם . אם המאגר כבר מכיל קובץ תהליך עבודה, אפשר לבחור אותו כאן. המערכת תבדוק אם קיימות שגיאות בקובץ. אם לא נמצאו שגיאות, יש להמשיך לשלב 7. אפשר גם לבחור את האפשרות " ליצור תהליך עבודה חדש " כדי להוסיף קובץ של תהליך עבודה שתצורתו נקבעה מראש. בחירה באפשרות זו תחליף את קובץ תהליך העבודה wpcom.yml אם הוא כבר קיים במאגר. יש ללחוץ על הכפתור " להתקין את תהליך העבודה עבורי " כדי להפעיל את קובץ תהליך העבודה במאגר. לאחר שתהליך עבודה נוסף ואומת, יש ללחוץ על לעדכן . המאגר ישתמש כעת בפריסה מתקדמת. לפרוס את הקוד לאחר חיבור המאגר של GitHub לאתר, השלב הבא הוא לפרוס את הקוד בפועל. ישנן שתי שיטות פריסה זמינות: אוטומטי וגם ידני . פריסות אוטומטיות אינן מומלצות באתרי הפקה פעילים, משום שכל שינוי קוד במאגר נפרס אוטומטית מ-GitHub לאתר הפעיל. במקום זאת, כדאי לשקול להגדיר פריסה אוטומטית אל אתר משוכפל ולסנכרן אותו לייצור כאשר הכל מוכן. פריסות ידניות מעניקות לך שליטה רבה יותר כאשר שינויי הקוד יידחפו בשידור חי, מאחר שיהיה עליך להפעיל באופן ידני כל פריסה. אנחנו ממליצים על פריסות ידניות אם אינך רוצה להשתמש באתר משוכפל. כדי להפעיל פריסה באופן ידני: יש לעבור אל העמוד 'אתרים': https://wordpress.com/sites/ יש ללחוץ על שם האתר כדי להציג את סקירה האתר. יש ללחוץ על הכרטיסייה פריסות . יש ללחוץ על תפריט שלוש הנקודות (⋮) במאגר שברצונך לפרוס. יש לבחור " להפעיל פריסה ידנית ". תוצג הודעה לכרזה הקובעת, "הפעלת הפריסה נוצרה" ומצב הפריסה ישתנה אל "ממתין בתור". יש להמתין להשלמת הפריסה (המצב ישתנה אל "נפרס"). יש ללחוץ שוב על תפריט שלוש הנקודות (⋮) ולבחור " להציג הפעלות פריסה ". יומן הפעלת הפריסה מציג את היוצר ואת הביצוע שנפרס. בלחיצה על רישום הפעלת הפריסה, אפשר להציג מידע נוסף. לנהל חיבורים קיימים כדי לנהל את חיבורי המאגר הקיימים של GitHub: יש לעבור אל העמוד 'אתרים': https://wordpress.com/sites/ יש ללחוץ על שם האתר כדי להציג את סקירה האתר. יש ללחוץ על הכרטיסייה פריסות . לאחר מכן, תוצג רשימת החיבורים. רשימת החיבורים מוצגת אם ישנו לפחות חיבור אחד בין מאגר GitHub לבין האתר. הרשימה כוללת מידע רלוונטי עבור כל חיבור, כגון שם המאגר והענף, הביצוע האחרון שנפרס באתר, במועד התרחשותו, מיקום הקוד, משך זמן הפעלת הפריסה והמצב שלה. פעולות נוספות זמינות אחרי לחיצה על תפריט שלוש הנקודות (⋮): להפעיל פריסה ידנית: מתחילה הפעלת פריסה בביצוע האחרון של הענף המוגדר. להציג הפעלות פריסה: נפתחת תצוגה של יומני ההפעלה של הפריסה עבור המאגר המחובר. להגדיר תצורת חיבור: נפתחת התצוגה לניהול חיבורים עבור המאגר. להתנתק מהמאגר: מוסר החיבור בין המאגר לבין האתר. יומני הפעלת פריסות יומני הפעלת פריסות מספקים תיעוד מפורט צעד אחר צעד של כל פריסה, בין אם היא מופעלת באופן אוטומטי או באופן ידני. יומנים אלה מסייעים לך לעקוב אחר שינויים, לעקוב אחר מצב הפריסה ולפתור כל בעיה שתתרחש. הודות לגישה ליומנים מ-10 ההפעלות האחרונות תוך 30 יום, אפשר לבדוק בקלות את הפעולות שהתרחשו בכל פריסה ולוודא שהכול פועל באופן חלק. כדי לבדוק את יומני הפריסה: יש לעבור אל העמוד 'אתרים': https://wordpress.com/sites/ יש ללחוץ על שם האתר כדי להציג את סקירה האתר. יש ללחוץ על הכרטיסייה פריסות . יש ללחוץ על תפריט שלוש הנקודות (⋮) ליד המאגר שברצונך להציג יומנים עבורו. לבחור " להציג את הפעלות הפריסה ". תצוגת הרשימה של הפעלות הפריסה מראה פעולות ביצוע שנפרסו באתר, מצב הפריסה, התאריך ומשך הזמן. ניתן ללחוץ בכל מקום בהפעלה כדי להרחיב ולהציג מידע נוסף אודות הפריסה. היומנים כוללים תיעוד של כל הפקודות שבוצעו, החל מהבאה של קוד מ-GitHub ועד למיקומם בספריית היעד. אפשר להרחיב את שורות היומן להצגת מידע נוסף על ידי לחיצה על " להציג עוד ". להתנתק ממאגר בעת התנתקות ממאגר של GitHub מהאתר, כל שינוי עתידי שיבוצע במאגר לא ישפיע עוד על האתר. כברירת מחדל, הקבצים שנפרסו נשארים באתר, אבל יש לך אפשרות להסיר אותם בזמן תהליך ההתנתקות. כדי להסיר מאגר: יש לעבור אל העמוד 'אתרים': https://wordpress.com/sites/ יש ללחוץ על שם האתר כדי להציג את סקירה האתר. יש ללחוץ על הכרטיסייה פריסות . יש ללחוץ על תפריט שלוש הנקודות (⋮) במאגר. יש לבחור " להתנתק מהמאגר ". יופיע חלון דו-שיח. יש ללחוץ על המתג כדי להסיר את הקבצים המשויכים מהאתר. יש ללחוץ על " להתנתק מהמאגר " כדי לסגור את תיבת הדו-שיח ולהתנתק מהמאגר. לתשומת ליבך, WordPress.com למפתחים עדיין יופיע תחת האפליקציות המותקנות של GitHub ותחת האפליקציות המורשות של GitHub . זאת מאחר שלפלטפורמה WordPress.com עדיין יש גישה למאגר, אבל החיבור נמחק. לנתק את WordPress.com מ-GitHub ניתן גם לבחור לבטל את הגישה של WordPress.com לחשבון GitHub. אפשר לעשות זאת בכל עת על ידי ביקור בהגדרות היישומים ב-GitHub. כדי לבטל את הגישה של אפליקציה מורשית לחשבון GitHub: יש לעבור אל אפליקציות מורשות של GitHub . לחצו על לבטל ליד WordPress.com למפתחים . יש ללחוץ על הכפתור " הבנתי, לבטל גישה ". גם בביטול הגישה לאפליקציה המורשית, עדיין תהיה אפשרות לפרוס את הקוד מאחר שהאפליקציה WordPress.com למפתחים תישאר מותקנת בחשבונות שנבחרו. כדי לבטל גישה להתקנה של WordPress.com ולהשבית את היכולת לפרוס קוד לאתר בפלטפורמה WordPress.com: יש לעבור אל אפליקציות מותקנות של GitHub . יש ללחוץ על להגדיר ליד WordPress.com למפתחים . באזור אזור סכנה , יש ללחוץ על לבטל התקנה ולאחר מכן ללחוץ על אישור בעת קבלת הנחיה לכך. בהסרת WordPress.com מרשימת האפליקציות המורשות אין משמעות הדבר שהמאגרים יימחקו או יפסיקו לפעול; המאגרים עדיין יהיו קיימים ב-GitHub לאחר ביטול הגישה של WordPress.com, אבל לפלטפורמה WordPress.com לא תהיה אפשרות לפרוס את הקוד. מדריכים קשורים פעילות סרגל הפעולות להתחבר ל-SSH להשתמש בלוח הבקרה של WP Admin במדריך הזה סרטון וידאו להדרכה להתחבר למאגר לנהל הגדרות פריסה פריסה מתקדמת לפרוס את הקוד לנהל חיבורים קיימים יומני הפעלת פריסות להתנתק ממאגר לנתק את WordPress.com מ-GitHub יש לך שאלה? להיעזר בסייען הבינה המלאכותית חזרה למעלה לא הצלחת למצוא את מה שנדרש? ליצור קשר לקבל תשובות מעוזר הבינה המלאכותית, עם גישה לתמיכה מנציג אנושי בכל שעות היממה וימות השבוע בתוכניות בתשלום. לפרסם שאלה בפורום שלנו ניתן לעיין בשאלות ולקבל תשובות ממשתמשים מנוסים אחרים. Copied to clipboard! WordPress.com מוצרים אחסון ב-WordPress WordPress לסוכנויות הצטרפות כשותף מממן שם דומיין בונה אתרים באמצעות בינה מלאכותית בונה אתרים יצירת בלוג Professional Email שירותי עיצוב לאתרים WordPress Studio WordPress לארגונים אפשרויות סקירה ערכות עיצוב של WordPress תוספים של WordPress מקבצי בלוקים של WordPress Google Apps משאבים בלוג של WordPress.com יוצר השמות לעסקים יצירת לוגו קורא WordPress.com נגישות הסרת מינויים עזרה מרכז תמיכה מדריכים קורסים פורומים טופס יצירת קשר מידע למפתחים חברה אודות תקשורת תנאי השירות מדיניות פרטיות אני לא רוצה למכור או לשתף את המידע האישי שלי הצהרת פרטיות למשתמשים מקליפורניה Deutsch Español Français Bahasa Indonesia Italiano Nederlands Português do Brasil Svenska Türkçe Русский العربية עִבְרִית 日本語 한국어 简体中文 繁體中文 English Deutsch Español Français Bahasa Indonesia Italiano Nederlands Português do Brasil Svenska Türkçe Русский العربية עִבְרִית 日本語 한국어 简体中文 繁體中文 English אפליקציות לנייד להוריד דרך App Store להתחיל לעבוד Google Play מדיה חברתית WordPress.com בפייסבוק WordPress.com ב-X (טוויטר) WordPress.com ב-Instagram WordPress.com ב-YouTube Automattic Automattic הצטרפות לכוח העבודה שלנו טוען תגובות... אתם חייבים להיות מחוברים על מנת לשלוח תגובה. להירשם רשום תמיכה הצטרפו ל 99 מנויים נוספים רשום אותי כבר יש לך חשבון ב-WordPress.com? זה הזמן להתחבר. תמיכה להירשם רשום הרשמה להתחבר העתקת קישור מקוצר דווח על תוכן זה להציג את הפוסט ב-Reader ניהול מינויים צמצום סרגל זה | 2026-01-13T09:29:34 |
https://gitstar-ranking.com/dotnet | dotnet - Gitstar Ranking Gitstar Ranking Users Organizations Repositories Rankings Users Organizations Repositories Sign in with GitHub dotnet Star 460028 Rank 15 Go to GitHub Fetched on 2026/01/09 07:52 277 Repositories aspnetcore 37574 maui 23124 core 21833 roslyn 20129 corefx 17545 runtime 17365 efcore 14520 AspNetCore.Docs 13050 coreclr 12782 csharplang 12434 BenchmarkDotNet 11324 orleans 10664 eShop 9896 yarp 9363 blazor 9316 machinelearning 9311 wpf 7540 reactive 7095 msbuild 5474 aspire 5302 tye 5237 MQTTnet 4907 Silk.NET 4827 dotnet-docker 4804 winforms 4735 machinelearning-samples 4666 docs 4621 Open-XML-SDK 4395 docfx 4381 fsharp 4227 samples 3670 command-line-api 3635 maui-samples 3587 cli 3472 roslynator 3355 aspnet-api-versioning 3171 interactive 3166 extensions 3097 standard 3051 sdk 3035 try 3022 vscode-csharp 3021 corert 2899 macios 2803 Docker.DotNet 2392 iot 2334 android-samples 2222 pinvoke 2179 spark 2091 android 2082 1 2 3 4 5 … › Released by @k0kubun in December 2014. Fork me on GitHub . | 2026-01-13T09:29:34 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3AdescriptorList | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:34 |
https://gitstar-ranking.com/PacktPublishing | PacktPublishing - Gitstar Ranking Gitstar Ranking Users Organizations Repositories Rankings Users Organizations Repositories Sign in with GitHub PacktPublishing Star 259399 Rank 31 Go to GitHub Fetched on 2026/01/09 08:23 9225 Repositories LLM-Engineers-Handbook 4600 Deep-Reinforcement-Learning-Hands-On 3064 The-Kaggle-Book 2298 Machine-Learning-for-Algorithmic-Trading-Second-Edition 2246 Advanced-Deep-Learning-with-Keras 1970 Node.js-Design-Patterns-Third-Edition 1869 Hands-On-Machine-Learning-for-Algorithmic-Trading 1772 Machine-Learning-for-Algorithmic-Trading-Second-Edition_Original 1517 Deep-Reinforcement-Learning-Hands-On-Second-Edition 1269 Learn-CUDA-Programming 1220 Learning-JavaScript-Data-Structures-and-Algorithms-Third-Edition 1107 3D-Graphics-Rendering-Cookbook 1093 Python-for-Algorithmic-Trading-Cookbook 1059 Deep-Learning-with-Keras 1050 40-Algorithms-Every-Programmer-Should-Know 1008 Hands-On-Graph-Neural-Networks-Using-Python 999 Causal-Inference-and-Discovery-in-Python 977 Learn-Algorithmic-Trading 920 Linux-Kernel-Programming 913 Modern-Computer-Vision-with-PyTorch 885 Vulkan-Cookbook 880 Django-4-by-example 859 Hands-on-Exploratory-Data-Analysis-with-Python 851 Java-Coding-Problems 843 Hands-On-Reinforcement-Learning-with-Python 834 Python-for-Finance-Cookbook 784 Mastering-Embedded-Linux-Programming-Third-Edition 776 Data-Engineering-with-Python 772 Pandas-Cookbook 770 50-Projects-In-50-Days---HTML-CSS-JavaScript 766 Learning-OpenCV-4-Computer-Vision-with-Python-Third-Edition 728 Node.js_Design_Patterns_Second_Edition_Code 713 Django-3-by-Example 707 Mastering-Graphics-Programming-with-Vulkan 676 Hands-On-Domain-Driven-Design-with-.NET-Core 665 Hands-On-GPU-Accelerated-Computer-Vision-with-OpenCV-and-CUDA 658 Learn-Data-Structures-and-Algorithms-with-Golang 640 Linux-Device-Drivers-Development 607 Building-Low-Latency-Applications-with-CPP 596 Transformers-for-Natural-Language-Processing 591 Modern-CMake-for-Cpp 582 Clean-Code-in-Python 578 TensorFlow-Machine-Learning-Cookbook 561 Django-2-by-Example 558 Software-Architecture-with-Cpp 547 Modern-Time-Series-Forecasting-with-Python 544 Mastering-OpenCV-4-Third-Edition 541 Hands-On-Data-Structures-and-Algorithms-with-Rust 537 Cpp17-STL-Cookbook 537 Python-Algorithmic-Trading-Cookbook 536 1 2 3 4 5 … › Released by @k0kubun in December 2014. Fork me on GitHub . | 2026-01-13T09:29:34 |
https://www.ecns.cn/video/2026-01-09/detail-iheyrzrv3841148.shtml | Comicomment: No country has the right to act as the world's police --> 中文 Home News Ecns Wire Business Travel Photo Video Voices RIGHT BG LINE Text: A A A Print Video Comicomment: No country has the right to act as the world's police 2026-01-09 17:03:29 Ecns.cn Editor : Meng Xiangjun ECNS App Download The US ’s bold military operation against Venezuela sets a dangerous precedent: powerful states can unilaterally impose their will on others, reducing the international order to a struggle of force. In reality, no country can legitimately serve as the world’s policeman or appoint itself an international judge—international law recognizes no such authority. The right to uphold justice across borders lies with multilateral institutions, not unilateral coercion. More Photo Exploring world's largest island Greenland Venezuelan people call on U.S. to release Nicolás Maduro and his wife Heavey snow hits Paris 'Southern Snow Town' draws tourists to Guizhou Province Global mayors attend dialogue in NE China on developing ice, snow economy Indonesia welcomes its first locally born giant panda cub Chinese FM on Venezuela situation: China always opposes imposing one country's will on another Maduro pleads not guilty in N.Y. court UN Security Council holds emergency meeting on Venezuela Harbin opens its 42nd Ice and Snow Festival China's Yangtze River remains world's busiest inland waterway by cargo throughput Bosideng Protest held in New York against U.S. military strikes on Venezuela Venezuelan President Nicolás Maduro transported to Brooklyn detention center International ice sculpture competition heats up in Harbin Mourners pay tribute to Crans-Montana bar fire victims Venezuelan leader Maduro brought to New York Beijing-Tangshan intercity railway starts full-line operation Passenger trips of 3 major Hainan airports exceed 50 million in 2025 First 'Grassland curling' attracts 350 competitors China launches two new satellites for space target detection test People perform 'circle dance' to pray for a bountiful new year in Qingha In numbers: China's high-speed rail mileage exceeds 50,000 km First batch of China's emergency humanitarian aid arrives in Cambodia Central London illuminated to welcome 2026 Chinese Foreign Minister meets Cambodian Deputy PM in Yunnan In Numbers: China holds Central Economic Work Conference to plan for 2026 Exploring vivid sports competition throughout 2025 Exploring stunning winter scenery in Altay China's first L3 self-driving car debuts in Chongqin Grand bridge ready for traffic operation in Guizhou Harbin's celebrity snowman lights up winter night Southbound Travel for Guangdong Vehicles scheme implemented for entry into urban Hong Kong China's Feng/Huang claim mixed doubles title at BWF World Tour Finals Exploring overwintering migratory birds in Poyang Lake Xi presents orders to promote two military officers to rank of genera Most popular in 24h More Top news China's willingness to promote shared development with Venezuela remains unchanged: FM spokesperson Chinese firms top global humanoid robot market in 2025: new report CIIE Stories | Where a Danish company finds 'possibility in every drop' U.S. could lose UN General Assembly vote over unpaid dues, UN says Chinese navy hospital ship pays first visit to Brazil More Video Comicomment: No country has the right to act as the world's police What's it like doing business in China? Check what foreign friends say LINE Media partners: People's Daily | Xinhua | CGTN | China Daily Back to top About Us | Jobs | Contact Us | Privacy Policy Copyright ©1999-2026 Chinanews.com. All rights reserved. Reproduction in whole or in part without permission is prohibited. [ 网上传播视听节目许可证（0106168) ] [ 京ICP证040655号 ] [ 京公网安备 11010202009201号 ] [ 京ICP备05004340号-1 ] --> --> | 2026-01-13T09:29:34 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3AeditableComboBoxValue | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:34 |
https://gitstar-ranking.com/huggingface | huggingface - Gitstar Ranking Gitstar Ranking Users Organizations Repositories Rankings Users Organizations Repositories Sign in with GitHub huggingface Star 638170 Rank 8 Go to GitHub Fetched on 2026/01/09 10:12 377 Repositories transformers 154764 pytorch-image-models 36161 diffusers 32388 open-r1 25801 smolagents 24816 agents-course 24698 datasets 21062 lerobot 20790 peft 20425 candle 19031 sentence-transformers 18085 trl 16907 transformers.js 15183 text-generation-inference 10720 chat-ui 10416 tokenizers 10376 accelerate 9427 smol-course 6571 parler-tts 5507 alignment-handbook 5474 deep-rl-class 4693 autotrain-advanced 4549 nanoVLM 4495 notebooks 4430 text-embeddings-inference 4370 speech-to-speech 4271 diffusion-models-class 4248 distil-whisper 4015 course 3646 safetensors 3586 smollm 3547 blog 3280 optimum 3242 huggingface_hub 3237 neuralcoref 2890 knockknock 2825 datatrove 2813 swift-coreml-diffusers 2728 setfit 2661 cookbook 2568 nanotron 2412 evaluate 2397 huggingface.js 2317 lighteval 2236 awesome-papers 2053 evaluation-guidebook 2029 chat-macOS 1983 picotron 1939 transformers.js-examples 1913 transfer-learning-conv-ai 1755 1 2 3 4 5 … › Released by @k0kubun in December 2014. Fork me on GitHub . | 2026-01-13T09:29:34 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3Atextarea | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:34 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3AvalidateButton | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:34 |
https://wiki.documentfoundation.org/Special:Random | Documentation/Calc Functions/ERF.PRECISE - The Document Foundation Wiki Jump to content Main menu Main menu move to sidebar hide Navigation Main page Get Involved Recent changes Random page Support LibreOffice! Editing the wiki Help resources The Document Foundation Wiki Search Search English Appearance Log in Personal tools Log in Documentation/Calc Functions/ERF.PRECISE Page Discussion English Read View source View history Tools Tools move to sidebar hide Actions Read View source View history General What links here Related changes Special pages Printable version Permanent link Page information Appearance move to sidebar hide From The Document Foundation Wiki < Documentation | Calc Functions This page contains changes which are not marked for translation. TDF LibreOffice Document Liberation Project Community Blogs Weblate Nextcloud Redmine Ask LibreOffice Donate Wiki Home Development Design QA Events Documentation Website Localization Accessibility Marketing Diversity Wiki Help The foundation Documentation Home Official Publications Other Resources FAQ HowTo Macros Docs Development Calc Functions Home | List of functions | Abbreviations Function name: ERF.PRECISE Category: Statistical Analysis Summary: Calculates values of the error function, also known as the Gauss error function. The error function is defined as an integral, which ERF.PRECISE evaluates between 0 and a specified limit. Syntax: ERF.PRECISE( Lower limit ) Returns: Returns a real number in the range -1 < x < 1, which is the value of the error function between 0 and the specified limit. Arguments: Lower limit is a real number, or a reference to a cell containing that number, which is the limit of the integral that defines the error function. The calculation takes place between 0 and this limit. The error function is an odd function and ERF.PRECISE utilizes the relationship [math]\displaystyle{ \text{ERF.PRECISE}(-x)=-\text{ERF.PRECISE}(x) }[/math] to ensure that the correct result is returned for negative values of Lower limit . If Lower limit is non-numeric, then ERF.PRECISE reports a #VALUE! error. Additional details: Calc's ERF and ERF.PRECISE functions perform similar calculations. However, ERF allows both upper and lower limits of the integral to be specified as arguments, whereas ERF.PRECISE always uses the value 0 for one of the limits. The requirements for ERF are specified in ODF 1.2; ERF.PRECISE is provided for interoperability with Microsoft Excel. The formula for ERF.PRECISE is: [math]\displaystyle{ \text{ERF.PRECISE}(x)~=~\frac{2}{\sqrt{\pi}}\:\int_{0}^{x}e^{-t^2}dt }[/math] where x is the limit of the integral. The following figure illustrates the ERF.PRECISE function: Plot for ERF.PRECISE function The name space for ERF.PRECISE is COM.MICROSOFT.ERF.PRECISE . For more information about the error function, visit Wikipedia's Error function page. Examples: Formula Description Returns =ERF.PRECISE(A1) where cell A1 contains the value 0.5. Here the function calculates the integral between 0 and 0.5. Note that the formula =ERF(A1) returns the same result. 0.520499877813047 =ERF.PRECISE(-0.5) Here the function calculates the integral between -0.5 and 0. Note that the formula =ERF(-0.5) returns the same result. -0.520499877813047 Related LibreOffice functions: ERF ERFC ERFC.PRECISE ODF standard: None Related (or similar) Excel functions: ERF.PRECISE since v.2010. Retrieved from " https://wiki.documentfoundation.org/index.php?title=Documentation/Calc_Functions/ERF.PRECISE&oldid=801881 " Category : Documentation This page was last edited 14:10, 21 May 2025 by Ilmari Lauhakangas . Based on work by Ady and Steve Fanning and others . Please note that all contributions to The Document Foundation Wiki are considered to be released under the Creative Commons Attribution-ShareAlike 3.0 Unported License , unless otherwise specified. This does not include the source code of LibreOffice, which is licensed under the GNU Lesser General Public License ( LGPLv3 ). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy (see Project:Copyrights for details). LibreOffice was based on OpenOffice.org. If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here. Privacy policy About The Document Foundation Wiki Imprint | 2026-01-13T09:29:34 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3Adescription | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:34 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3AhelpArea | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:34 |
https://www.atlassian.com/company/corporate-social-responsibility/report | Sustainability Report: See Our Commitment | Atlassian Close View this page in your language ? All languages Choose your language 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Get it free Products Featured Developers Product Managers IT professionals Business Teams Leadership Teams Featured Developers Product Managers IT professionals Business Teams Leadership Teams See all apps Featured FEATURED APPS Jira Flexible project management Confluence Collaborative knowledge workspace Jira Service Management High-velocity service delivery ATLASSIAN COLLECTIONS Supercharge teamwork seamlessly Jira • Confluence • Loom • Rovo Optimize strategy and outcomes confidently Focus • Talent • Align Deliver service at high-velocity Jira Service Management • Customer Service Management • Assets • Rovo Ship high-quality software fast Rovo Dev • DX • Pipelines • Bitbucket • Compass POWERED BY Rovo AI-powered apps – driven by your team's knowledge. Developers Jira Flexible project management Compass Software catalog for teams Pipelines Scalable CI/CD automation Bitbucket Source code and CI/CD DX Measure productivity and AI impact Rovo Dev Agentic AI for developers Ship high-quality software fast Rovo Dev • DX • Pipelines • Bitbucket • Compass Rovo AI-powered apps – driven by your team's knowledge. Product Managers Jira Flexible project management Confluence Knowledge, all in one place Jira Product Discovery Capture & prioritize ideas Supercharge teamwork seamlessly Jira • Confluence • Loom • Rovo Rovo AI-powered apps – driven by your team's knowledge. IT professionals Jira Service Management High-velocity service delivery Guard Enhanced cloud security Rovo AI-powered apps – driven by your team's knowledge. Business Teams Jira Flexible project management Confluence Knowledge, all in one place Trello Organized & visualized work Loom Quick, async video updates Jira Service Management High-velocity service delivery Customer Service Management Customer experiences reimagined Supercharge teamwork seamlessly Jira • Confluence • Loom • Rovo Rovo AI-powered apps – driven by your team's knowledge. Leadership Teams Focus Enterprise-scale strategic planning Talent Knowledge workforce planning Jira Align Enterprise-wide work planning & value Optimize strategy and outcomes confidently Focus • Talent • Align Rovo AI-powered apps – driven by your team's knowledge. Back Solutions Solutions By use case Team collaboration Strategy and planning Service management Software development By team Software Marketing IT By size Enterprise Small business Startup Non-profit By industry Retail Telecommunications Professional services Government Rovo AI-powered apps – driven by your team's knowledge. Back Why Atlassian Why Atlassian System of Work New Atlassian's blueprint for how teams work together Integrations Connect thousands of apps to your Atlassian products Customers Case studies & stories powered by teamwork FedRAMP Compliant solutions for the public sector Resilience Enterprise-grade & highly performant infrastructure Platform Our deeply integrated, reliable & secure platform Trust center Ensure your data’s security, compliance & availability Back Resources Resources Customer Support Ask questions, report bugs & give us feedback Find Partners Consulting, training & product customization support Atlassian Ascend Resources and support for your transformation Community Learn, connect and grow with the Atlassian Community support General inquiries Product Advice Partner support Enterprise support Technical Support Pricing and Billing Developer support Purchasing & Licensing Resources Project Management Agile Atlassian Learning Get Started Project Collaboration Team Playbook Product Documentation Back Enterprise More + Less - Get it free Jira Flexible project management Jira Service Management High-velocity service delivery Confluence Knowledge, all in one place See all products Get it free Back Get it free Company Customers Careers Careers Home Apply Engineering Careers Early Careers Awards Team Anywhere Team Everyone Candidate Resources Talent Community Back Investors Events Blog Newsroom Press kit Contact More + Less - Atlassian Sustainability Report We’re building a 100-year company together. Atlassian’s seventh Sustainability Report details our progress from July 1, 2024 to June 30, 2025. Get the report Planet People Customers Community Planet We've committed to achieve net zero by 2040. We believe in making long-term climate progress (together). 100 % of U.S. in-office electricity and work-from-home energy use covered by our virtual power purchase agreement (VPPA). Our highlights Mitigating supplier-related emissions is a game of patience and persistence. Out of our top 15 suppliers by emissions without science-based targets that we've engaged, 10 have now set or committed to setting science-based targets, either as part of their agreement with Atlassian or directly with the Science Based Targets initiative. Where we fell short Atlassian’s rapid growth and increased headcount have challenged our efforts to lower business travel emissions, which rose 13% this past year. To course-correct, we adopted a plan for Atlassian’s first internal carbon fee, intended to incentivize emissions reduction and directly fund the purchase of Sustainable Aviation Fuel certificates. Where we’re going Atlassian’s guiding star remains the same: net zero by 2040. But our approach may change as we navigate evolving global regulations and AI’s impact on emissions. We’ll also need to adapt to meet evolving guidance from frameworks like the Science Based Targets initiative. 100 % of U.S. in-office electricity and work-from-home energy use covered by our virtual power purchase agreement (VPPA). People At Atlassian, our people set us apart. We are dedicated to building an inclusive workplace and ensuring every Atlassian feels a sense of belonging. ~10,000 questions through our new agent, NORA. Our highlights We streamlined our new-hire onboarding program by leveraging our own AI-powered tools. “Newlassians” now have NORA, a Rovo agent we developed that successfully answered nearly 10,000 questions and boasts the most weekly active users among all agents within Atlassian. Where we fell short Managers have expressed uncertainty about how to support employees with disabilities and want to make sure their team members have comprehensive assistance. We established accommodation resources in each region. These resources ensure that employees with short-term or long-term medical conditions or disabilities have equitable access to the support, tools, and adjustments they need to fully contribute and thrive in their roles. Where we’re going We’re eyeing new ways to enhance employee engagement and experience, including through the physical work spaces we design and build. We’ll also incorporate AI to help deliver meaningful connections that support modern, distributed ways of working. ~10,000 questions through our new agent, NORA. Customers Transparency and accountability to our customers and stakeholders underpin our approach. We also look to the Atlassian values and UN Guiding Principles on Business and Human Rights. 2x increase in uses of our responsible technology review by teams to assess internal, external, and third-party AI products since fiscal year 2024. Our highlights We embedded our responsible technology review process into the development lifecycle, resulting in over 100 assessments of internal, external, and third-party AI products. These reviews helped us fine-tune how we are developing and deploying AI technology consistently with our Responsible Technology Principles . Where we fell short While we have working groups focused on human rights topics, bringing executive oversight into our governance model remains a gap that we aspire to close. Where we’re going We’re investing deeper in human rights areas like due diligence. We’ll also continue to optimize responsible tech reviews and training for scale and simplicity. These advancements will set us up for future compliance with regulations like the Corporate Sustainability Due Diligence Directive. 2x increase in uses of our responsible technology review by teams to assess internal, external, and third-party AI products since fiscal year 2024. Community The Atlassian Foundation is on a mission to unleash the potential of social impact teams. We empower teams to change lives through education. 1% Atlassian was in the top percentile for partner trust and approachability in the Center for Effective Philanthropy’s 2025 Grantee Perception Report. Our highlights We celebrated the 10-year anniversary of Pledge 1% , a movement we co-founded. We continued to make good on our commitment, including US$12 million in donations through the Atlassian Foundation and free or discounted Atlassian tools for over 12,500 nonprofits. Where we fell short The frequency of extreme weather events continues to intensify, and Atlassian’s reactive response to emergency grant making hasn’t been scaling to meet the community needs of today. Moving forward, we will roll out a proactive approach that invests in recovery and building resilience. Where we’re going With the Sustainability and Atlassian Foundation teams coming together under Legal, we have the opportunity to set a new strategic direction: one that better deploys the full power of Atlassian to take bold bets toward addressing the challenges of the next decade. 1% Atlassian was in the top percentile for partner trust and approachability in the Center for Effective Philanthropy’s 2025 Grantee Perception Report. Read our Sustainability Report “We believe in climate change. We believe in human rights. We believe in the power of belonging. We’re still committed to social and environmental progress in everything we do.” Mike Cannon-Brookes, Atlassian CEO Get the report Want to see how we did in past years? 2024 report → 2023 report → 2022 report → 2021 report → 2020 report → 2019 report → Company Careers Events Blogs Investor Relations Atlassian Foundation Press kit Contact us products Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket See all products Resources Technical support Purchasing & licensing Atlassian Community Knowledge base Marketplace My account Create support ticket Learn Partners Training & certification Documentation Developer resources Enterprise services See all resources Copyright © 2025 Atlassian Privacy Policy Terms Impressum Choose language Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:34 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3Aapply | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:34 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3AdescriptorRadioList | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:34 |
https://ace.atlassian.com/communityevents/ | About | Atlassian Community Events Skip to main content Toggle Navigation Events Connect Atlassian Community Events Join a Chapter Community-led Conferences Online Community Connect with Orbiit Learn Community-Led Classes Company User Groups Earn an Atlassian Certification Become a Champion ACE Speakers Find an ACE Speaker Log in Atlassian Community Events Atlassian Community Events are free, user-led meetups happening in cities all over the world. Meet other Atlassian enthusiasts in your area and benefit from: Valuable content Deep dive into interesting topics through presentations led by other users, Atlassian experts, and even Atlassians! All the swag! Enjoy free food, drink, and swag from Atlassian and local Solution Partners. Networking opportunities Meet other Atlassian fans in your city and learn each others’ best practices. Exclusive discounts Save on certification exams and get early access discounts to Atlassian events and conferences. Bring a friend Community Events are free to attend and all are welcome. Bring a plus one (or three) and grow your local community! The inside scoop Be the first to know about the latest product updates and announcements from Atlassian. Upcoming ACE events Get involved There's an event for everyone. Attend local community events, special events, or industry-specific meet-ups. Or, start a new community event in your city. © 2026 Atlassian Community Events All Rights Reserved ∙ Events ∙ Contact Us ∙ Privacy Policy ∙ Terms and Conditions ∙ Notice at Collection | 2026-01-13T09:29:34 |
https://service.weibo.com/share/share.php?appkey=2152474398&type=3&title=2小时40余个问题，护士节中国援鄂护士与170余位印尼同行“云端”分享抗疫经验&pic=https://www.chinadaily.com.cn/image_e/2020/logo21.jpg&url=https://cn.chinadaily.com.cn/a/202005/12/WS5eba58d8a310eec9c72b8589.html | 分享到微博-微博-随时随地分享身边的新鲜事儿 微博 加入微博一起分享新鲜事 登录 | 注册 140 请登录并选择要私信的好友 300 赞一下这个内容 公开 分享 获取分享按钮 正在发布微博，请稍候 | 2026-01-13T09:29:34 |
http://www.chinadaily.com.cn/world/special_coverage/67b8453ea310c240449d6975 | Russia-Ukraine conflict: Three years on - Chinadaily.com.cn The China Story at your Fingertips OPEN a1 a1 Global Edition ASIA 中文 双语 Français HOME CHINA WORLD BUSINESS LIFESTYLE CULTURE TRAVEL WATCHTHIS SPORTS OPINION REGIONAL FORUM NEWSPAPER China Daily PDF China Daily E-paper MOBILE Editor's note As the Russia-Ukraine conflict enters its fourth year, its ripple effects continue to shape global geopolitics, economies, and everyday lives. Let's examine the evolving dynamics of the conflict, the diplomatic efforts for peace, and the shifting sentiments on the ground and look at the current situation as well as the shifting US stance and EU commitments that may affect the conflict's outcome. All 16 News Updates Ukraine says latest peace talks with US, Europe 'productive' --> KIEV -- Ukraine's talks with US and European partners over the past three days in the US state of Florida were "productive and constructive," Ukraine's top peace negotiator Rustem Umerov said on Sunday. In a Facebook post, Umerov said discussions between Ukraine and the US focused on further development of a 20-point peace plan, aligning positions on multilateral and US security guarantee frameworks for Ukraine, and further development of an economic and prosperity plan. The sides also discussed timelines and the sequencing of next steps. "Ukraine remains fully committed to achieving a just and sustainable peace," Umerov said. "Our shared priority is to stop the killing, ensure guaranteed security, and create conditions for Ukraine's recovery, stability, and long-term prosperity." "Peace must be not only a cessation of hostilities, but also a dignified foundation for a stable future," he said, adding that Ukraine will continue "close coordination" with the US and Europe in the next stages. He added that key European national security advisors joined the discussions to align on a shared strategic approach between Ukraine, the United States and Europe. US presidential special envoy Steve Witkoff issued a similar statement on X, confirming that "a series of productive and constructive meetings" were held over the past three days. The Ukrainian delegation included Umerov, who is also secretary of the National Security and Defense Council of Ukraine, and Andriy Hnatov, chief of the General Staff of the Armed Forces of Ukraine. The US delegation included Witkoff, Trump's son-in-law Jared Kushner and White House staff member Josh Gruenbaum. Over the weekend, Russian President Vladimir Putin's special envoy Kirill Dmitriev held separate talks with US officials in Miami, Florida. "The discussions are proceeding constructively," Dmitriev told reporters Saturday. During his annual year-end press conference in Moscow on Friday, Putin said Russia agrees to end the Ukraine crisis through negotiations, alongside eliminating the root causes, noting that now "the ball is entirely in the court of Ukraine and its European sponsors." Share - WeChat Kremlin says negotiations with Ukraine on hold --> MOSCOW -- Kremlin spokesman Dmitry Peskov said Wednesday that negotiations with Ukraine are on pause. Asked about possible talks between Russian President Vladimir Putin and Ukrainian President Volodymyr Zelensky, Peskov said expert-level discussions could lay the groundwork for any higher-level contact. He stressed that such meetings "cannot be an end in themselves," adding they would not resolve what he called a complex and difficult problem. Russia remains open to resolving the conflict through diplomacy and political dialogue, Peskov said. Share - WeChat Putin-Zelensky meeting not being planned, intense mutual attacks persist --> MOSCOW/KIEV - A meeting between Russian President Vladimir Putin and Ukrainian President Volodymyr Zelensky is not being planned, Russian Foreign Minister Sergei Lavrov said Friday as heavy fighting between Russia and Ukraine dragged on. "Putin is ready to meet with Zelensky when the agenda would be ready for a summit, and this agenda is not ready at all," Lavrov told the US news outlet NBC. His comments came a week after US President Donald Trump met with Putin in the US state of Alaska for talks aimed at ending the three-year conflict in Ukraine. The US president also met with Zelensky and European leaders on Monday. The latest discussions of a potential Putin-Zelensky meeting surfaced after Trump said he called Putin and started working on a bilateral meeting between Putin and Zelensky -- and possibly a trilateral one including himself -- following his talks on Monday. Commenting on the potential meetings, Trump told reporters Friday: "We're going to see if Putin and Zelensky will be working together. You know, that's like oil and vinegar a little bit." "They don't get along too well ... but we'll see, and then we'll see whether or not I would have to be there. I'd rather not. I'd rather have them have a meeting and see how they can do," he said. Lavrov told NBC that Russia has agreed to show flexibility on several issues raised by Trump during his meeting with Putin. The foreign minister previously said that Russia does not reject any formats, either bilateral or trilateral, on resolving the conflict in Ukraine, but noted that any contacts over Ukraine involving top officials need to be prepared "extremely carefully." Zelensky on Friday said Russia is "doing everything" to prevent his meeting with Putin from taking place. "The meeting is one of the components of how to end the war. And since they don't want to end it, they will look for space to (avoid it)," he added. On the frontline, both Russia and Ukraine have intensified attacks on each other's energy infrastructures over the past week. The Russian Defense Ministry said Friday that over the past week, Russian troops captured nine settlements and launched six group strikes targeting the Ukrainian military-industrial complex and energy facilities, an oil refinery, and storage sites of Ukrainian missiles, fuel, rocket-artillery weapons, and long-range drones. During the period, Russian air defense systems shot down 25 guided aerial bombs, 11 rocket projectiles from the US-made HIMARS multiple launch rocket system, as well as 1,500 drones, it said. Zelensky said Thursday that Russia launched one of the largest strikes against Ukraine overnight involving over 570 drones and 40 missiles. A US factory in western Ukraine was targeted, he added. The commander of Ukraine's Unmanned Systems Forces, Robert Brovdi, announced on Friday an attack on the Unecha pumping station in Russia's Bryansk region. The station is a crucial part of the Druzhba oil pipeline, which supplies oil to Hungary and Slovakia. Hungarian Prime Minister Viktor Orban said Friday the pipeline was subjected to repeated Ukrainian attacks over the past weeks. Share - WeChat Ukraine ready for 30-day truce with Russia starting Monday -- FM --> A mother comforts her son in a school basement being used as a shelter after a Russian airstrike on a residential neighborhood in Kyiv, Ukraine, on April 24, 2025. EVGENIY MALOLETKA/AP KYIV -- Ukrainian Foreign Minister Andrii Sybiha said on Saturday that Kyiv is ready for a "full and unconditional" 30-day ceasefire with Russia starting Monday. Sybiha made the statement in a post on social media X, following a meeting with leaders of the "coalition of the willing," an initiative led by Britain and France in support of Ukraine. A durable ceasefire can pave the way to peace negotiations, Sybiha said. Earlier in the day, Ukrainian President Volodymyr Zelensky met with leaders of the coalition, including French President Emmanuel Macron, German Chancellor Friedrich Merz, Polish Prime Minister Donald Tusk and British Prime Minister Keir Starmer. According to the Ukrainian Foreign Ministry, the five leaders also held a "fruitful call" with US President Donald Trump, focusing on peace efforts. Share - WeChat Zelensky says troops active inside Russia --> This handout photograph taken and released on April 5, 2025 by the Ukrainian Presidential Press Service shows the Ukrainian President Volodymyr Zelensky (L) during his meetings with French Chief of the Defence Staff General Thierry Burkhard and Britain Chief of the Defence Staff Admiral Tony Radakin in Kyiv. AFP PHOTO / UKRAINIAN PRESIDENTIAL PRESS SERVICE KYIV — Ukrainian President Volodymyr Zelensky confirmed for the first time on Monday that his country's troops have been active in Russia's Belgorod region, as they seek to protect Ukrainian towns near the border. Ukrainian troops remain in parts of the neighboring Russian region of Kursk eight months after a cross-border incursion, though Russian forces have recaptured much of the lost territory. In his nightly video address, Zelensky said Ukraine's top commander, Oleksandr Syrskyi, had presented a report "on the front line, our presence in the Kursk region and our presence in the Belgorod region". "We continue active operations in the enemy's border areas and this is absolutely justified. The war must return to where it came from," he said. "Our main objective remains the same: to protect our land and our communities in the Sumy and Kharkiv regions from Russian occupiers." It is the first time in the more than three years since the conflict broke out that Zelensky has explicitly mentioned a Ukrainian presence in Belgorod, a region with a population of about 1.5 million people. The Russian military acknowledged facing Ukrainian land attacks in the region last month, at a time when Ukrainian forces were under pressure in Kursk. Zelensky repeated Kyiv's long-held contention that despite Russia's recapturing of areas in Kursk in recent weeks, the operation was successful in that it drew Russian forces away from the conflict's main front line in the eastern Donetsk region. "Due to the entire Kursk operation, we have managed to reduce pressure on other front-line sectors, particularly in the Donetsk region," he said. According to the DeepState military blog, which is considered close to Ukraine's army, troops have occupied a 13-square-kilometer area in the Russian region, near the border village of Demidovka. Russian military bloggers had reported battles in Belgorod region between Russian and Ukrainian troops. Meanwhile, the Ukraine air force said on Tuesday that Russia launched 46 drones and an Iskander-M ballistic missile during an overnight attack. The air force shot down nine drones, with another 31 drones not reaching their targets, likely because of electronic warfare countermeasures, it said on Telegram. It did not say what happened to the remaining six drones or the missile. In another development, the central Ukrainian city of Kryvyi Rih held vigils on Monday to begin three days of mourning for 11 adults and nine children allegedly killed by a Russian missile last week. Friday evening's strike on Zelensky's home city sprayed shrapnel across a dense residential area, including a playground. Russia said the strike had targeted a meeting of Ukrainian service members and foreign trainers and killed up to 85 of them, a claim rejected by Kyiv as disinformation. "No strikes are carried out on social facilities and social infrastructure," Kremlin spokesman Dmitry Peskov told reporters during a briefing on Monday when asked about Friday's attack. Agencies via Xinhua Share - WeChat 'Questions' remain on Ukraine truce idea: Kremlin --> Firefighters work to control a blaze in Kyiv, Ukraine, on Sunday following a Russian missile attack. STATE EMERGENCY SERVICE OF UKRAINE/AFP MOSCOW — The Kremlin said on Monday that Russian President Vladimir Putin still supported the idea of a truce in Ukraine, but many questions remained about how it would work. United States President Donald Trump has been pushing for a ceasefire between Moscow and Kyiv since taking office in January, but his administration has failed to make a breakthrough despite talks with both sides. "Putin does support the idea that a ceasefire is needed, but before that a whole range of questions have to be answered," Kremlin spokesman Dmitry Peskov told reporters on Monday. "These questions are hanging in the air, so far no one has given an answer to them," he added, blaming the lack of progress on "the Kyiv regime's uncontrollability". Meanwhile, Trump has voiced frustration at the slow pace of talks, telling NBC news last month that he was "pissed off" with Putin. On Sunday, he told reporters: "We're talking to Russia. We'd like them to stop. I don't like the bombing. The bombing goes on and on." Last month, Putin rejected a joint US-Ukrainian proposal for an unconditional and full ceasefire, while the Kremlin has made a US-proposed truce in the Black Sea dependent on the West lifting certain sanctions. Ukraine's President Volodymyr Zelensky on Sunday lamented the lack of a US response to Russia's refusal to agree on the ceasefire. "We are waiting for the United States to respond — so far there has been no response," he said. French President Emmanuel Macron echoed Zelensky's calls for a stronger response to Russia. "A ceasefire is needed as soon as possible. And strong action if Russia continues to try to buy time and refuse peace," Macron said on X on Sunday. On the ground, Russia mounted a "massive" missile and drone attack on Ukraine that killed two people and wounded seven others, Zelensky said on Sunday. "The number of Russian air attacks is increasing", which proved that "the pressure on Russia is still insufficient", he said. In Kyiv, explosions were heard in the night and smoke rose from the city on Sunday morning. One person was killed and three people were wounded, the head of the city's military administration, Tymur Tkachenko, wrote on social media. Kyiv Mayor Vitali Klitschko said "the body of a man killed in an enemy attack was discovered in Darnytsia district". A missile strike partially destroyed a building housing state foreign-language broadcasters, the Russian-language Freedom television channel reported, saying that its newsroom had been destroyed. Russia attacked Ukraine with 23 cruise and ballistic missiles and 109 drones during the night, the Ukrainian air force said on Sunday, adding it shot down 13 of the missiles and 40 drones while 54 others caused no damage. In the southern Kherson region, a drone killed a 59-year-old man, while in the northeastern Kharkiv region, near the border with Russia, two people were wounded in an aerial bomb attack, regional officials said. Russia's Defense Ministry said on Sunday that troops "liberated" a village in Ukraine's Sumy region, close to the border with Russia's Kursk region. "A unit of the North group of forces, during offensive actions, liberated the village of Basovka in Sumy region," the ministry said. Ukraine quickly rejected the report. "The enemy continues its disinformation campaign regarding the seizure of settlements in Sumy region or the breakthrough of the border," Andriy Demchenko, spokesman for the State Border Guard Service of Ukraine, told AFP. In Russia's southwest, a Ukrainian drone damaged railway tracks in the Krasnodar region, local authorities said on Monday. "There were no casualties and no fire occurred," the administration of the region said on Telegram. Separately, Ukrainian Economy Minister Yulia Svyrydenko said on Monday that Kyiv is sending officials to Washington in the coming days for further talks on a deal giving the US preferential access to Ukrainian natural resources. AGENCIES VIA XINHUA Share - WeChat Deals reached to protect Black Sea shipping By HENG WEILI in New York --> This photo taken on Oct 9, 2023 shows the White House in Washington, DC, the United States. [Photo/Xinhua] The United States announced agreements on Tuesday with Ukraine and Russia to ensure safe passage in the Black Sea and ban military attacks by the two countries on energy facilities. The White House issued separate statements for Ukraine and Russia, summarizing the three days of talks in Riyadh, Saudi Arabia. Some of the points, such as on the Black Sea, contained the same language for both sides. The statements said that the sides in the three-year-long war have "agreed to ensure safe navigation, eliminate the use of force, and prevent the use of commercial vessels for military purposes in the Black Sea". Both statements concluded that President Donald J. Trump's "imperative that the killing on both sides of the Russia-Ukraine conflict must stop, as the necessary step toward achieving an enduring peace settlement". Russian Foreign Minister Sergei Lavrov said: "We will need clear guarantees. And given the sad experience of agreements with just Kiev, the guarantees can only be the result of an order from Washington to Zelensky and his team to do one thing and not the other." "If the Russians violate this, then I have a direct question for President Trump. If they violate, here is the evidence — we ask for sanctions, we ask for weapons, et cetera," Ukrainian President Volodymyr Zelensky told reporters in Kiev. The Kremlin said in its own statement that the United States also vowed to help restore access for Russian agricultural and fertilizer exports to the world market, reduce the cost of insurance for maritime transportation, and enhance access to ports and payment systems for such transactions. Zelensky said that the agricultural provision was "a weakening of positions and a weakening of sanctions". Lifting restrictions on Russia's agricultural exports would also need the approval of the European Union, which currently is not likely, The New York Times reported. The Black Sea Grain Initiative, originally brokered in July 2022 by the United Nations and Türkiye, sought to guarantee the safe passage of Ukrainian agricultural exports in return for the easing of Western restrictions on Russia's grain and fertilizer business. Moscow did not renew the deal in 2023, claiming that the West failed to uphold its commitments. Russia also wants restrictions lifted on the Russian Agricultural Bank and other financial institutions involved in international trade of food and fertilizers, including reconnecting them to the SWIFT payment system. "We're thinking about all of them right now," Trump said Tuesday of Russia's requests. "There are five or six conditions." The statements also cited agreements to develop measures to enforce the previously reached 30-day ban on strikes against energy infrastructure. One potential sticking point in the agreements is where the EU stands. In a TV interview on Tuesday, Lavrov said that the approach taken by EU leaders on the conflict contradicts Trump's position. Lavrov said the bloc's continued push for NATO membership for Ukraine stems from former US president Joe Biden's decision to push the EU toward a confrontation with Russia. "In other words, they are in direct contradiction to the Trump administration," Lavrov said, noting that Trump, along with Secretary of State Marco Rubio and national security adviser Mike Waltz, had "made it clear that preliminary talks are underway on the parameters of the final settlement and that NATO should be off the table". Lavrov said Biden made "a colossal mistake" by refusing to engage with Russia and insisting that Ukraine join the military bloc, "thereby creating an unacceptable threat for us". Earlier this month, the UK and France discussed sending a military contingent to Ukraine once a ceasefire is reached. Moscow called it a pretext for deploying NATO troops in the country, which it said could lead to a war between the military bloc and Russia. The US and Ukraine also agreed that the United States "remains committed to helping achieve the exchange of prisoners of war, the release of civilian detainees, and the return of forcibly transferred Ukrainian children". Both statements also said that the US, Russia and Ukraine "welcome the good offices of third countries with a view toward supporting the implementation of the energy and maritime agreements". Share - WeChat Cease-fire talks focus on energy sites By HENG WEILI in New York --> This handout photograph released by the Ukrainian Emergency Service early on March 5, 2025, shows a Ukrainian rescuer working to extinguish a fire in a building following an attack from Russia at an undisclosed location in Odesa region. AFP PHOTO / UKRAINIAN EMERGENCY SERVICE The United States and Russia held talks on Monday aimed at producing a 30-day limited cease-fire between Russia and Ukraine — focused on stemming attacks on energy infrastructure — but the two countries in the conflict accused the other of continuing military attacks. One major sticking point in the discussions is what targets would be off-limits to strike. While the White House said "energy and infrastructure" would be covered, the Kremlin said that the agreement referred more narrowly to "energy infrastructure". Ukrainian President Volodymyr Zelensky has said he would like to see infrastructure such as railways and ports protected. Kyiv blamed Moscow for a cyberattack that knocked out the online ticketing system for Ukraine's state railway service, causing long queues at stations on Monday. The talks in the Saudi capital of Riyadh were expected to address some of those differences, as well as a potential pause in attacks in the Black Sea to safeguard commercial shipping. A joint statement on the talks was expected on Tuesday, according to Russia media, which reported that the talks Monday lasted more than 12 hours. "Not every negotiation yields a high-profile document or agreement," Grigory Karasin, part of the Russian team, told reporters during a break in the negotiations. "What matters is maintaining communication and understanding each other's positions. In this regard, we are succeeding." Kremlin spokesman Dmitry Peskov said that the US had suggested the talks focus on ways to protect the Black Sea shipping route. "This was President Trump's suggestion, and President Putin agreed to it," Peskov said. He also said that on the table would be the restoration of a 2022 grain deal that allowed millions of tons of Ukrainian grain to be exported. Russia withdrew from the agreement in 2023, claiming that Western sanctions restricted its own agricultural exports, The New York Times reported. The deal was originally mediated by the United Nations and Türkiye. US President Donald Trump, in speaking to reporters at the White House, said territorial lines and the potential for US ownership of a key nuclear power plant in southern Ukraine also have been part of the talks. Serhii Leshchenko, an adviser to the Ukrainian presidency, said the delegation remained in Riyadh on Monday and expected to meet again with the Americans. The Russian Defense Ministry said that a Ukrainian drone targeted an oil pumping station in southern Russia that serves a pipeline carrying Kazakhstan's Caspian Sea oil to the Russian port of Novorossiisk. It said the drone was downed before it could reach the station. Peskov said Monday that the Russian military has been fulfilling President Vladimir Putin's order to halt attacks on energy facilities for 30 days. He has accused Ukraine of derailing the partial cease-fire with attacks on Russia's energy facilities, including a gas metering station in Sudzha in Russia's Kursk region. Ukraine's military general staff rejected Moscow's accusations and blamed the Russian military for shelling the station, a claim Peskov called "absurd". Zelensky said Sunday evening that "since March 11, a proposal for an unconditional cease-fire has been on the table, and these attacks could have already stopped." Zelensky has emphasized that Ukraine is open to Trump's proposal of a full, 30-day cease-fire. Putin has made a complete cease-fire conditional on a halt of arms supplies to Kyiv and a suspension of Ukraine's military mobilization — demands rejected by Kyiv and its Western allies. Agencies contributed to this story. hengweili@chinadailyusa.com Share - WeChat US, Russia start Ukraine ceasefire talks By Cui Haipei in Dubai --> Negotiators from the United States and Russia sat down on Monday for talks in Saudi Arabia on a partial ceasefire in the Ukraine conflict, hours after a round of negotiations between US and Ukrainian delegations, Russian news reports said. The state Tass and RIA-Novosti news agencies confirmed that negotiations had begun in the capital Riyadh. The meeting is expected to be followed by another contact between US and Ukrainian teams. Originally planned to take place simultaneously to enable shuttle diplomacy -- with the US going back and forth between the delegations -- the talks are now taking place one after the other. The separate meetings are set to discuss details of a pause in long-range attacks from both Russia and Ukraine against energy facilities and civilian infrastructure, as well as a halt on attacks in the Black Sea to ensure safe commercial shipping. Earlier, US special envoy Steve Witkoff voiced optimism that any agreement struck would pave the way for a "full-on" ceasefire. "I think you're going to see in Saudi Arabia on Monday some real progress, particularly as it affects a Black Sea ceasefire on ships between both countries. And from that you'll naturally gravitate to a full-on shooting ceasefire," he told Fox News. But the Kremlin on Sunday downplayed expectations of a rapid resolution. "We are only at the beginning of this path," Kremlin spokesman Dmitry Peskov told Russian state TV. "There are difficult negotiations ahead." Share - WeChat US talks set on Russia-Ukraine war By HENG WEILI in New York --> This photo taken on Aug 15, 2024 shows a Ukrainian tank destroyed during Russian attacks in Toretsk. [Photo/Xinhua] US and Russian delegations will meet in Saudi Arabia on Monday to discuss a potential 30-day cease-fire in the Ukraine-Russia war. The talks will take place a day after representatives of the United States and Ukraine met in Riyadh, the Saudi capital. "We have concluded our meeting with the American team, Ukrainian Defense Minister Rustem Unerov posted on X on Sunday. "The discussion was productive and focused — we addressed key points including energy." Protecting energy facilities, critical infrastructure and allowing navigation in the Black Sea are expected to be discussed Monday. "I think that you're going to see in Saudi Arabia on Monday some real progress, particularly as it affects a Black Sea cease-fire on ships between both countries. And from that, you'll naturally gravitate into a full-on shooting cease-fire," US special envoy Steve Witkoff said in an interview with Fox News on Sunday. A Ukrainian official, speaking on condition of anonymity, said the Ukrainian delegation might hold additional discussions with US officials on Monday, The New York Times reported. The US hopes to reach a broad cease-fire within weeks, targeting a truce agreement by April 20, Bloomberg News reported on Sunday. Despite the continued talks, Russia and Ukraine have significant differences over what a peace deal should include. "Both sides still believe that they can continue the war regardless of the American position," Dmitry Kuznets, a military analyst with the Russian news outlet Meduza told the Times, adding that the two sides' "visions of what an agreement could look like are still infinitely far from each other". US President Donald Trump and Russian President Vladimir Putin agreed last week "that the movement to peace will begin" with the 30-day pause in attacks on energy facilities. But that plan was cast into doubt, with Moscow saying Ukraine hit an oil depot in southern Russia, while Kiev said Russia had struck hospitals and homes and knocked out power to some railways. In a post on social media, Ukrainian President Volodymyr Zelensky said: "This week alone, more than 1,580 guided aerial bombs, almost 1,100 strike drones and 15 missiles of various types were used against our people. New solutions are needed, with new pressure on Moscow to stop both these strikes and this war." Russia's Ministry of Defense said on Sunday it had shot down 59 Ukrainian drones overnight. A moratorium on energy infrastructure strikes could favor Moscow more than Kiev, given it would prevent Ukraine from conducting strikes on Russian oil facilities. Putin has said he wants Ukraine to drop its ambitions to join NATO. Ukraine defines joining NATO as a goal in its constitution and says that membership would be the best security guarantee that it can receive as part of a peace deal. Last month, John Coale, Trump's deputy Ukraine envoy, said the US had not ruled out potential NATO membership for Ukraine — or a return to its pre-2014 borders. US Defense Secretary Pete Hegseth a day earlier had told Ukraine's military allies in Brussels a return to Ukraine's pre-2014 borders was unrealistic and that the US did not see NATO membership for Kiev. Trump has said he does not believe Russia would "allow" Ukraine NATO membership. The UK and France are looking to create a deterrent force of foreign troops, ships and planes in or around Ukraine after a peace deal is signed. But some Russian officials have said they could not accept such a force. Witkoff minimized concerns among NATO allies that Putin might be emboldened by any peace deal in Ukraine. "I just don't see that he wants to take all of Europe. This is a much different situation than it was in World War II," Witkoff said. "And I think the Europeans are beginning to come to that belief, too. But it sort of doesn't matter. "The agenda is stop the killing, stop the carnage. Let's end this thing," he said. Russia wants to control all of the four eastern Ukrainian regions it has claimed as its own, plus the Crimean peninsula. Russia's Kommersant daily cited unnamed sources who attended a private business event with Putin on Tuesday as saying he wants the US to formally recognize the four regions — Luhansk, Donetsk, Zaporizhzhia and Kherson — as part of Russia along with Crimea. Ukraine says it already recognizes that it cannot recapture some occupied Ukrainian territory by force and that it will have to be returned diplomatically over time. Kiev says, however, that it will never recognize Russian sovereignty over Ukrainian territory. Agencies contributed to this story. Share - WeChat In call, Trump floats idea of US running Ukraine's power plants By HENG WEILI in New York --> US President Donald Trump, in a call on Wednesday with Ukrainian President Volodymyr Zelensky, suggested that the United States could take control of Ukraine's power plants to ensure their security, in their discussion about a limited cease-fire between Kiev and Moscow. Trump told Zelensky that the US could be "very helpful in running those plants with its electricity and utility expertise", according to a White House statement from Secretary of State Marco Rubio and national security adviser Mike Waltz. Trump added that "American ownership of those plants could be the best protection for that infrastructure". The power plant discussion included the Zaporizhzhia nuclear facility, Europe's largest, which is currently controlled by Russia, The New York Times reported. "The question was exclusively about the station under temporary occupation," Zelensky said. The two leaders also agreed on a partial cease-fire against energy facilities, according to the statement. Technical teams will meet in Saudi Arabia in the coming days to discuss broadening the cease-fire to the Black Sea on the way to a full cease-fire. They agreed that could be the first step toward the full end of the war and ensuring security. Trump also briefed Zelensky on his conversation Tuesday with Russian President Vladimir Putin. Trump and Zelensky reviewed the battlefield situation in Kursk and agreed to share information closely between their defense staffs as the situation evolved. Zelensky asked for additional air defense systems to protect civilians, particularly Patriot missile systems; Trump agreed to work with him to find what was available, particularly in Europe. While there were signs of progress, Putin and Zelensky still have firm positions on certain issues. According to the Kremlin, Putin made clear to Trump that there must be a halt to foreign military aid and intelligence-sharing as part of any deal. But White House press secretary Karoline Leavitt on Wednesday said that US "intelligence sharing in terms of defense for Ukraine" would continue. In a readout on Tuesday of the talk between Trump and Putin, Leavitt posted: "The leaders agreed that the movement to peace will begin with an energy and infrastructure ceasefire, as well as technical negotiations on implementation of a maritime ceasefire in the Black Sea, full ceasefire and permanent peace." Trump's call with Zelensky was about half as long as his call with Putin, in which the Russian president agreed to not target Ukraine's energy infrastructure but declined to back a full 30-day cease-fire. "Even last night, after Putin's conversation with ... Trump, when Putin said that he was allegedly giving orders to stop strikes on Ukrainian energy, there were 150 drones launched overnight, including on energy facilities," Zelensky said at a news conference with Finnish President Alexander Stubb in Helsinki prior to his call with Trump. Russia responded by saying it had halted its targeting of Ukraine's energy facilities and accused Kiev of attacking equipment near one of its pipelines. "Unfortunately, we see that for now there is no reciprocity on the part of the Kiev regime," Kremlin spokesman Dmitry Peskov said. The White House described the call between Trump and Putin as the first step in a "movement to peace". But there was no indication that Putin backed away from his conditions for a prospective peace deal, which are fiercely opposed by Kiev. Waltz said on social media that he and his Russian counterpart, Yuri Ushakov, agreed Wednesday that their teams would meet soon in Riyadh, Saudi Arabia, "to focus on implementing and expanding the partial cease-fire President Trump secured from Russia". The Russian Defense Ministry said its military had launched seven drones at power facilities related to the military-industrial complex in Ukraine's southern Mykolaiv region, but that it shot them down after receiving Putin's order to not hit energy infrastructure. Moscow accused Ukraine of targeting its energy facility in the Krasnodar region bordering the Crimean Peninsula, which Russia annexed in 2014, several hours after the Putin and Trump talks. The ministry said that three drones targeted oil transfer equipment that feeds the Caspian Pipeline Consortium, causing a fire and leading an oil tank to lose pressure. "It is absolutely clear that we are talking about yet another provocation deliberately concocted by the Kiev regime, aimed at derailing the peace initiatives of the US president," the ministry said. Russia said that its air defenses intercepted 57 Ukrainian drones over the Azov Sea and several Russian regions — the border provinces of Kursk and Bryansk and the nearby regions of Oryol and Tula. Zelensky said that "words of a cease-fire" weren't enough. "If the Russians don't hit our facilities, we definitely won't hit theirs," Zelensky said. "I don't think anybody should make any concessions in terms of helping Ukraine, but rather, assistance to Ukraine should be increased," Zelensky said. "This will be a signal that Ukraine is ready for any surprises from the Russians." Trump has repeatedly complained about the cost of the conflict — the US has sent Ukraine more than $180 billion in military and economic aid since the start of the war in February 2022. Nigel Gould-Davies, senior fellow for Russia and Eurasia at the International Institute for Strategic Studies, said that it was "completely unsurprising" that Putin rejected the cease-fire, adding that it's "imprudent for him to tell President Trump that directly, since Trump has made ending the war a very, very high priority". Zelensky said that one of the most difficult issues in future negotiations would be the issue of territorial concessions. "For us, the red line is the recognition of the Ukrainian temporarily occupied territories as Russian," he said. "We will not go for it." Agencies contributed to this story. Share - WeChat Russia announces final stage of military operation in Kursk region: Peskov --> Kremlin spokesman Dmitry Peskov [Photo/Agencies] MOSCOW - The Russian military operation to retake the Kursk region from Ukrainian armed forces entered its final stage, Kremlin spokesman Dmitry Peskov said Thursday. Russian President Vladimir Putin visited one of the command posts in the Kursk region on Wednesday evening, and was briefed by senior commanders that Russia is close to liberating the territory of the Kursk region from Ukrainian armed forces, reported the TASS news agency. Putin emphasized the urgency of swiftly concluding the operation and establishing a security zone in the region. Chief of the General Staff of the Russian Armed Forces Valery Gerasimov said that the Ukrainian forces in the Kursk region had been isolated and were being systematically destroyed. The large-scale offensive by Ukrainian forces in the Kursk region began in August 2024. Share - WeChat Putin calls for border security zone, urges full liberation of Kursk region --> Russia's President Vladimir Putin addresses commanders as he visits a control center of the Russian armed forces in the Kursk region, Russia, March 12, 2025, in this still image taken from video. [Photo/Agencies] MOSCOW - Russian President Vladimir Putin on Wednesday proposed establishing a security zone along Russia's state border and demanded the complete expulsion of enemy forces from the Kursk region during a visit to a military command center overseeing operations in the area. "Of course, we should think about the future and about creating a security zone along the state border," Putin said, adding that the immediate priority is to "achieve a full defeat of the enemy in the Kursk region and ensure its complete liberation". The Russian president also noted that those enemy soldiers who were taken captive in the Kursk region "should be treated as terrorists in accordance with the laws of the Russian Federation". According to Russian Chief of the General Staff Valery Gerasimov, who reported to Putin during the visit, Russian troops have reclaimed over 1,100 square kilometers of territory in the Kursk region, representing more than 86 percent of the area previously occupied by opposing forces. Share - WeChat China calls for sustainable peace solution to Ukraine crisis By Mo Jingxi --> Foreign Ministry spokeswoman Mao Ning expressed hope on Wednesday that all parties involved in the Ukraine crisis would find a sustainable and lasting peace solution that addresses each party's concerns through dialogue and negotiations. Mao made the remarks after Ukraine expressed readiness to accept the US proposal for a 30-day ceasefire with Russia after talks in Saudi Arabia on Tuesday. "We have taken note of the relevant reports. From the very first day of the (Ukraine) crisis, China has been calling for political settlement through dialogue and negotiation. We have been actively working toward peace and pushing for talks," Mao said. She said China hopes that all parties involved can reach a sustainable solution that addresses each other's concerns through dialogue and negotiation. Share - WeChat Saudi talks focus on Ukraine concessions By CUI HAIPEI in Dubai, UAE --> Delegations from Ukraine and the United States, accompanied by Saudi Arabian officials, hold a meeting in Jeddah, Saudi Arabia, on Tuesday. WANG DONGZHEN/XINHUA High-level delegations from Ukraine and the United States held talks in Saudi Arabia on Tuesday, with Kyiv ready to sign a key minerals deal with the Donald Trump administration and poised to propose a partial cease-fire with Moscow — in an effort to mend ties and restore support from Washington. The three-day meeting in the Red Sea port city of Jeddah started as the US was gauging if Ukraine is willing to make concessions for Trump's efforts to swiftly end Europe's biggest conflict since World War II. Since taking office in January, the US president has engaged directly with Russia, while halting military assistance to and intelligence sharing with Ukraine. Ukrainian presidency chief of staff, Andriy Yermak, who is part of the Ukrainian delegation, said the discussions had begun positively. "The meeting with the US team started very constructively, we continue our work," he wrote on X. China supports all efforts conducive to a peaceful settlement of the Ukraine crisis and hopes all parties can reach a just, lasting and acceptable solution, Foreign Ministry spokeswoman Mao Ning said on Tuesday. China is willing to continue to work with the international community to play a constructive role in the political settlement of the crisis, she told a news briefing in Beijing. However, Ukraine on Tuesday launched its biggest drone attack on Moscow to date, deploying at least 91 drones, killing at least three people, injuring 18 others and causing a short shutdown of the Russian capital's four airports, according to Russian officials. The Jeddah talks were expected to also focus on a minerals deal between the US and Ukraine. Trump has framed the deal as key to continued US support and compensation for $65 billion in US military aid to Ukraine in three years. Previous row On Feb 28, Trump and Vice-President JD Vance accused Ukrainian President Volodymyr Zelensky of avoiding a cease-fire with Russia, and of being ungrateful to the US and Trump for supplying military and other assistance. Zelensky later said he is still willing to sign the deal on critical minerals, though US Secretary of State Marco Rubio said it would not be the focus of Tuesday's meeting. Two senior Ukrainian officials said earlier their delegation is ready to sign the minerals accord and will propose a partial ceasefire covering the Black Sea and long-range missile strikes, as well as the release of prisoners. Rubio signaled that Trump would likely be pleased by such a proposal. "We have to understand the Ukrainian position and have a general idea of what concessions they'd be willing to make. You're not going to get a cease-fire and an end to this war unless both sides make concessions," he told reporters. However, Rubio declined to specify the concessions each side has to make, but said Kyiv would have difficulty reclaiming all of its lost territory. "The Russians can't conquer all of Ukraine, and obviously it'll be very difficult for Ukraine in any reasonable time period to sort of force the Russians back all the way to where they were in 2014," he said. Rubio and Zelensky landed a few hours apart on Monday in Saudi Arabia, but did not meet. They both met with the kingdom's Crown Prince Mohammed bin Salman on Monday. According to a joint statement published on Tuesday by the Saudi state news agency, the crown prince and Zelensky discussed efforts to achieve "sustainable, fair, and comprehensive" peace in Ukraine. Meanwhile, Trump's Middle East Special Envoy Steve Witkoff plans to visit Moscow to meet President Vladimir Putin, a person briefed on the plans said on Monday. Agencies and Xinhua contributed to this story. Share - WeChat Zelensky discusses advancing peace in Ukraine with Saudi Crown Prince --> Saudi Crown Prince Mohammed bin Salman (R) meets with visiting Ukrainian President Volodymyr Zelensky in Jeddah, Saudi Arabia, March 10, 2025. [Photo/Xinhua] KYIV - Ukrainian President Volodymyr Zelensky said overnight Tuesday that he discussed steps toward peace in Ukraine with Saudi Crown Prince Mohammed bin Salman during a meeting in Jeddah, Saudi Arabia. "We had a detailed discussion on the steps and conditions needed to end the war and secure a reliable and lasting peace," Zelensky wrote on X. The talks also covered the release of prisoners, the return of Ukrainian children from Russia, and formats of security guarantees for Ukraine, Zelensky added. Emphasizing that Ukraine's position in upcoming talks with the US team will be "fully constructive", Zelensky expressed hope for "practical outcomes". Economic cooperation, investments and Ukraine's reconstruction were also discussed at the meeting. Zelensky arrived in the Saudi coastal city earlier Monday with the head of the president's office Andriy Yermak, Foreign Minister Andrii Sybiha and Defense Minister Rustem Umerov, ahead of the US-Ukraine talks. Also on Monday, US Secretary of State Marco Rubio arrived in Jeddah and met with the Saudi crown prince. The US-Ukraine meeting, reportedly scheduled for Tuesday, follows a rare shouting match at the White House between Trump and Zelensky in late February, which led to the cancellation of a bilateral minerals agreement and the subsequent suspension of US military aid to Ukraine. Share - WeChat Russia downs 337 Ukrainian drones overnight: Ministry of Defense --> A residential house ablaze after recent Ukraine's drone attack, according the local authorities, in the Moscow region, is seen in this image released March 11, 2025. [Photo/Handout via REUTERS] MOSCOW - Russia's air defense systems shot down 337 Ukrainian drones overnight, the Russian Ministry of Defense announced Tuesday on its Telegram channel. Those drones included 91 shot down over the Moscow region, 126 over Kursk, 38 over Bryansk, and 25 over Belgorod, the ministry said. According to the TASS news agency, it was the largest drone attack Ukraine has launched against Russia in 2025. Share - WeChat 4 killed after Ukraine shells shopping center in Russia's Kursk region --> MOSCOW - Four people were killed in a Ukrainian shelling attack on a shopping center in the village of Belaya in Russia's Kursk Oblast, the region's acting governor said Monday. "The death toll from the shelling of a shopping center in the Belovsky district has risen to four. Two women (born in 1959 and 1988), a 39-year-old man and an 18-year-old boy were killed," Khinshtein said on the messaging app Telegram. According to the governor, Ukrainian forces targeted the Dobrynya shopping center in Belaya on Monday evening. Earlier reports put the death toll at three, with nine others injured, including four teenagers. Share - WeChat US to assess Ukraine's peace stance in Saudi Arabia meeting --> People look at a damaged building two days after Russian shelling in Donetsk, on Sunday. MARIA SENOVILLA/EPA-EFE WASHINGTON — The US side is planning to use Tuesday's meeting with a Ukrainian delegation in Saudi Arabia in part to determine whether Ukraine is willing to make material concessions to Russia to end the conflict, according to two US officials. The US delegation will also be watching for signs that the Ukrainians are serious about improving ties with the Donald Trump administration after a meeting between President Trump and Ukrainian President Volodymyr Zelensky devolved into an argument last month, said one of the officials who requested anonymity. US Secretary of State Marco Rubio was expected to arrive in Jeddah on Monday for the bilateral talks on Tuesday with Ukrainian officials, who will be led by Andriy Yermak, a top Zelensky aide. Rubio will be joined by National Security Adviser Mike Waltz and Trump's Middle East envoy Steve Witkoff. "You can't say 'I want peace', and, 'I refuse to compromise on anything,'" one of the US officials said of the upcoming talks. "We want to see if the Ukrainians are interested not just in peace, but in a realistic peace," said the other official. "If they are only interested in 2014 or 2022 borders, that tells you something." Trump expressed optimism about the talks. "We're going to make a lot of progress, I believe, this week," he told reporters traveling with him on Air Force One. Zelensky traveled to Saudi Arabia on Monday to "continue to work for the sake of peace". He said he hopes the talks between his team and US officials will bear results. Aerial and naval truce Kyiv will propose an aerial and naval cease-fire with Russia during talks, a Ukrainian official told AFP on Monday. "We do have a proposal for a cease-fire in the sky and cease-fire at sea because these are the cease-fire options that are easy to install and to monitor and it's possible to start with them," the official told AFP, speaking on condition of anonymity. US officials had met with Russian officials in the Saudi capital of Riyadh in February for separate bilateral discussions which were focused largely on rebuilding a working relationship after a near-total freeze on official contact under former US president Joe Biden. On the battlefield, Russian troops have been making slow but steady progress in eastern Ukraine, while thousands of Ukrainian troops who stormed into Russia's Kursk region last summer are nearly surrounded. The Ukrainian military said on Monday that Russia launched 176 drones during its overnight attack. The country's armed forces shot down 130 drones and another 42 did not reach their targets, likely due to electronic warfare countermeasures, the military said in a statement on Telegram. In a statement, National Security Council spokesman Brian Hughes said Zelensky had made progress in restoring the US-Ukraine relationship following his acrimonious meeting with Trump on Feb 28. Hanging over Jeddah is the fate of a minerals deal between the US and Ukraine, in which Kyiv wants a security guarantee from Washington in exchange for access to certain mineral resources in Ukraine. Zelensky and Trump were slated to sign that accord during Zelensky's Washington visit, but it was not signed after th | 2026-01-13T09:29:34 |
https://www.atlassian.com/hu/software/jira/guides/issues/tutorials | Tutorials on Jira Work Items | Atlassian Close View this page in your language ? All languages Choose your language 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Get it free Features All Features Rovo in Jira Back Solutions Teams Use cases Company size Teams Marketing Engineering Design Operations IT Use cases Getting started Planning Campaign Management Agile Project Management Program Management Company size Enterprise Back Product guide Templates Templates All Templates Software Development Marketing Design Sales Operations Service Management HR Legal IT Operations Finance Jira Service Management templates Back Pricing More + Less - Get it free Back Get it free Getting started Introduction to Jira Jira for Teams 7 Steps to Get Started in Jira Projects Overview Tutorials Resources Boards Overview Tutorials Resources Work items/issues Overview Tutorials Resources Workflows Overview Tutorials Resources Integrations Overview Tutorials Resources Reports and Dashboards Overview Tutorials Resources Insights Overview Tutorials Resources Permissions Overview Tutorials Resources JQL Overview Tutorials Cheat sheet Resources Navigation Overview Tutorials Resources Automation Overview Tutorials Resources Timeline Overview Tutorials Resources Advanced planning Overview Tutorials Resources Jira Mobile Overview Tutorials Resources More about Jira Editions of Jira Hosting options Jira work items tutorials Create a work item Select “Create” in the top navigation. Your work item will appear in the backlog or board of the project. Find a work item Perform a global search and find a work item across the entire site The search bar in the top navigation enables you to quickly search for work items across the whole instance via work item ID or keywords. You can narrow down your search by project, assignee, and/or status. Perform a contextual search and find a work item in the project’s board, roadmap, or backlog view Search bars can be found in the roadmap, backlog, and board view. Work items would appear in the search results if these work items can be found that particular view. Find a work item in a given project via Work item Navigator Navigate to “Work items” in the sidebar navigation. Toggle between “Basic” or “JQL” modes in the top right of the screen. In Basic mode, you can type keywords in the search bar and/or use the dropdown menus to filter work items by project, work type, status, assignee, and any fields that a work item can have. In JQL mode, you to build structured queries using the Jira Query Language (JQL) to search for work items. Please note that the Work item Navigator is not available by default in team-managed projects. Enable this feature by going to Project Settings > Features > Work item navigator . Add an work type to a project In team-managed projects: Select “Project Settings” in the sidebar navigation on the left, then select “Work types”, then hit “+ Add work type”. Drag and drop the types of fields you’d like to have in the work type, and give each field type a name. You could also set the default values for each field if you’d like. In company-managed projects: How to link work items Open a work item. Select Link work item at the top of the work item modal. Choose the type of work item link (for example, "this work item is blocked by..."). Specify the work item(s) you want to link to by typing the full work item key (for example, ABC-123). Select Link . Configure a work item’s layout Select any work item from your board. In the bottom right of the work item view, select Configure . Drag and drop work item fields in the appropriate regions. Company Careers Events Blogs Investor Relations Atlassian Foundation Press kit Contact us products Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket See all products Resources Technical support Purchasing & licensing Atlassian Community Knowledge base Marketplace My account Create support ticket Learn Partners Training & certification Documentation Developer resources Enterprise services See all resources Copyright © 2025 Atlassian Privacy Policy Terms Impressum Choose language Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:34 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3AsecretTextarea | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:34 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3AwithCustomDescriptorByName | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:34 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3ArowSet | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:34 |
https://wordpress.com/zh-cn/support/github-deployments/ | 在 WordPress.com 上使用 GitHub 部署 – WordPress.com 支持 产品 特色 资源 套餐与定价 登录 从这里开始 菜单 WordPress主机 WordPress for Agencies 成为联盟成员 域名 AI 网站生成器 网站构建器 创建一个博客 电子报 专业电子邮件 网站设计服务 电商版 WordPress Studio 企业级 WordPress 概述 WordPress主题 WordPress 插件 WordPress 样板 Google App 支持中心 WordPress新闻 企业名称生成器 徽标制作工具 发现新文章 热门标签 博客搜索 关闭导航菜单 从这里开始 注册 登录 关于 套餐与定价 产品 WordPress主机 WordPress for Agencies 成为联盟成员 域名 AI 网站生成器 网站构建器 创建一个博客 电子报 专业电子邮件 网站设计服务 电商版 WordPress Studio 企业级 WordPress 特色 概述 WordPress主题 WordPress 插件 WordPress 样板 Google App 资源 支持中心 WordPress新闻 企业名称生成器 徽标制作工具 发现新文章 热门标签 博客搜索 Jetpack 应用程序 了解更多 支持中心 使用指南 课程 论坛 联系 搜索 支持中心 / 使用指南 支持中心 使用指南 课程 论坛 联系 使用指南 / 管理您的账户 / 工具 / 在 WordPress.com 上使用 GitHub 部署 在 WordPress.com 上使用 GitHub 部署 GitHub 部署会将您的 GitHub 存储库直接集成到 WordPress.com 站点上，为您提供一个版本受控的自动化工作流，用于部署对插件、主题或整个站点的更改。本指南涵盖设置流程以及管理已连接存储库的方法。 采用 WordPress.com 商务版和电商版套餐 的站点可使用此功能。如果您有商务版套餐，请确保 将其激活 。对于免费站点和使用个人版及高级版套餐的站点，请 升级您的套餐 以使用此功能。 在此指南中 视频教程 连接存储库 管理部署设置 高级部署 部署您的代码 管理现有连接 部署运行日志 断开存储库连接 断开 WordPress.com 与 GitHub 的连接 有问题？ 询问我们的 AI Assistant 返回顶部 视频教程 此视频为英文内容。 YouTube 提供自动翻译功能，帮助您以母语观看： 开启自动翻译字幕的方法： 播放视频。 点击视频右下角的 ⚙️ 设置 图标。 选择 字幕/CC 。 选择 自动翻译 。 从列表中选择您的首选语言。 使用自动配音（实验功能）的方法： 点击 ⚙️ 设置 图标。 选择 音轨 。 选择您想收听的语言： ℹ️ 翻译和配音由 Google 自动生成，可能不够准确，且自动配音功能仍在测试中，暂未向所有语言开放。 连接存储库 在将 GitHub 存储库部署到您的 WordPress.com 站点之前，您需要先通过以下步骤在两者之间建立连接： 访问您的“站点”页面： https://wordpress.com/sites/ 点击您站点的名称以查看站点概览。 点击“ 部署 ”选项卡。 点击“ 连接存储库 ”按钮。然后，如果您看到列出的存储库，则表示您已连接 GitHub 账户。继续执行步骤 11。 点击“ 安装 WordPress.com 应用程序 ”按钮。 新窗口将打开，如果您尚未登录 GitHub 账户，系统将提示您进行登录。然后，您将看到此屏幕： 点击“ 授权 WordPress.com for Developers ”按钮。 选择您的存储库所在的 GitHub 组织或账户。 选择您要连接的一个或多个存储库： 所有存储库： 选择此选项将授权 WordPress.com 访问所选 GitHub 账户拥有的所有当前 和 未来存储库。这包括只读的公共存储库。 仅特定存储库： 选择此选项将允许您选择 WordPress.com 可以在所选 GitHub 账户上访问的存储库。 选定选项后，点击“ 安装 ”按钮。 新窗口将关闭，您将返回 WordPress.com。您所选的存储库应与关联该存储库的 GitHub 账户一并列出： 点击要连接的存储库旁边的“ 选择 ”。 此时，您应该能在您的“ 已授权的 GitHub 应用程序 ”和“ 已安装的 GitHub 应用程序 ”下看到 WordPress.com for Developers 。 管理部署设置 选定存储库后，您需要调整部署设置： 部署分支： 默认为存储库的默认分支（通常为“ main ”），但可更改为您想使用的分支。 目标目录： 您要在其中部署文件的服务器文件夹。对于插件，目标目录为 /wp-content/plugins/my-plugin-name 。对于主题，目标目录为 /wp-content/themes/my-theme-name 。如需部署部分站点内容（即多个插件或主题），您可以使用 /wp-content 。存储库的内容将与 WordPress 站点在指定目录中的现有内容合并。 自动部署： 您可以通过两种方式将内容部署到 WordPress.com： 自动： 代码一经提交，将部署到您的 WordPress.com 站点。建议对暂存站点启用自动部署。 手动： 代码将在您 请求部署 后部署。建议对生产站点启用手动部署。 部署模式： 存在两种部署类型： 简单： 此模式会将 所有 文件从存储库的分支复制到站点，然后直接部署，不进行任何后处理。 高级： 此模式支持使用工作流脚本，可实现自定义构建步骤，例如安装 Composer 依赖项、执行部署前代码测试以及控制文件部署。非常适合需要 Composer 或 Node 软件的存储库。 更多信息请参阅下文的“高级部署”部分 。 配置完所有设置后，点击“ 连接 ”按钮。您的存储库将被添加： 请注意，您必须触发首次部署， 无论是自动还是手动 。然后，您可以随时通过点击“ 连接存储库 ”按钮连接另一个存储库。 高级部署 借助高级部署功能，您可以在部署前提供工作流脚本来处理存储库中的文件。这将开启诸多可能性，例如检查代码是否符合团队编码规范、运行单元测试、将文件从部署范围中排除、安装依赖项等。开始使用前，请参阅 我们的工作流示例 。 要设置高级部署，请执行以下步骤： 系统将显示一个表单，您可以在其中配置部署。 点击存储库的名称以管理连接。 在右侧的“ 选择您的部署模式 ”下，选择“ 高级 ”。 如果存储库中已包含工作流文件，您可在此处进行选择。系统将检查文件是否存在任何错误。如果未发现错误，请继续执行步骤 7。 您也可以选择“ 创建新工作流 ”选项来添加预配置的工作流文件。选择此选项将覆盖 wpcom.yml 工作流文件（如果您的存储库中已存在）。 点击“ 为我安装工作流 ”按钮，将工作流文件提交到存储库。 添加并验证工作流后，点击“ 更新 ”。您的存储库现在将使用高级部署功能。 部署您的代码 将您的 GitHub 存储库连接到站点后，下一步实际上是部署您的代码。您可通过两种方法进行部署： 自动 和 手动 。 不建议对实时生产站点启用自动部署 ，因为存储库中的任何代码更改都会自动从 GitHub 部署到实时站点。相反，请考虑设置自动部署到 暂存站点 ，待准备就绪后再同步到生产站点。 手动 部署能让您更自主地控制代码变更何时上线，因为每次部署都需要您手动触发。如果您不想使用暂存站点，我们建议您启用手动部署。 要手动触发部署，请执行以下步骤： 访问您的“站点”页面： https://wordpress.com/sites/ 点击您站点的名称以查看站点概览。 点击“ 部署 ”选项卡。 点击您要部署的存储库上的省略号菜单 (⋮)。 选择“ 触发手动部署 ”。您应该会看到一条横幅通知提示“部署运行已创建”，并且部署状态将变更为“已排队”。 等待部署完成（状态将变更为“已部署”）。 再次点击省略号菜单 (⋮)，然后选择“ 查看部署运行 ”。 部署运行日志 会显示作者和已部署的提交信息。如果您点击部署运行条目，则可以查看更多信息。 管理现有连接 要管理您的现有 GitHub 存储库连接，请执行以下步骤： 访问您的“站点”页面： https://wordpress.com/sites/ 点击您站点的名称以查看站点概览。 点击“ 部署 ”选项卡。 然后，您应该会看到连接列表。 当 GitHub 存储库与您的站点之间存在至少一个连接时，系统将显示连接列表。该列表包含每个连接的相关信息，例如存储库名称和分支、最后部署到站点的提交信息、发生时间、代码放置位置、部署运行耗时及其状态。 点击省略号菜单 (⋮) 后，您还可以执行以下额外操作： 触发手动部署： 在已配置分支的最新提交信息上 启动部署运行 。 查看部署运行： 打开已连接存储库的 部署运行日志 视图。 配置连接： 打开存储库的 管理连接视图 。 断开存储库连接： 移除存储库与站点之间的连接。 部署运行日志 部署运行日志可提供每次部署的详细分步记录，无论是自动触发还是手动触发。这些日志可帮助您追踪更改、监控部署状态并排查出现的任何问题。通过访问最近 30 天内最后 10 次运行的日志，您可以轻松查看每次部署期间发生的情况，并确保一切运行顺畅。 要检查部署日志，请执行以下步骤： 访问您的“站点”页面： https://wordpress.com/sites/ 点击您站点的名称以查看站点概览。 点击“ 部署 ”选项卡。 点击要查看其日志的存储库旁边的省略号菜单 (⋮)。 选择“ 查看部署运行 ”。 部署运行 列表视图会显示已部署到站点的提交信息、部署状态、日期和持续时间。 点击运行条目的任意位置即可展开并查看有关该部署的更多信息。 日志记录了所有已执行的命令，包括从 GitHub 获取代码，以及将其放置在目标目录中。您可以通过点击“ 显示更多 ”来展开日志行以查看更多信息。 断开存储库连接 在您断开 GitHub 存储库与您站点的连接后，将来对该存储库的任何更改都不会再影响您的站点。默认情况下，已部署的文件仍会保留在您的站点上，但您可以选择在断开连接的过程中将其删除。 要删除存储库，请执行以下步骤： 访问您的“站点”页面： https://wordpress.com/sites/ 点击您站点的名称以查看站点概览。 点击“ 部署 ”选项卡。 点击存储库上的省略号菜单 (⋮)。 选择“ 断开存储库连接 ”。 屏幕上将出现一个对话框窗口。点击开关即可将关联文件从站点中移除。 点击“ 断开存储库连接 ”，以关闭对话框并断开存储库连接。 请注意， WordPress.com for Developers 仍会出现在您的 已安装的 GitHub 应用程序 和 已授权的 GitHub 应用程序 中。这是因为 WordPress.com 仍然可以访问该存储库，但连接已被删除。 断开 WordPress.com 与 GitHub 的连接 您还可以选择撤销 WordPress.com 对您的 GitHub 账户的访问权限。您随时可通过访问 GitHub 上的 应用程序设置 来执行此操作。 要撤销授权应用程序对您 GitHub 账户的访问权限，请执行以下步骤： 转到“ 已授权的 GitHub 应用程序 ”。 点击 WordPress.com for Developers 旁边的“ 撤销 ”。 点击“ 我已知晓，撤销访问权限 ”按钮。 即使您撤销了已授权的应用程序访问权限，代码仍然可以部署，因为 WordPress.com for Developers 应用程序仍然安装在所选账户上。 要撤销对 WordPress.com 安装的访问权限并禁用向您的 WordPress.com 站点部署代码的功能，请执行以下步骤： 转到“ 已安装的 GitHub 应用程序 ”。 点击 WordPress.com for Developers 旁边的“ 配置 ”。 在“ 危险区 ”区域中，点击“ 卸载 ”，然后在系统提示时点击“ 确定 ”。 从授权应用程序列表中移除 WordPress.com 并不 意味着这些存储库将被删除或停止工作；在您撤销 WordPress.com 的访问权限后，您的存储库仍将存在于 GitHub 上，但 WordPress.com 将不能再部署代码。 相关指南 使用 WP Admin 仪表盘 为您的网站添加徽标 流量设置 操作栏 在此指南中 视频教程 连接存储库 管理部署设置 高级部署 部署您的代码 管理现有连接 部署运行日志 断开存储库连接 断开 WordPress.com 与 GitHub 的连接 有问题？ 询问我们的 AI Assistant 返回顶部 找不到所需内容？ 联系我们 通过我们的 AI 助手获得答案，付费套餐用户还可享受全天候的专家人工支持。 在我们的论坛中提问 浏览问题，并从其他资深用户处获得解答。 Copied to clipboard! WordPress.com 产品 WordPress主机 WordPress for Agencies 成为联盟成员 域名 AI 网站生成器 网站构建器 创建一个博客 专业电子邮件 网站设计服务 WordPress Studio 企业级 WordPress 特色 概述 WordPress主题 WordPress 插件 WordPress 样板 Google App 资源 WordPress.com 博客 企业名称生成器 徽标制作工具 WordPress.com 阅读器 可访问性 删除订阅 帮助 支持中心 使用指南 课程 论坛 联系 开发者资源 公司 关于 新闻 服务条款 隐私政策 请勿出售或分享我的个人信息 面向加州用户的隐私声明 Deutsch Español Français Bahasa Indonesia Italiano Nederlands Português do Brasil Svenska Türkçe Русский العربية עִבְרִית 日本語 한국어 简体中文 繁體中文 English Deutsch Español Français Bahasa Indonesia Italiano Nederlands Português do Brasil Svenska Türkçe Русский العربية עִבְרִית 日本語 한국어 简体中文 繁體中文 English 移动应用程序 在以下位置下载 应用中心 在以下位置获取 Google Play 社交媒体 Facebook 上的 WordPress.com X (Twitter) 上的 WordPress.com Instagram 上的 WordPress.com YouTube 上的 WordPress.com Automattic Automattic 与我们合作 正在加载评论... 撰写评论... 电子邮箱地址（必填） 显示名称（必填） 网站地址 WordPress.com 支持 注册 登录 复制短链接 举报此内容 管理订阅 | 2026-01-13T09:29:34 |
http://www.eguizhou.gov.cn/ | Guizhou, China Facebook X Contact --> HOME ABOUT Overview Regions Photos GOVERNMENT Officials Departments MEDIA CENTER News Specials Videos Reports in PDF BUSINESS Why Guizhou Guide Opportunities Policies Parks Industries Enterprises TRAVEL Attractions Dining Transportation Hotels Shopping Entertainment Guizhou in Foreign Eyes Agencies CULTURE What's on Ethnic Culture People LIVING Visas Medical Services Education Marriage Adoption Numbers Tips and Info 中文 Facebook SEARCH Share your views on 2026 China's Government Work Report Happy New Year Join 56 ethnic-pandas on a cultural fashion tour Revel in Guizhou's autumn splendor Big Data Expo 2025 Happy National Day NEWS Dong New Year celebrations showcase ancient traditions A video of recent Dong New Year celebrations in Zhaoxing Dong village, Guizhou province, showcases the community's long-standing cultural traditions. Cold front coats Guizhou mountains in rime Qinglong: Diverse passions, shared stage On the journey to modernization BUSINESS Deft push to develop big data, computing power industries Develop baijiu tailored to international consumers, deputy says Toy manufacturing shifting inland due to rising labor costs Guizhou export sees strong competitiveness in Southeast Asia CULTURE Intl Weiqi masters invitational tournament held in Guiyang Blockbuster movie makes Guiyang cinema moviegoer hotspot Cheng Yan: Bridge cultures between Guizhou and Hong Kong Grand Song of Dong shines in HK TRAVEL Bedrock bears marks of ancient glacial activity Cinema boosts Guizhou tourism with extraordinary audiovisual experience Experience Guizhou's gifts Guiyang and Gui'an enter flower viewing season GUIZHOU IN FOREIGN EYES US photographer praises Huajiang Grand Canyon Bridge Educational bonds with ASEAN strengthened Hot and cold, but mostly cool Liupanshui offers unique winter experience, short-sleeve skiing Visas Medical services Education Marriage Adoption Numbers Videos On the journey to modernization Reports Specials China (Guizhou) Intl Alcoholic Beverages Expo Big Data Expo 2025 Regions Overview Guiyang Guian New Area Liupanshui Anshun Qianxinan Qiandongnan Qiannan Zunyi Tongren Bijie About Overview Regions Photos Government Officials Departments Media Center News Specials Videos Reports in PDF Business Why Guizhou Guide Opportunities Policies Parks Industries Enterprises Travel Attractions Dining Transportation Hotels Shopping Entertainment Guizhou in Foreign Eyes Agencies Culture What's on Ethnic Culture People Living Visas Medical Services Education Marriage Adoption Numbers Tips and Info Links > 中国日报贵州频道 贵州省人民政府网 Guiyang Guian New Area Liupanshui Anshun Qianxinan Qiandongnan Qiannan Zunyi Tongren Bijie Beijing Shanghai Copyright © The Publicity Department of the CPC Guizhou Provincial Committee. All rights Reserved. 京ICP备13028878号-8 | 2026-01-13T09:29:34 |
https://www.ecns.cn/hd/2026-01-04/detail-iheymvap1612569.shtml#10 | International ice sculpture competition heats up in Harbin --> 中文 Home News Ecns Wire Business Travel Photo Video Voices RIGHT BG LINE Text: A A A Print Photo International ice sculpture competition heats up in Harbin ( 1 /10) 2026-01-04 10:20:27 Ecns.cn Editor :Zhao Li Members of a team from St. Petersburg, Russia, work on an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026.(Photo: China News Service/Zhao Yuhang) The competition has attracted 38 teams and 76 artists from 12 countries, including Australia, Poland, France, the United States, Spain, India and China. A Russian contestant creates an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026. (Photo: China News Service/Zhao Yuhang) A contestant from Mongolia works on an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026. (Aerial photo) (Photo: Yu Kun) A contestant from Mongolia works on an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026. (Aerial photo) (Photo: Yu Kun) Members of a China?Russia joint team carve an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, Jan. 3, 2026. (Aerial photo/ Yu Kun) The work was created to mark the 10th anniversary of the sister-city relationship between Harbin and Murmansk, Russia. (Photo: Yu Kun) A Russian contestant creates an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026. (Photo: China News Service/Zhao Yuhang) A Russian contestant creates an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026. (Photo: China News Service/Zhao Yuhang) A Spanish contestant works on an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026. (Photo: China News Service/Zhao Yuhang) A Spanish contestant works on an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026. (Photo: China News Service/Zhao Yuhang) A Russian contestant creates an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026. (Photo: China News Service/Zhao Yuhang) Previous The competition has attracted 38 teams and 76 artists from 12 countries, including Australia, Poland, France, the United States, Spain, India and China.--> The work was created to mark the 10th anniversary of the sister-city relationship between Harbin and Murmansk, Russia. (Photo: Yu Kun)--> Next (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) LINE More Photo Mourners pay tribute to Crans-Montana bar fire victims Venezuelan leader Maduro brought to New York Highlights of Chinese President Xi Jinping's 2026 New Year message Beijing-Tangshan intercity railway starts full-line operation First 'Grassland curling' attracts 350 competitors China launches two new satellites for space target detection test ${visuals_2} ${visuals_3} More Video (W.E. Talk) Experts on 2026: China's 15th Five-Year Plan significant for the World (W.E. Talk) Experts look to 2026: Seizing opportunities amid crises, forging ahead after breakthroughs The Awkward Chronicles of Uncle Sam: Claimed Glory, Met Chaos The Dunhuang Flying Dancers in the 1,360°C kiln fire The Awkward Chronicles of Uncle Sam: Tariff Bullying and Backfire (W.E. Talk) Experts' review on 2025: China serves as a stabilizing force in a world of turmoil and chaos ${new_video_hd2} ${new_video_hd3} LINE Media partners: People's Daily | Xinhua | CGTN | China Daily Back to top About Us | Jobs | Contact Us | Privacy Policy Copyright ©1999-2026 Chinanews.com. All rights reserved. Reproduction in whole or in part without permission is prohibited. [ 网上传播视听节目许可证（0106168) ] [ 京ICP证040655号 ] [ 京公网安备 11010202009201号 ] [ 京ICP备05004340号-1 ] --> --> | 2026-01-13T09:29:34 |
https://reports.jenkins.io/jelly-taglib-ref.html#hudson.3Aaggregated-failed-tests | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:34 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3Aslave-mode | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:34 |
https://reports.jenkins.io/jelly-taglib-ref.html#header | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:34 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3Atextbox | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:34 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3Aadvanced | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:34 |
https://wordpress.com/it/support/distribuzioni-github/ | Utilizza le distribuzioni GitHub su WordPress.com – Supporto Prodotti Funzionalità Risorse Piani e prezzi Accedi Comincia ora Menu Hosting WordPress WordPress per agenzie Diventa un affiliato Nomi di dominio Costruttore di siti IA Costruttore di siti web Crea un blog Newsletter Professional Email Servizi di progettazione di siti Commerce WordPress Studio WordPress Enterprise Panoramica Temi WordPress Plugin WordPress Pattern WordPress Google Apps Centro di supporto Novità di WordPress Generatore di nomi commerciali Costruttore di loghi Scopri nuovi articoli Tag più popolari Cerca blog Chiudi il menu di navigazione Comincia ora Registrati Accedi Informazioni Piani e prezzi Prodotti Hosting WordPress WordPress per agenzie Diventa un affiliato Nomi di dominio Costruttore di siti IA Costruttore di siti web Crea un blog Newsletter Professional Email Servizi di progettazione di siti Commerce WordPress Studio WordPress Enterprise Funzionalità Panoramica Temi WordPress Plugin WordPress Pattern WordPress Google Apps Risorse Centro di supporto Novità di WordPress Generatore di nomi commerciali Costruttore di loghi Scopri nuovi articoli Tag più popolari Cerca blog App Jetpack Scopri di più Centro di supporto Guide Corsi Forum Contatti Ricerca Centro di supporto / Guide Centro di supporto Guide Corsi Forum Contatti Guide / Strumenti / Utilizza le distribuzioni GitHub su WordPress.com Utilizza le distribuzioni GitHub su WordPress.com GitHub Deployments integra i tuoi repository GitHub direttamente con il tuo sito WordPress.com, offrendoti un flusso di lavoro automatizzato e controllato per distribuire plugin, temi o modifiche complete al sito. Questa guida descrive il processo di configurazione e mostra come gestire i repository connessi. Questa funzionalità è disponibile sui siti con i piani WordPress.com Business e Commerce . Se disponi di un piano Business, assicurati di attivarlo. Per i siti gratuiti e quelli con piano Personal e Premium, aggiorna il tuo piano per accedere a questa funzione. In questa guida Tutorial video Connetti un repository Gestisci le impostazioni di distribuzione Distribuzione avanzata Distribuisci il codice Gestisci le connessioni esistenti Log di esecuzione della distribuzione Disconnetti un repository Disconnetti WordPress.com da GitHub Hai una domanda? Chiedi al nostro Assistente IA Torna in cima Tutorial video Questo video è in inglese. YouTube offre funzioni di traduzione automatica per permetterti di guardarlo nella tua lingua: Per visualizzare i sottotitoli tradotti automaticamente: Riproduci il video. Fai clic su ⚙️ Impostazioni (in basso a destra nel video). Seleziona Sottotitoli/CC . Scegli Traduzione automatica . Seleziona la lingua che preferisci. Per ascoltare il doppiaggio automatico (sperimentale): Fai clic su ⚙️ Impostazioni . Seleziona Traccia audio . Scegli la lingua in cui vuoi ascoltare il video. ℹ️ Le traduzioni e i doppiaggi sono generati automaticamente da Google, potrebbero non essere perfetti e il doppiaggio automatico è ancora in fase di test, quindi potrebbe non essere disponibile per tutte le lingue. Connetti un repository Prima di poter distribuire un repository GitHub sul tuo sito WordPress.com, devi configurare la connessione tra i due seguendo questi passaggi: Visita la tua pagina Siti: https://wordpress.com/sites/ Fai clic sul nome del tuo sito per visualizzare la panoramica del sito. Fai clic sulla scheda Distribuzioni . Fai clic sul pulsante “ Connetti “. Quindi, se vedi i repository elencati, hai già connesso il tuo account GitHub. Passa al punto 11. Fai clic sul pulsante “ Installa l’app WordPress.com “. Si aprirà una nuova finestra e ti verrà chiesto di accedere al tuo account GitHub se non l’hai già fatto. Quindi vedrai questa schermata: Fai clic sul pulsante “ Autorizza WordPress.com per sviluppatori “. Seleziona l’organizzazione o l’account GitHub in cui si trova il tuo repository. Seleziona quale/quali repository desideri connettere: Tutti i repository: selezionando questa opzione si garantirà a WordPress.com l’accesso a tutti i repository attuali e future possedute dall’account GitHub selezionato. Sono inclusi i repository pubblici di sola lettura. Seleziona solo repository: selezionando questa opzione potrai scegliere a quali repository WordPress.com può accedere sull’account GitHub selezionato. Dopo aver selezionato un’opzione, fai clic sul pulsante Installa . La nuova finestra si chiuderà e tornerai su WordPress.com. Il/i repository selezionate dovrebbero essere elencati insieme all’account GitHub associato a tale repository: Fai clic su Seleziona accanto al repository da connettere. A questo punto, dovresti vedere WordPress.com per sviluppatori sotto le tue App GitHub autorizzate e le App GitHub installate . Gestisci le impostazioni di distribuzione Dopo aver selezionato un repository, dovrai modificare le impostazioni di distribuzione: Ramo di distribuzione: ha come valore predefinito il ramo predefinito del repository (in genere principale ), ma può essere modificato nel ramo che vuoi utilizzare. Directory di destinazione: la cartella del server in cui vuoi distribuire i file. Per i plugin, sarà /wp-content/plugins/my-plugin-name . Per i temi, sarà /wp-content/themes/my-theme-name . Per una distribuzione parziale del sito (ad esempio, più plugin o temi), puoi usare /wp-content . I contenuti di un repository verranno accorpati con i contenuti esistenti del sito WordPress nella directory specificata. Distribuzioni automatiche: ci sono due modi per effettuare le distribuzioni su WordPress.com: Automatico: una volta eseguito il commit, il codice verrà distribuito sul sito WordPress.com. Le distribuzioni automatiche sono consigliate per i siti di staging. Manuale: il codice verrà distribuito una volta richiesta la distribuzione . Le distribuzioni manuali sono consigliate per i siti di produzione. Modalità di distribuzione: esistono due tipi di distribuzione: Semplice: questa modalità copierà tutti i file da una sezione del repository al sito e li distribuirà senza post-elaborazione. Avanzate: con questa modalità, è possibile utilizzare uno script di flusso di lavoro, che consente di personalizzare le fasi di compilazione, come l’installazione delle dipendenze Composer, l’esecuzione di test del codice prima della distribuzione e il controllo della distribuzione dei file. Ideale per i repository che necessitano di software Composer o Node. Per ulteriori informazioni, vedi Distribuzione avanzata di seguito . Una volta configurate tutte le impostazioni, fai clic sul pulsante Connetti . Il tuo repository verrà aggiunto: È necessario attivare la prima distribuzione, automaticamente o manualmente .È quindi possibile connettere un altro repository in qualsiasi momento facendo clic sul pulsante “ Connetti repository “. Distribuzione avanzata Con la distribuzione avanzata è possibile fornire uno script del flusso di lavoro per elaborare i file nel repository prima della distribuzione. Questo apre molte possibilità, come controllare il codice per assicurarsi che soddisfi gli standard di codifica del team, eseguire test unitari, escludere file dalla distribuzione, installare dipendenze e molto altro ancora. Per iniziare, dai un’occhiata alle nostre ricette per flussi di lavoro . Per impostare la distribuzione avanzata: Verrà visualizzato un modulo in cui è possibile configurare la distribuzione. Fai clic sul nome del repository per gestire la connessione. Sul lato destro, in “ Scegli la tua modalità di distribuzione “, scegli Avanzata . Se il repository contiene già un file del flusso di lavoro, puoi selezionarlo qui. Il sistema controllerà il file per eventuali errori. Se non vengono trovati errori, vai al passaggio 7. È inoltre possibile selezionare l’opzione “ Crea nuovo flusso di lavoro ” per aggiungere un file di flusso di lavoro preconfigurato. Se scegli questa opzione, il file del flusso di lavoro wpcom.yml verrà sovrascritto se già esistente nel repository. Fai clic sul pulsante “ Installa flusso di lavoro per me ” per eseguire il commit del file del flusso di lavoro nel repository. Una volta aggiunto e verificato un flusso di lavoro, fai clic su Aggiorna . Il tuo repository ora utilizzerà la distribuzione avanzata. Distribuisci il codice Dopo aver connesso il repository GitHub a un sito, il passaggio successivo è quello di distribuire il codice. Sono disponibili due metodi di distribuzione: Automatico e Manuale . Le distribuzioni automatiche non sono raccomandate per i siti di produzione live, poiché qualsiasi modifica del codice nel repository viene distribuita automaticamente da GitHub al sito live. Una volta pronto, puoi configurare la distribuzione automatica su un sito di staging e sincronizzarla con il sito di produzione. Le distribuzioni manuali ti danno più controllo su quando le modifiche del codice vengono inviate in tempo reale, poiché dovrai attivare manualmente ogni distribuzione. Se non vuoi utilizzare un sito di staging, ti consigliamo di eseguire le distribuzioni manuali. Per avviare manualmente una distribuzione: Visita la tua pagina Siti: https://wordpress.com/sites/ Fai clic sul nome del tuo sito per visualizzare la panoramica del sito. Fai clic sulla scheda Distribuzioni . Fai clic sul menu con i tre puntini (⋮) nel repository che vuoi distribuire. Scegli “ Avvia distribuzione manuale “. Dovresti vedere un banner di notifica che dice “Esecuzione della distribuzione creata” e lo stato della distribuzione cambierà in “In coda”. Attendi il completamento della distribuzione (lo stato cambierà in “Distribuito”). Fai di nuovo clic sul menu con i tre puntini (⋮) e scegli “ Visualizza esecuzioni di distribuzione “. Nel log di esecuzione della distribuzione vengono visualizzati l’autore e il commit distribuito. Se fai clic sulla voce di esecuzione della distribuzione, puoi visualizzare ulteriori informazioni. Gestisci le connessioni esistenti Per gestire le connessioni esistenti al repository GitHub: Visita la tua pagina Siti: https://wordpress.com/sites/ Fai clic sul nome del tuo sito per visualizzare la panoramica del sito. Fai clic sulla scheda Distribuzioni . Dovresti quindi vedere l’elenco delle connessioni. L’elenco delle connessioni viene mostrato se esiste almeno una connessione tra un repository GitHub e il tuo sito. L’elenco include le informazioni rilevanti per ogni connessione, come il nome del repository e il ramo, l’ultimo commit distribuito su un sito, la data in cui è avvenuto, il luogo in cui è stato posizionato il codice, la durata della distribuzione e il relativo stato. Sono disponibili azioni aggiuntive dopo aver fatto clic sul menu con i tre puntini (⋮): Avvia distribuzione manuale: avvia un’esecuzione della distribuzione sull’ultimo commit del ramo configurato. Vedi esecuzioni della distribuzione: apre la visualizzazione log di esecuzione della distribuzione per il repository connesso. Configura connessione: apre la vista gestisci connessione per il repository. Disconnetti repository: rimuove la connessione tra repository e sito. Log di esecuzione della distribuzione I log di esecuzione della distribuzione forniscono un record dettagliato e puntuale di ogni distribuzione, indipendentemente dal fatto che venga attivata automaticamente o manualmente. Questi log ti aiutano a tenere traccia delle modifiche, a monitorare lo stato della distribuzione e risolvere eventuali problemi. Con l’accesso ai log delle ultime 10 esecuzioni nell’arco di 30 giorni, puoi facilmente rivedere cosa è successo durante ogni distribuzione e assicurarti che tutto funzioni senza intoppi. Per controllare i log di una distribuzione: Visita la tua pagina Siti: https://wordpress.com/sites/ Fai clic sul nome del tuo sito per visualizzare la panoramica del sito. Fai clic sulla scheda Distribuzioni . Fai clic sul menu con i puntini di sospensione (⋮) accanto al repository per il quale vuoi visualizzare i log. Seleziona “ Visualizza esecuzioni della distribuzione “. La vista elenco delle distribuzioni mostra i commit distribuiti sul sito, lo stato della distribuzione, la data e la durata. Fai clic in un punto qualsiasi di una sequenza per espandere e visualizzare ulteriori informazioni sulla distribuzione. I log forniscono un record di tutti i comandi eseguiti, dal recupero del codice da GitHub al suo posizionamento nella directory di destinazione. Puoi espandere le righe di log per visualizzare ulteriori informazioni facendo clic su “ mostra di più “. Disconnetti un repository Quando disconnetti un repository GitHub dal tuo sito, qualsiasi modifica futura al repository non avrà più impatto sul tuo sito. Per impostazione predefinita, i file distribuiti rimangono sul tuo sito, ma hai la possibilità di rimuoverli durante il processo di disconnessione. Per rimuovere un repository: Visita la tua pagina Siti: https://wordpress.com/sites/ Fai clic sul nome del tuo sito per visualizzare la panoramica del sito. Fai clic sulla scheda Distribuzioni . Fai clic sul menu con i tre puntini (⋮) nel repository. Seleziona “ Disconnetti repository “. Apparirà una finestra di dialogo. Fai clic sul pulsante per rimuovere i file associati dal sito. Fai clic su “ Disconnetti repository ” per chiudere la finestra di dialogo e disconnettere il repository. Nota che WordPress.com per sviluppatori verrà comunque visualizzato nelle tue app GitHub installate e nelle tue app GitHub autorizzate . Questo perché WordPress.com ha ancora accesso al repository, ma la connessione è stata eliminata. Disconnetti WordPress.com da GitHub Puoi anche decidere di revocare l’accesso di WordPress.com al tuo account GitHub. Puoi farlo in qualsiasi momento visitando le impostazioni delle tue applicazioni su GitHub. Per revocare l’accesso autorizzato dell’app al tuo account GitHub: Vai alle app GitHub autorizzate . Fai clic su Revoca accanto a WordPress.com per sviluppatori . Fai clic sul pulsante “ Ho capito, revoca l’accesso “. Anche se revochi l’accesso autorizzato all’app, il codice può comunque essere distribuito perché l’app WordPress.com per sviluppatori rimane installata sugli account selezionati. Per revocare l’accesso all’installazione di WordPress.com e disabilitare la possibilità di distribuire codice al tuo sito WordPress.com: Vai su App GitHub installate . Fai clic su Configura accanto a WordPress.com per sviluppatori . Nell’area Zona di pericolo , fai clic su Disinstalla , quindi fai clic su OK quando richiesto. La rimozione di WordPress.com dall’elenco delle app autorizzate non comporta la cancellazione o il blocco dei repository; questi ultimi continueranno a esistere su GitHub anche dopo la revoca dell’accesso a WordPress.com, ma WordPress.com non potrà più distribuire codice. Guide correlate Connessione a SSH 4 minuti per la lettura Accedere al database del tuo sito 3 minuti per la lettura Abilitare la modalità di difesa 2 minuti per la lettura In questa guida Tutorial video Connetti un repository Gestisci le impostazioni di distribuzione Distribuzione avanzata Distribuisci il codice Gestisci le connessioni esistenti Log di esecuzione della distribuzione Disconnetti un repository Disconnetti WordPress.com da GitHub Hai una domanda? Chiedi al nostro Assistente IA Torna in cima Non hai trovato quello di cui avevi bisogno? Contattaci Ottieni risposte dal nostro assistente IA, con accesso al supporto di esperti umani 24 ore su 24, 7 giorni su 7, sui piani a pagamento. Fai una domanda nel nostro forum Sfoglia le domande e ottieni risposte da altri utenti esperti. Copied to clipboard! WordPress.com Prodotti Hosting WordPress WordPress per agenzie Diventa un affiliato Nomi di dominio Costruttore di siti IA Costruttore di siti web Crea un blog Professional Email Servizi di progettazione di siti WordPress Studio WordPress Enterprise Funzionalità Panoramica Temi WordPress Plugin WordPress Pattern WordPress Google Apps Risorse Blog di WordPress.com Generatore di nomi commerciali Costruttore di loghi Lettura di WordPress.com Accessibilità Rimuovi abbonamenti Aiuto Centro di supporto Guide Corsi Forum Contatti Risorse per gli sviluppatori Società Informazioni Stampa Termini di servizio Informativa sulla privacy Non vendere o condividere le mie informazioni personali Nota sulla privacy per utenti in California Deutsch Español Français Bahasa Indonesia Italiano Nederlands Português do Brasil Svenska Türkçe Русский العربية עִבְרִית 日本語 한국어 简体中文 繁體中文 English Deutsch Español Français Bahasa Indonesia Italiano Nederlands Português do Brasil Svenska Türkçe Русский العربية עִבְרִית 日本語 한국어 简体中文 繁體中文 English App per dispositivi mobili Scarica su App Store Provalo Google Play Social Media WordPress.com su Facebook WordPress.com su X (Twitter) WordPress.com su Instagram WordPress.com on YouTube Automattic Automattic Lavora con noi Caricamento commenti... Scrivi un Commento... E-mail Nome Sito web Supporto Registrati Accedi Copia shortlink Segnala questo contenuto Gestisci gli abbonamenti | 2026-01-13T09:29:34 |
https://ace.atlassian.com/communityevents | About | Atlassian Community Events Skip to main content Toggle Navigation Events Connect Atlassian Community Events Join a Chapter Community-led Conferences Online Community Connect with Orbiit Learn Community-Led Classes Company User Groups Earn an Atlassian Certification Become a Champion ACE Speakers Find an ACE Speaker Log in Atlassian Community Events Atlassian Community Events are free, user-led meetups happening in cities all over the world. Meet other Atlassian enthusiasts in your area and benefit from: Valuable content Deep dive into interesting topics through presentations led by other users, Atlassian experts, and even Atlassians! All the swag! Enjoy free food, drink, and swag from Atlassian and local Solution Partners. Networking opportunities Meet other Atlassian fans in your city and learn each others’ best practices. Exclusive discounts Save on certification exams and get early access discounts to Atlassian events and conferences. Bring a friend Community Events are free to attend and all are welcome. Bring a plus one (or three) and grow your local community! The inside scoop Be the first to know about the latest product updates and announcements from Atlassian. Upcoming ACE events Get involved There's an event for everyone. Attend local community events, special events, or industry-specific meet-ups. Or, start a new community event in your city. © 2026 Atlassian Community Events All Rights Reserved ∙ Events ∙ Contact Us ∙ Privacy Policy ∙ Terms and Conditions ∙ Notice at Collection | 2026-01-13T09:29:34 |
https://cloudflare.com/ja-jp/zero-trust/solutions/multi-channel-phishing/ | マルチチャネルフィッシング | Zero Trust | Cloudflare サインアップ 言語 English English (United Kingdom) Deutsch Español (Latinoamérica) Español (España) Français Italiano 日本語 한국어 Polski Português (Brasil) Русский 繁體中文 简体中文 プラットフォーム コネクティビティクラウド Cloudflareのコネクティビティクラウドは、ネットワーキング、セキュリティ、パフォーマンスのサービスを60以上提供します。 エンタープライズ 大中企業向け スモールビジネス 小規模組織向け パートナー Cloudflareパートナーになる ユースケース アプリケーションモダナイゼーション パフォーマンスを加速 アプリの可用性を確保 Web体験を最適化 セキュリティモダナイゼーション VPNの代替 フィッシング対策 WebアプリとAPIを保護 ネットワークモダナイゼーション コーヒーショップネットワーキング WANモダナイゼーション 企業ネットワークの簡素化 CXOトピック AIを導入 労働力とデジタル体験にAI導入 AIセキュリティ エージェント型AIおよびGenAIアプリケーションのセキュリティ保護 データコンプライアンス コンプライアンスの合理化とリスク最小化 ポスト量子の暗号 データの保護とコンプライアンス基準の充足 業界 ヘルスケア 銀行 小売 ゲーミング 公共機関 リソース 製品ガイド リファレンスアーキテクチャ アナリストレポート 相談 イベント デモ ウェビナー ワークショップ デモを依頼 製品 製品 ワークスペースのセキュリティ ゼロトラストネットワークアクセス セキュアWebゲートウェイ メールセキュリティ クラウドアクセスセキュリティブローカー（CASB） アプリケーションセキュリティ レイヤー7のDDoS攻撃対策 Webアプリケーションファイアウォール APIセキュリティ ボット管理 アプリケーションパフォーマンス CDN DNS スマートルーティング Load balancing ネットワーキングとSASE レイヤー3/4のDDoS攻撃対策 NaaS/SD- WAN Firewall as a Service ネットワークインターコネクト プランと料金 Enterpriseプラン 中小企業向けプラン 個人向けプラン プランを比較する グローバルサービス サポートとサクセスバンドル 最適化されたCloudflare体験 プロフェッショナルサービス 専門家主導の実装 技術アカウント管理 技術管理を重視 セキュリティオペレーションサービス Cloudflareの監視と対応 ドメイン登録 ドメインの購入と管理 1.1.1.1 フリーDNSリゾルバー リソース 製品ガイド リファレンスアーキテ クチャ アナリストレポート 製品デモとツアー プラン選択にヘルプが必要 開発者 ドキュメンテーション 開発者ライブラリ ドキュメントとガイド アプリケーションデモ 構築可能なものを見る チュートリアル 段階的な構築チュートリアル リファレンスアーキテクチャ 図とデザインパターン 製品 人工知能 AI Gateway AIアプリの監視と制御 Workers AI 当社のネットワークでMLモデルを実行 コンピューティング Observability ログ、メトリクス、トレース Workers サーバーレスアプリの構築と展開 メディア Images 画像の変換と最適化 Realtime リアルタイムのオーディオおよび 動画アプリを構築 ストレージとデータベース D1 サーバーレスSQLデータベースを作成 R2 高額のエグレス料金なしでデータを保存 プランと料金 Workers サーバーレスアプリの構築とデプロイ Workers KV アプリ用のサーバーレスkey-valueストア R2 高額のエグレス料金なしでデータ保存 プロジェクトを詳しく見る お客様事例 30秒でできるAIデモ 始めるためのクイックガイド Workers Playgroundを詳しく見る 構築、テスト、デプロイ Developers Discord コミュニティに参加する 構築を開始する パートナー パートナーネットワーク Cloudflareで成長、革新、顧客ニーズを満たす パートナーポータル リソースの検索と案件登録 パートナーのタイプ PowerUPプログラム 顧客の接続と保護を維持しつつ、ビジネスを成長 テクノロジーパートナー 当社のテクノロジーパートナーとインテグレーターのエコシステムについて グローバルシステムインテグレーター シームレスで大規模なデジタルトランスフォーメーションサポート サービスプロバイダー 本当に価値のあるサービスプロバイダーのネットワークをご紹介 セルフサーブエージェンシープログラム クライアントのセルフサーブアカウントを管理 ピアツーピア（P2P）ポータル ネットワークのトラフィックインサイト パートナー の検索 PowerUPでビジネスを強化し、Cloudflare Powered+パートナーとつながりましょう。 リソース 相談 デモと製品ツアー オンデマンドの製品デモ 導入事例 Cloudflareで成功を追求 ウェビナー 洞察に満ちたディスカッション ワークショップ バーチャルフォーラム ライブラリ 役立つガイド、ロードマップなど レポート Cloudflareの調査インサイト ブログ 技術的な詳細情報と製品ニュース ラーニングセンター 教育ツールとハウツーコンテンツ 構築 リファレンスアーキテクチャ テクニカルガイド ソリューションおよび製品ガイド 製品ドキュメント ドキュメンテーション 開発者向けドキュメント 探求 theNET デジタルエンタープライズに関する経営管理層向けインサイト Cloudflare TV 革新的なシリーズとイベント Cloudforce One 脅威のリサーチとオペレーション Radar インターネットトラフィックとセキュリティのトレンド アナリストレポート 業界調査レポート イベント 今後の地域イベント 信頼、プライバシー、コンプライアンス コンプライアンス情報とポリシー サポート 問い合わせる コミュニティフォーラム アカウントにアクセスできなくなりましたか？ Developers Discord 支援を申し込む 会社 会社情報 リーダーシップ リーダーの紹介 IR 投資家情報 プレス 最近のニュースを詳しく見る キャリア 求人情報を確認する 信頼、プライバシー、安全性 プライバシー ポリシー、データ、保護 信頼 ポリシー、プロセス、安全性 コンプライアンス 認定および規制 透明性 ポリシーと開示 情報 公共の利益 人道支援 プロジェクトGalileo 政府 Athenianプロジェクト 選挙 Cloudflare For Campaigns 健康 Project Fair Shot グローバルネットワーク 世界の場所とステータス ログイン 営業担当者への問い合わせ メール検出のCloudy LLM要約| ブログを読む > SASEとワークスペースセキュリティ 概要 ソリューション 製品 リソース 価格設定 Cloudflareでマルチチャネルフィッシングから保護 受信トレイを超えて機能する多層式保護を実装 Cloudflareのコネクティビティクラウドは、自動化されマルチレイヤーのアプローチでフィッシングの脅威をメール、SMS、ソーシャルメディア、インスタントメッセンジャー、その他コラボアプリに渡り保護します。 お問い合わせ Cloudflareの違い ロータッチで高効率の保護 最低限のチューニングで業界屈指の検出効果を発揮し、フィッシングのリスクを最小化。 幅広い統合、低コスト すべてのフィッシングユースケースに対応できる単一かつ完全統合されたプラットフォームで支出を削減。 迅速に展開、簡単に管理 継続的管理に必要な時間と労力を削減しつつ、即時の保護を確保します。 仕組み 完全なマルチチャネル保護を単一のプラットフォームで実装 Cloudflareの統合型セキュリティプラットフォームを活用して、まずはメールを保護し、続いてZero Trustサービスを付加的に運用してあらゆるチャネルに渡りフィッシング保護を拡張できます。 ソリューションブリーフを読む 労力をかけないデプロイとスケーリング メールセキュリティを素早くレイヤー化し、最も重要なチャネルを保護し、続いて労力をかけずにマルチチャネル能力を貴社独自のペースで実現。 メールの脅威を食い止める ビジネスメース侵害（BEC）攻撃、悪意のある添付ファイル、その他メールベースの脅威を機械学習搭載のコンテキスト分析を活用して自動的に阻止。 認証情報の窃取により発生する漏洩を防ぐ 条件付きアクセ ス、および認証情報が盗難または侵害された際の最終防衛ラインとして機能する対フィッシングFIDO2セキュリティキーを実装。 リンクベースの詐欺攻撃をブロック 多彩なコラボアプリを用い巧妙に偽装されたリンクをクリックさせようとする標的型攻撃からユーザーを完全隔離。 Werner Enterprises、Cloudflareと共にフィッシングを軽減しセキュリティを統合 米国で最大級のトラック運送会社の1社であるWerner Enterprisesは、世界クラスのサプライチェーンソリューション連盟の中心で活躍しています。攻撃がその頻度と洗練化を高めており、同社は、巨大で分散化された従業員を守るフィッシング保護策を必要としていました。 Wernerは、Microsoft 365の受信箱の保護、モバイルおよびローミングユーザー保護の改善、そしてフィッシングを食い止めるためのより積 極的なアプローチをとるに当たり、Cloudflare Email Securityを採用しました。同社では、管理の複雑性を低減させながら、悪意のあるメールを減らすことに成功しました。 「当社では採用を進めた結果、当社のユーザーが毎日受信する、多くの悪意のあるまたは疑わしいEメールを50%削減できました。」 マルチチャネルに渡りフィッシングを食い止めるための行動を起こしましょう。 お問い 合わせ アナリストの評価 Cloudflare、本メールセキュリティアナリストレポートの「現行サービス」カテゴリーでトップ3にランクイン Cloudflare、2025年第2四半期の『Forrester Wave™：メール、メッセージング、コラボレーションセキュリティソリューション部門』で「Strong Performer（優れた企業）」認定マルウェア対策とサンドボックス、悪意のあるURLの検出とWebセキュリティ、脅威インテリジェンス、コンテンツ分析と処理を含む9つの基準で、最高点（5.0点中5.0点）獲得。 本レポートでは、「Cloudflareは、現在のメール、メッセージング、コラボレーションツールを、深いコンテンツ分析、処理、マルウェア検出機能で補強したい組織にとって堅固な選択肢」と評価されています。 レポー トを読む Cloudflareとの出会い Cloudflareのコネクティビティクラウドが、マルチチャネルフィッシング保護を簡素化 Cloudflareの クラウドネイティブなセキュリティ の統合型プラットフォームとコネクティビティサービスが、メール、インスタントメッセンジャー、SMS、ソーシャルメディア、他コラボアプリに渡るフィッシングに対処します。 構成可能なアーキテクチャ 広範な相互運用性とカスタマイゼーションを活用し、セキュリティのあらゆる要件に対応します。 パフォーマンス インターネットユーザーの95%からおよそ50ミリ秒の近さにあるグローバルネットワークで、あらゆる場所の従業員のために保護を実現。 脅威インテリジェンス Webの最大20%をプロキシし、毎日数十億単位の脅威をブロックすることから得たインテリジェンスにより、サイバー攻撃を全面的に阻止。 統合インターフェース ツールとワークフローを統合。 リソース Slide 1 of 6 ソリューション概説 メールセキュリティおよびZero Trustサービスにより、従業員とアプリケーションに渡り、Cloudflareが完全なフィッシング保護を実現する仕組みを徹底解説します。 ソリューション概要を入手 インサイト Cloudflare Email Securityで、フィッシング、ビジネスメール詐欺攻撃、リンクベースの攻撃からユーザ ーを先制的に保護する方法を解説します。 Webページを開く インサイト コストをかけず、ユーザーに影響することが一切なく、現在お使いのメール防御を侵害するフィッシング攻撃を特定 無料評価をリクエスト ソリューション概説 Cloudflareがブラウザ分離保護と管理を適用してリンクベースのフィッシングのリスクを防ぐ仕組みを解説します。 ブリーフをダウンロード 導入事例 Cloudflareがハードキーを用いるマルチ要素認証（MFA）で巧妙な文字ベースのフィッシング攻撃を撃退した方法を解説します。 導入事例を読む レポート Cloudflareが1年間で処理するおよそ130億件のメールに基づく主な攻撃動向を取り上げています。 レポートを入手する ソリューション概説 メールセキュリティおよびZero Trustサービスにより、従業員とアプリケーションに渡り、Cloudflareが完全なフィッシング保護を実現する仕組みを徹底解説します。 ソリューション概要を入手 インサイト Cloudflare Email Securityで、フィッシング、ビジネスメール詐欺攻撃、リンクベースの攻撃からユーザーを先制的に保護する方法を解説します。 Webページを開く インサイト コストをかけず、ユーザーに影響することが一切なく、現在お使いのメール防御を侵害するフィッシング攻撃を特定 無料評価をリクエスト ソリューション概説 Cloudflareがブラウザ分離保護と管理を適用してリンクベースのフィッシングのリスクを防ぐ仕組みを解説します。 ブリーフをダウンロード 導入事例 Cloudflareがハードキーを用いるマルチ要素認証（MFA）で巧妙な文字ベースのフィッシング攻撃を撃退した方法を解説します。 導入事例を読む レポート Cloudflareが1年間で処理するおよそ130億件のメールに基づく主な攻撃動向を取り上げています。 レポートを入手する ソリューション概説 メールセキュリティおよびZero Trustサービスにより、従業員とアプリケーションに渡り、Cloudflareが完全なフィッシング保護を実現する仕組みを徹底解説します。 ソリューション概要を入手 インサイト Cloudflare Email Securityで、フィッシング、ビジネスメール詐欺攻撃、リンクベースの攻撃からユーザーを先制的に保護する方法を解説します。 Webページを開く インサイト コストをかけず、ユーザーに影響することが一切なく、現在お使いのメール防御を侵害するフィッシング攻撃を特定 無料評価をリクエスト ソリューション概説 Cloudflareがブラウザ分離保護と管理を適用してリンクベースのフィッシングのリスクを防ぐ仕組みを解説します。 ブリーフをダウンロード 導入事例 Cloudflareがハードキーを用いるマルチ要素認証（MFA）で巧妙な文字ベースのフィッシング攻撃を撃退した方法を解説します。 導入事例を読む レポート Cloudflareが1年間で処理するおよそ130億件のメールに基づく主な攻撃動向を取り上げています。 レポートを入手する 利用開始 Freeプラン 中小企業向けプラン エンタープライズ向け 推奨製品を尋ねる デモを依頼 営業担当者へのお問い合わせ ソリューション コネクティビティクラウド アプリケーションサービス SASEとワークスペースのセキュリティ ネットワークサービス 開発者プラットフォーム サポート ヘルプセンター カスタマーサポート コミュニティフォーラム Developers Discord アカウントにアクセスできなくなりましたか？ Cloudflareステータス コンプライアンス コンプライアンスリソース 信頼 GDPR 責任あるAI 透明性レポート 不正利用を報告する 公共の利益 プロジ ェクトGalileo Athenianプロジェクト Cloudflare for Campaigns Project Fairshot 会社 Cloudflareについて ネットワークマップ Cloudflareのチーム ロゴとプレスキット 多様性、公平性、包摂性 インパクト/ESG © 2026 Cloudflare, Inc. プライバシーポリシー 利用規約 セキュリティの問題を報告 信頼性と安全性 Cookieの設定 商標 | 2026-01-13T09:29:34 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3AoptionalBlock | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:34 |
https://www.ecns.cn/video/2026-01-01/detail-iheymvap1609951.shtml | The Awkward Chronicles of Uncle Sam: Claimed Glory, Met Chaos --> 中文 Home News Ecns Wire Business Travel Photo Video Voices RIGHT BG LINE Text: A A A Print Video The Awkward Chronicles of Uncle Sam: Claimed Glory, Met Chaos 2026-01-01 08:09:31 Ecns.cn Editor : Meng Xiangjun ECNS App Download “Clever” Uncle Sam’s 2025 scorecard: shift blame, stall governance, profit from conflicts, swing the tariff hammer—only to hit himself. The more he meddles and dodges, the deeper the mess and the faster credibility crumbles. More Photo Beijing-Tangshan intercity railway starts full-line operation Passenger trips of 3 major Hainan airports exceed 50 million in 2025 First 'Grassland curling' attracts 350 competitors China launches two new satellites for space target detection test People perform 'circle dance' to pray for a bountiful new year in Qingha First batch of China's emergency humanitarian aid arrives in Cambodia Central London illuminated to welcome 2026 Chinese Foreign Minister meets Cambodian Deputy PM in Yunnan Exploring vivid sports competition throughout 2025 Exploring stunning winter scenery in Altay China's first L3 self-driving car debuts in Chongqin Grand bridge ready for traffic operation in Guizhou Harbin's celebrity snowman lights up winter night Southbound Travel for Guangdong Vehicles scheme implemented for entry into urban Hong Kong China's Feng/Huang claim mixed doubles title at BWF World Tour Finals Exploring overwintering migratory birds in Poyang Lake Xi presents orders to promote two military officers to rank of genera Inner Mongolia holds winter festival Memorial held for victims of Bondi Beach shooting in Sydney New year display unveiled at Times Square Night view of the 27th Harbin Ice and Snow World resembles fairy tale China launches island-wide special customs operations in Hainan FTP Why the world comes to Yiwu Exploring Hainan Free Trade Port before island-wide special customs operations Japanese bid farewell to the last two giant pandas Hainan's tallest building reaches key construction milestone Newly released Russia-transferred Japanese Unit 731 atrocity archives reveal human experiments, biological warfare committed by Japanese Imperial Army: FM Hainan FTP ready for island-wide independent customs operation Witnesses of a painful past, still waiting for an apology Geminid meteor shower seen across China Team China Sun Yingsha, Wang Chuqin win silver at the WTT Finals Hong Kong 2025 Kum Tag Desert welcomes its first snowfall this winter China's Lin Shidong advances to quarterfinals at WTT United States Smash Main tower of 27th Harbin Ice and Snow World topped out in NE China China launches sitellites for UAE, Egypt, Nepal Photo exhibition in Kazakhstan marks 70th founding anniversary of China's Xinjiang Uygur Autonomous Region Most popular in 24h More Top news (W.E. Talk) Looking ahead to 2026: As geopolitical conflict risks intensify, all parties seek opportunities amid crisis through strategic moves (W.E. Talk) Experts look to 2026: Seizing opportunities amid crises, forging ahead after breakthroughs South Korea's presidential office moves back to Cheong Wa Dae The Dunhuang Flying Dancers in the 1,360°C kiln fire Full text: Chinese President Xi Jinping's 2026 New Year message More Video (W.E. Talk) Experts look to 2026: Seizing opportunities amid crises, forging ahead after breakthroughs The Dunhuang Flying Dancers in the 1,360°C kiln fire LINE Media partners: People's Daily | Xinhua | CGTN | China Daily Back to top About Us | Jobs | Contact Us | Privacy Policy Copyright ©1999-2026 Chinanews.com. All rights reserved. Reproduction in whole or in part without permission is prohibited. [ 网上传播视听节目许可证（0106168) ] [ 京ICP证040655号 ] [ 京公网安备 11010202009201号 ] [ 京ICP备05004340号-1 ] --> --> | 2026-01-13T09:29:34 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3Aselect | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:34 |
https://www.ecns.cn/hd/2026-01-04/detail-iheymvap1612569.shtml#6 | International ice sculpture competition heats up in Harbin --> 中文 Home News Ecns Wire Business Travel Photo Video Voices RIGHT BG LINE Text: A A A Print Photo International ice sculpture competition heats up in Harbin ( 1 /10) 2026-01-04 10:20:27 Ecns.cn Editor :Zhao Li Members of a team from St. Petersburg, Russia, work on an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026.(Photo: China News Service/Zhao Yuhang) The competition has attracted 38 teams and 76 artists from 12 countries, including Australia, Poland, France, the United States, Spain, India and China. A Russian contestant creates an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026. (Photo: China News Service/Zhao Yuhang) A contestant from Mongolia works on an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026. (Aerial photo) (Photo: Yu Kun) A contestant from Mongolia works on an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026. (Aerial photo) (Photo: Yu Kun) Members of a China?Russia joint team carve an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, Jan. 3, 2026. (Aerial photo/ Yu Kun) The work was created to mark the 10th anniversary of the sister-city relationship between Harbin and Murmansk, Russia. (Photo: Yu Kun) A Russian contestant creates an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026. (Photo: China News Service/Zhao Yuhang) A Russian contestant creates an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026. (Photo: China News Service/Zhao Yuhang) A Spanish contestant works on an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026. (Photo: China News Service/Zhao Yuhang) A Spanish contestant works on an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026. (Photo: China News Service/Zhao Yuhang) A Russian contestant creates an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026. (Photo: China News Service/Zhao Yuhang) Previous The competition has attracted 38 teams and 76 artists from 12 countries, including Australia, Poland, France, the United States, Spain, India and China.--> The work was created to mark the 10th anniversary of the sister-city relationship between Harbin and Murmansk, Russia. (Photo: Yu Kun)--> Next (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) LINE More Photo Mourners pay tribute to Crans-Montana bar fire victims Venezuelan leader Maduro brought to New York Highlights of Chinese President Xi Jinping's 2026 New Year message Beijing-Tangshan intercity railway starts full-line operation First 'Grassland curling' attracts 350 competitors China launches two new satellites for space target detection test ${visuals_2} ${visuals_3} More Video (W.E. Talk) Experts on 2026: China's 15th Five-Year Plan significant for the World (W.E. Talk) Experts look to 2026: Seizing opportunities amid crises, forging ahead after breakthroughs The Awkward Chronicles of Uncle Sam: Claimed Glory, Met Chaos The Dunhuang Flying Dancers in the 1,360°C kiln fire The Awkward Chronicles of Uncle Sam: Tariff Bullying and Backfire (W.E. Talk) Experts' review on 2025: China serves as a stabilizing force in a world of turmoil and chaos ${new_video_hd2} ${new_video_hd3} LINE Media partners: People's Daily | Xinhua | CGTN | China Daily Back to top About Us | Jobs | Contact Us | Privacy Policy Copyright ©1999-2026 Chinanews.com. All rights reserved. Reproduction in whole or in part without permission is prohibited. [ 网上传播视听节目许可证（0106168) ] [ 京ICP证040655号 ] [ 京公网安备 11010202009201号 ] [ 京ICP备05004340号-1 ] --> --> | 2026-01-13T09:29:34 |
https://www.splunk.com/fr_fr/products/enterprise-security.html | Splunk Enterprise Security | Splunk English Deutsch 日本語 한국어 中文 繁體中文 false logo Assistance Assistance client Portail d’assistance Contactez-nous Splunk Answers État du système Assistance Cisco Assistance AppDynamics Mises à jour de sécurité des produits Langues Deutsch English 日本語 한국어 简体中文 繁體中文 Se connecter Cliquez sur Compte utilisateur Se connecter S’inscrire Mon tableau de bord Instances Ma formation Déconnexion PRODUCT LOGINS Splunk Observability Cloud Splunk Cloud Services Splunk On-Call Splunk Synthetic Monitoring Splunk Web Optimization Splunk AppDynamics logo Plateforme Plateforme La plateforme de données extensible offre une sécurité unifiée, une observabilité complète et des applications personnalisées illimitées. Tarifs Téléchargements et version d'essai gratuite Présentations des produits PRODUITS Cloud Platform Enterprise Splunkbase SCÉNARIOS D’UTILISATION Analysez l’état des services informatiques Conformité Évaluation de la résilience Gestion des données Intelligence artificielle Modernisation de l’IT Optimisation des données Supervision de la blockchain Supervision serverless Transformation cloud Présentation de la plateforme Voir tous les scénarios d’utilisation Sécurité Enterprise Security Renforcez votre résilience numérique en modernisant votre SOC grâce à des fonctions unifiées de détection des menaces, d’investigation et de réponse. Tarifs Téléchargements et version d'essai gratuite Présentations des produits Fonctionnalités Plateforme TDIR unifiée SIEM SOAR UEBA Attack Analyzer Asset and Risk Intelligence SCÉNARIOS D’UTILISATION Conformité Détection des anomalies Gestion des incidents Intelligence artificielle Optimisation des données Orchestrez les workflows de réponse Prévention de la fraude Recherche des menaces Résolution des problèmes IT Supervision de la sécurité Vue d’ensemble de la sécurité Voir tous les scénarios d’utilisation Observabilité Observabilité Obtenez la visibilité nécessaire pour détecter, diagnostiquer et résoudre les problèmes de performance, afin de garantir la fluidité de vos applications et de vos opérations. Tarifs Téléchargements et version d'essai gratuite Présentations des produits PRODUITS Observability Cloud IT Service Intelligence AppDynamics SCÉNARIOS D’UTILISATION Améliorez l’expérience des utilisateurs finaux Déboguez les problèmes dans les microservices Intégrité des services IT Intelligence artificielle Modernisation des applications Migration vers le cloud Observabilité en libre-service Optimisez la supervision du cloud Prévention des interruptions Réduisez le bruit des alertes Vue d’ensemble de l’observabilité Voir tous les scénarios d’utilisation Industries Industries Splunk aide les organisations de tous les secteurs à devenir plus productives, plus conformes et plus sûres. Aéronautique et défense Communications et medias Énergie et infrastructures Enseignement supérieur Fabrication Organismes à but non lucratif Retail Santé Secteur public Services en ligne Services financiers Technologie Voir tous les secteurs d’activité Ressources Événements Rejoignez-nous à un événement près de chez vous. Blogs Découvrez ce que fait Splunk. LANCEZ-VOUS Bien démarrer avec Splunk Splunk Lantern Communauté et groupes d’utilisateurs Réussite client Centre de ressources APPRENDRE Formation et certification Documentation Blogs Événements .conf26 POURQUOI SPLUNK Pourquoi Splunk À propos de Splunk Prix et récompenses Témoignages de clients Splunk et ses concurrents Partenaires Afficher toutes les ressources Cliquez sur Recherche Aide Assistance Assistance client Portail d’assistance Contactez-nous Splunk Answers État du système Assistance Cisco Assistance AppDynamics Mises à jour de sécurité des produits Langues Deutsch English 日本語 한국어 简体中文 繁體中文 Se connecter Cliquez sur Compte utilisateur Se connecter S’inscrire Mon tableau de bord Instances Ma formation Déconnexion PRODUCT LOGINS Splunk Observability Cloud Splunk Cloud Services Splunk On-Call Splunk Synthetic Monitoring Splunk Web Optimization Splunk AppDynamics Versions d’essai Cliquez sur Recherche Aide Versions d’essai logo Versions d’essai Plateforme Sécurité Observabilité Industries Ressources Assistance Account Se connecter | S’inscrire Deutsch English 日本語 한국어 简体中文 繁體中文 Plateforme Sécurité Observabilité Industries Ressources Assistance Plateforme La plateforme de données extensible offre une sécurité unifiée, une observabilité complète et des applications personnalisées illimitées. Tarifs Téléchargements et version d'essai gratuite Présentations des produits PRODUITS Cloud Platform Enterprise Splunkbase SCÉNARIOS D’UTILISATION Analysez l’état des services informatiques Conformité Évaluation de la résilience Gestion des données Intelligence artificielle Modernisation de l’IT Optimisation des données Supervision de la blockchain Supervision serverless Transformation cloud Présentation de la plateforme Voir tous les scénarios d’utilisation Enterprise Security Renforcez votre résilience numérique en modernisant votre SOC grâce à des fonctions unifiées de détection des menaces, d’investigation et de réponse. Tarifs Téléchargements et version d'essai gratuite Présentations des produits Fonctionnalités Plateforme TDIR unifiée SIEM SOAR UEBA Attack Analyzer Asset and Risk Intelligence SCÉNARIOS D’UTILISATION Conformité Détection des anomalies Gestion des incidents Intelligence artificielle Optimisation des données Orchestrez les workflows de réponse Prévention de la fraude Recherche des menaces Résolution des problèmes IT Supervision de la sécurité Vue d’ensemble de la sécurité Voir tous les scénarios d’utilisation Observabilité Obtenez la visibilité nécessaire pour détecter, diagnostiquer et résoudre les problèmes de performance, afin de garantir la fluidité de vos applications et de vos opérations. Tarifs Téléchargements et version d'essai gratuite Présentations des produits PRODUITS Observability Cloud IT Service Intelligence AppDynamics SCÉNARIOS D’UTILISATION Améliorez l’expérience des utilisateurs finaux Déboguez les problèmes dans les microservices Intégrité des services IT Intelligence artificielle Modernisation des applications Migration vers le cloud Observabilité en libre-service Optimisez la supervision du cloud Prévention des interruptions Réduisez le bruit des alertes Vue d’ensemble de l’observabilité Voir tous les scénarios d’utilisation Industries Splunk aide les organisations de tous les secteurs à devenir plus productives, plus conformes et plus sûres. Aéronautique et défense Communications et medias Énergie et infrastructures Enseignement supérieur Fabrication Organismes à but non lucratif Retail Santé Secteur public Services en ligne Services financiers Technologie Voir tous les secteurs d’activité Événements Rejoignez-nous à un événement près de chez vous. Blogs Découvrez ce que fait Splunk. LANCEZ-VOUS Bien démarrer avec Splunk Splunk Lantern Communauté et groupes d’utilisateurs Réussite client Centre de ressources APPRENDRE Formation et certification Documentation Blogs Événements .conf26 POURQUOI SPLUNK Pourquoi Splunk À propos de Splunk Prix et récompenses Témoignages de clients Splunk et ses concurrents Partenaires Afficher toutes les ressources Assistance client Portail d’assistance Contactez-nous Splunk Answers État du système Assistance Cisco Assistance AppDynamics Mises à jour de sécurité des produits Se connecter S’inscrire Mon tableau de bord Instances Ma formation Déconnexion PRODUCT LOGINS Splunk Observability Cloud Splunk Cloud Services Splunk On-Call Splunk Synthetic Monitoring Splunk Web Optimization Splunk AppDynamics Splunk Enterprise Security Splunk Enterprise Security Splunk Enterprise Security Fonctionnalités Capacités Capacités SIEM SOAR UEBA Options d’achat FAQ More Splunk Enterprise Security Unifiez le processus TDIR Réduisez la prolifération des outils Allez plus vite avec l’IA Décuplez les moyens du SOC Vous en avez assez des outils déconnectés ? Adoptez le nouveau standard de détection, d’investigation et de réponse aux menaces (TDIR). Enterprise Security (ES) est une plateforme TDIR unifiée qui s’intègre parfaitement à l’IA agentique, au SOAR, à l’UEBA, et au SIEM. Suivre la visite guidée const items = document.querySelectorAll('.gsap-words-list li'); items.forEach((item, i) => { item.style.display = i === 0 ? 'block' : 'none'; }); let current = 0; function showWord(index) { items.forEach((item, i) => { item.style.display = i === index ? 'block' : 'none'; }); gsap.fromTo(items[index], { y: -40, scale: 0.8 }, { y: 0, scale: 1.1, duration: 0.5}); gsap.to(items[index], { scale: 1, duration: 0.2, delay: 0.5 }); } function nextWord() { current = (current + 1) % items.length; showWord(current); } setInterval(nextWord, 2000); showWord(0); Localisez et arrêtez les menaces émergentes avec Splunk Splunk Enterprise Security aide les clients à réduire le déluge d’alertes, à accélérer les résultats de sécurité, à minimiser considérablement le risque et à renforcer la résilience à l’ère de l’IA agentique. Visibilité à 360° 111% de menaces supplémentaires détectées avec précision 1 Expérience simplifiée 64% de gain d’efficacité du SecOps 2 Accélération du SOC 55% d’accélération de la résolution des incidents 1 x Plus de clients Mettez un terme à l’épuisement des analystes avec la plateforme SecOps alimentée par l’IA de référence Obtenez une visibilité haute fidélité sur vos données Enterprise Security vous aide à gérer, interroger et analyser les données dans tous vos domaines, clouds et appareils. Lorsqu’elles peuvent compter sur une large visibilité, des détections pilotées par l’IA et des alertes hiérarchisées par l’IA, les équipes du SOC peuvent se concentrer sur les vrais positifs et réagir rapidement à des alertes haute fidélité. Unifiez le TDIR sur une même plateforme de sécurité Éliminez les silos et les changements de contexte avec une plateforme holistique qui intègre la détection, l’investigation et la réponse. Enterprise Security centralise les workflows du SOC et rationalise chaque étape, de la détection à la correction, au sein d’un même environnement de travail intuitif. Détectez les menaces internes et les attaques zero-day avec l’UEBA Enterprise Security s’appuie sur l’analyse du comportement des utilisateurs et des entités (UEBA) et le machine learning pour identifier les anomalies et les changements de comportement, pour que votre équipe puisse intervenir en cas de compromission de compte ou d’actif. Automatisation à l’échelle du SOC et enrichissement contextuel Mettez le pouvoir de l’automatisation à la portée de chaque membre du SOC grâce au SOAR (orchestration et automatisation de la réponse de sécurité) et à l’enrichissement automatique de la threat intelligence. Normalisez les investigations, suivez des plans de réponse pour éliminer les conjectures et assurez la cohérence de la réponse. Décuplez le pouvoir de vos analystes avec les workflows pilotés par l’IA Mettez l’IA au service de chaque analyste pour minimiser les efforts manuels et accélérer les investigations et les interventions grâce aux requêtes en langage naturel, aux workflows guidés, aux résumés instantanés et aux rapports automatisés. Déployez des détections en toute confiance pour réduire le temps de détection Detection Studio* permet de gérer l’intégralité du cycle de vie de la détection : les ingénieurs peuvent tester, déployer et contrôler les détections au sein d’une même expérience. Mesurez et renforcez votre couverture en vous appuyant sur le framework MITRE ATT&CK® pour que votre équipe soit toujours au fait de l’évolution des TTP et puisse agir rapidement en cas d’angle mort. * Disponible en version alpha dans certaines régions seulement Découvrez toutes les fonctionnalités d’Enterprise Security Voir toutes les fonctionnalités Alertes basée sur les risques (RBA) SOAR UEBA : optimisation des risques et des détections Assistant IA Gestion et fédération des données Alertes basée sur les risques (RBA) Accélérez la détection des menaces et hiérarchisez la réponse Dopez la productivité de votre SOC grâce à la détection des menaces haute fidélité, capable de réduire le volume des alertes jusqu’à 90 % . La RBA améliore les taux de vrais positifs pour que votre équipe se concentre sur les menaces les plus importantes. SOAR Gagnez en efficacité en automatisant les workflows TDIR Splunk SOAR automatise les workflows de sécurité pour alléger la part de travail manuel, éviter les déluges d’alertes et réduire les temps de réponse. Parfaitement intégrée à Splunk Enterprise Security, la solution permet d’automatiser le processus TDIR à grande échelle. UEBA : optimisation des risques et des détections Adaptez des modèles de machine learning et des workflows centrés sur l’utilisateur Affinez les modèles de machine learning et de comportement des utilisateurs en fonction des spécificités de vos processus, politiques, actifs, rôles utilisateurs et fonctions opérationnelles, pour optimiser la détection et l’atténuation des menaces internes et avancées. Assistant IA Appuyez-vous sur l’IA pour obtenir des conseils, élaborer des requêtes et générer des résumés et des rapports Obtenez instantanément des conseils sur mesure pour vos investigations, de l’aide à la création de requêtes, des résumés clairs et des rapports automatisés : tous les analystes bénéficient d’un assistant IA intégré à leurs workflows.* * Disponibilité contrôlée dans certaines régions Gestion et fédération des données Rationalisez la gestion et la consultation des données pour les équipes de sécurité Bénéficiez d’une visibilité unifiée sur les données grâce à des fonctions sophistiquées comme la recherche fédérée et l’analyse fédérée. Optimisez les coûts des scénarios de sécurité et donnez au SOC les moyens de détecter les menaces, d’investiguer et de répondre plus rapidement que jamais. Options d’achat d’Enterprise Security (ES) En savoir plus ES Essentials ES Premier Fonctionnalités incluses Supervision de la sécurité Supervisez les environnements locaux, hybrides et multicloud en temps réel pour détecter les menaces au plus tôt et réduire les risques. ✓ ✓ Détection des menaces Détectez les menaces avec rapidité et précision grâce à la RBA et à Detection Studio* ; misez sur une supervision en temps réel, des analyses avancées et la threat intelligence. * Disponible en version alpha dans certaines régions ✓ ✓ Investigation des menaces Obtenez des informations sur tout type de menace grâce à une plateforme intégrée qui combine la recherche avancée, la corrélation et l’analyse pour faciliter la collaboration et optimiser l’efficacité des workflows. ✓ ✓ Recherche des menaces Exploitez les puissantes fonctions de recherche, de corrélation, d’analyse et d’enrichissement de la threat intelligence pour découvrir les menaces invisibles et émergentes. ✓ ✓ Automatisation Automatisez les tâches, orchestrez les workflows et exécutez des playbooks personnalisables avec un SOAR accessible à tous les profils d’analyste. ✓ Détection des menaces internes Repérez les menaces internes au plus tôt grâce à la supervision en temps réel et au machine learning avancé qui signalent les anomalies et déclenchent des alertes haute fidélité. ✓ Gestion et fédération des données* Maximisez la visibilité des données avec la recherche fédérée et l’analyse fédérée. * Peut entraîner des frais supplémentaires ✓ ✓ Découvrez comment les clients maximisent la valeur avec Splunk Voir tous les témoignages 3 fois plus rapide pour répondre aux menaces, permettant à l’équipe de se consacrer à des tâches plus utiles et rentables. Lire le témoignage 40 % d’augmentation des détections de cybermenaces, et capacité à arrêter les menaces en un temps record. Lire le témoignage 120 Md $ de capitalisation protégés, et réduction significative du bruit grâce aux alertes basées sur le risque. Lire le témoignage x Questions fréquentes Qu’est-ce que Splunk Enterprise Security (ES) ? Splunk Enterprise Security (ES) est une plateforme intégrée de détection des menaces, d’investigation et de réponse (TDIR) qui unifie les workflows de sécurité. Elle intègre plusieurs fonctions essentielles : gestion des informations et des événements de sécurité (SIEM), IA agentique et SOAR pour l’automatisation, UEBA et IA/ML pour améliorer la précision des détections et la vitesse de réponse. En réunissant ces capacités au sein d’une même interface, Enterprise Security optimise les opérations, élimine les silos et donne aux équipes SOC la possibilité de détecter, investiguer et prendre en charge les menaces avec un maximum d’efficacité. En tant que client, quels sont les avantages immédiats de l’adoption d’ES Premier ? Le passage à ES Premier a des avantages immédiats et tangibles pour les clients actuels de Splunk. Citons notamment : La consolidation des outils : en rassemblant les différents outils de sécurité au sein d’une plateforme unifiée de TDIR, on rationalise les workflows, on réduit considérablement les délais d’intervention et on allège la complexité du processus de gestion des incidents pour les équipes. L’intégration d’outils disparates au sein d’une même interface évite aux clients de changer constamment de contexte, élimine de nombreuses étapes manuelles et produit une vision centralisée des menaces et des alertes. L’UEBA intégrée avec machine learning : les clients reçoivent des informations très détaillées sur les anomalies dans le comportement des utilisateurs et des entités, ce qui leur permet d’identifier les menaces internes, les comptes compromis et les tactiques sophistiquées comme les attaques zero-day. Des capacités SOAR pour l’ensemble du SOC : ES Premier lève tout obstacle à l’utilisation de l’orchestration et de l’automatisation de la réponse de sécurité (SOAR) et met ces puissantes fonctions à la portée de tous les membres de l’équipe, quel que soit leur rôle ou leur expérience. Tous les membres du SOC peuvent simplifier les workflows, enrichir les alertes et lancer des actions de réponse. En adoptant ES Premier dès maintenant, les clients vont améliorer l’efficacité des opérations, étendre la portée des opérations de sécurité et profiter des capacités d’IA les plus récentes. * Disponibilité contrôlée dans certaines régions. Quelle est la différence entre Splunk Enterprise Security Essentials et Enterprise Security Premier ? Actuellement, les clients peuvent choisir entre deux versions d’Enterprise Security : Essentials et Premier. ES Essentials comprend non seulement le célèbre SIEM de Splunk, mais aussi l’AI Assistant for Security (AIA) et Detection Studio dans les régions où il est disponible. Splunk Enterprise Security Essentials est une solution de gestion des informations et des événements de sécurité (SIEM) leader du marché depuis plus de 10 ans. Splunk Enterprise Security Premier va au-delà des simples capacités de SIEM. Il s’agit d’une nouvelle plateforme unifiée dédiée à la détection des menaces, à l’investigation et à la réponse. Elle rassemble des fonctions de SIEM, d’UEBA, de SOAR et d’IA au sein d’une même plateforme pour faire face à l’évolution rapide du paysage de sécurité. Comment est-ce que Splunk Enterprise Security utilise l’IA agentique pour améliorer l’efficacité du SOC ? Splunk Enterprise Security (ES) s’appuie sur l’IA agentique pour doper l’efficacité des équipes du centre des opérations de sécurité (SOC) en automatisant les tâches simples et routinières afin d’accroître l’autonomie de la solution. Cette approche permet aux équipes SOC d’amplifier progressivement le rôle de l’IA, que ce soit pour accomplir des actions entièrement automatisées ou émettre des suggestions, le tout sous haute supervision humaine. ES comprend des fonctionnalités sophistiquées comme l’inversion des malwares qui décompose automatiquement les scripts malveillants ligne par ligne, extrait les indicateurs de compromission, signale les techniques d’évasion et regroupe les comportements récurrents pour accélérer les analyses. De plus, un agent de tri évalue, hiérarchise et explique les alertes pour aider les équipes du SOC à se concentrer sur les menaces prioritaires. Grâce aux commandes en langage naturel, les équipes du SOC élaborent et personnalisent rapidement des playbooks d’automatisation et des règles de détection sans compétences techniques avancées. En unifiant l’enrichissement des alertes, le tri, l’investigation et l’analyse des malwares, ES allège la charge opérationnelle et permet aux analystes du SOC de se concentrer sur les tâches de sécurité à fort impact. 1 IDC Business Value Snapshot, commandé par Splunk, The Business Value of Splunk Security: A Unified TDIR Platform, #US53392325, mai 2025 2 Analyzing the Economic Benefits of Splunk Security, Enterprise Strategy Group, septembre 2023 Bien démarrer avec Enterprise Security Découvrez comment Splunk réunit tout le workflow TDIR au sein d’une puissante plateforme SOC agentique et unifiée. Suivre la visite guidée ENTREPRISE ENTREPRISE À propos de Splunk Carrières Splunk et les autres solutions Équipe de direction Communiqué de presse Partenaires Positions politiques de Splunk Splunk Protects SURGe Pourquoi Splunk ? PRODUITS PRODUITS Téléchargements et essais gratuits Tarification Voir tous les produits SITES SPLUNK SITES SPLUNK .conf Documentation Relations investisseurs Formation et certification Boutique Splunk Vidéos Voir toutes les ressources CONTACTER SPLUNK CONTACTER SPLUNK Contacter le service commercial Contacter l’assistance AVIS D'UTILISATEURS AVIS D'UTILISATEURS Gartner Peer Insights™ PeerSpot TrustRadius Splunk Twitter Facebook Linked In Youtube Instagram --> © 2005 - 2026 Splunk LLC Tous droits réservés. Domaine juridique Confidentialité Plan du site Cookies Conditions d'utilisation du site web Modern Slavery Splunk © 2005 - 2026 Splunk LLC Tous droits réservés. × | 2026-01-13T09:29:34 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3AsaveApplyBar | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:34 |
https://gitstar-ranking.com/dair-ai | dair-ai - Gitstar Ranking Gitstar Ranking Users Organizations Repositories Rankings Users Organizations Repositories Sign in with GitHub dair-ai Star 148110 Rank 71 Go to GitHub Fetched on 2026/01/09 10:17 63 Repositories Prompt-Engineering-Guide 68934 ML-YouTube-Courses 17082 ml-visuals 16656 ML-Papers-of-the-Week 12199 ML-Papers-Explained 8256 ML-Course-Notes 6373 Mathematics-for-ML 5623 ML-Notebooks 3430 Transformers-Recipe 1624 nlp_paper_summaries 1480 GNNs-Recipe 1267 MLOPs-Primer 967 AI-Product-Index 778 pytorch_notebooks 590 d2l-study-group 394 nlp_fundamentals 371 nlp_newsletter 303 awesome-ML-projects-guide 248 dair-ai.github.io 237 emotion_dataset 216 awesome-research-proposals-guide 204 m2-deep-research 189 ml-nlp-paper-discussions 150 keep-learning-ml 91 nlp_overview 49 notebooks 43 covid_19_search_application 30 maven-pe-for-llms-4 24 odsc_2020_nlp 22 research_emotion_analysis 21 llm-evaluator 18 deep-ai-research 18 data_science_writing_primer 18 deep-research-n8n 17 nlp_highlights 16 pe-for-llms 15 datasets 15 paper_implementations 13 maven-pe-for-llms 13 maven-pe-for-llms-6 9 deep_learning_notations 9 cursor-course 9 nlp_with_tensorflow 8 maven-pe-for-llms-8 8 cursor-final-project 8 maven-pe-for-llms-12 7 maven-pe-for-llms-11 7 maven-pe-for-llms-9 6 maven-pe-for-llms-7 6 maven-pe-for-llms-13 6 1 2 › Released by @k0kubun in December 2014. Fork me on GitHub . | 2026-01-13T09:29:34 |
https://gitstar-ranking.com/TheAlgorithms | TheAlgorithms - Gitstar Ranking Gitstar Ranking Users Organizations Repositories Rankings Users Organizations Repositories Sign in with GitHub TheAlgorithms Star 445168 Rank 16 Go to GitHub Fetched on 2026/01/09 09:32 44 Repositories Python 216664 Java 64696 JavaScript 34007 C-Plus-Plus 33659 Rust 25293 C 21555 Go 17740 C-Sharp 8000 Algorithms-Explanation 3357 TypeScript 2587 PHP 2552 Dart 2075 Kotlin 1585 Ruby 1293 Scala 1101 R 1083 TheAlgorithms.github.io 1079 website 981 Jupyter 885 Swift 543 Julia 494 Haskell 417 MATLAB-Octave 400 Lua 364 Solidity 356 Zig 330 .github 282 Elixir 256 F-Sharp 230 website-old 210 algorithms-keeper 185 AArch64_Assembly 180 OCaml 112 Clojure 108 Nim 98 scripts 87 Fortran 86 Elm 70 C-Plus-Plus-1 62 Mojo 48 Jule 30 Zig-delete 13 contributor_covenant 10 landing_page 5 Released by @k0kubun in December 2014. Fork me on GitHub . | 2026-01-13T09:29:34 |
https://gitstar-ranking.com/spring-projects | spring-projects - Gitstar Ranking Gitstar Ranking Users Organizations Repositories Rankings Users Organizations Repositories Sign in with GitHub spring-projects Star 226139 Rank 46 Go to GitHub Fetched on 2026/01/09 04:02 80 Repositories spring-boot 79611 spring-framework 59457 spring-security 9398 spring-petclinic 8858 spring-ai 7616 spring-data-examples 5392 spring-authorization-server 5077 spring-data-jpa 3218 spring-data-elasticsearch 2955 spring-batch 2898 spring-loaded 2721 spring-kafka 2438 spring-integration-samples 2365 spring-retry 2267 spring-session 1912 spring-data-redis 1843 spring-security-samples 1719 spring-data-mongodb 1667 spring-statemachine 1655 spring-integration 1611 spring-graphql 1583 spring-restdocs 1186 spring-hateoas 1075 spring-ai-examples 1062 spring-modulith 1049 spring-tools 946 spring-data-rest 944 spring-net 873 spring-data-neo4j 859 spring-amqp 849 spring-cloud 822 spring-data-commons 821 spring-data-relational 809 spring-shell 806 spring-data-r2dbc 702 spring-amqp-samples 606 spring-plugin 479 spring-webflow-samples 419 spring-hateoas-examples 397 spring-data-cassandra 395 spring-ldap 361 spring-grpc 360 spring-webflow 340 spring-ws 337 spring-flo 310 spring-vault 295 spring-integration-extensions 285 spring-data-couchbase 279 spring-batch-extensions 268 spring-data-envers 263 1 2 › Released by @k0kubun in December 2014. Fork me on GitHub . | 2026-01-13T09:29:34 |
https://docs.aws.amazon.com/es_es/cost-management/latest/userguide/ce-cost-comparison.html | Comparación de los costos entre periodos de tiempo - AWS Gestión de costes Comparación de los costos entre periodos de tiempo - AWS Gestión de costes Documentación AWS Billing and Cost Management Guía del usuario de Permisos Cómo acceder a la consola Las traducciones son generadas a través de traducción automática. En caso de conflicto entre la traducción y la version original de inglés, prevalecerá la version en inglés. Comparación de los costos entre periodos de tiempo La comparación de costos es una función del Explorador de costos que lo ayuda a identificar y comprender rápidamente los cambios en sus gastos de AWS. Analiza automáticamente las variaciones de los costos entre dos meses seleccionados, destacando los principales factores de costos y explicando las razones detrás de estos cambios. La característica proporciona acceso a la consola y a la API para ayudarlo a analizar los cambios en los costos de sus gastos de AWS. Ventajas principales: Identifica rápidamente los principales cambios en los costos de los servicios, las cuentas y las regiones. Proporciona un desglose detallado de los factores de costo, incluidos los cambios de uso y descuento. Reduce el tiempo de análisis manual de costos de horas a segundos. Disponible en el Explorador de costos sin costo adicional. Permisos Para acceder a los datos de la característica de Comparación de costos, necesita los siguientes permisos de IAM: ce:GetCostAndUsageComparisons ce:GetCostComparisonDrivers Estos permisos le permiten recuperar las comparaciones de costos y uso, y los factores que los impulsan. Cómo acceder a la consola Para analizar los cambios de costos en la consola, puede utilizar el widget Principales tendencias o el Explorador de costos. Acceso a la consola de Abra la consola de Administración de facturación y costos de en https://console.aws.amazon.com/costmanagement/ . Haga una de estas dos operaciones: En la página de inicio de la consola, consulte el widget de Principales tendencias , que muestra las 10 principales variaciones de costos entre los dos meses anteriores. En el panel de navegación, elija Explorador de costos y, a continuación, elija Comparar en el panel de Parámetros de informe . Revise el widget Principales tendencias con regularidad para identificar con antelación los cambios significativos en los costos. Para obtener más información sobre este widget, consulte Principales tendencias . JavaScript está desactivado o no está disponible en su navegador. Para utilizar la documentación de AWS, debe estar habilitado JavaScript. Para obtener más información, consulte las páginas de ayuda de su navegador. Convenciones del documento Previsiones Descripción de cómo funciona una comparación de costos ¿Le ha servido de ayuda esta página? - Sí Gracias por hacernos saber que estamos haciendo un buen trabajo. Si tiene un momento, díganos qué es lo que le ha gustado para que podamos seguir trabajando en esa línea. ¿Le ha servido de ayuda esta página? - No Gracias por informarnos de que debemos trabajar en esta página. Lamentamos haberle defraudado. Si tiene un momento, díganos cómo podemos mejorar la documentación. | 2026-01-13T09:29:34 |
https://www.ecns.cn/hd/2026-01-12/detail-iheyrzrv3843506.shtml#1 | 'Weepy horse' toy goes viral after sewing error --> 中文 Home News Ecns Wire Business Travel Photo Video Voices RIGHT BG LINE Text: A A A Print Photo 'Weepy horse' toy goes viral after sewing error ( 1 /5) 2026-01-12 14:09:33 Ecns.cn Editor :Zhao Li “Weepy horse” plush toys in various sizes are lined up at a factory in Yiwu, Zhejiang Province, Jan. 11, 2026. (Photo: China News Service/Dong Yixin) The “weepy horse”, originally intended as a smiling Year of the Horse figurine, attracted widespread attention after a consumer in Hangzhou shared her purchase online.The unusual design resulted from a worker mistakenly sewing the upturned mouth into a downward curve during production.The unexpected popularity of the defective design has led to a sharp increase in purchase orders,keeping factories working around the clock to fulfill demand. Zhang Huoqing, a merchant in Yiwu, east China’s Zhejiang Province, displays a “smiling horse” plush toy and its viral counterpart, the “weepy horse,” Jan. 11, 2026. (Photo: China News Service/Dong Yixin) Zhang Huoqing, a merchant in Yiwu, Zhejiang Province, smiles as she displays the “smiling horse” and “weepy horse” plush toys, Jan. 11, 2026. (Photo: China News Service/Dong Yixin) A buyer measures the size of a “weepy horse” plush toy in Yiwu, Zhejiang Province, Jan. 11, 2026. (Photo: China News Service/Dong Yixin) A batch of newly produced “weepy horse” plush toy samples is seen at a workshop in Yiwu, Zhejiang Province, Jan. 11, 2026. (Photo: China News Service/Dong Yixin) Previous The “weepy horse”, originally intended as a smiling Year of the Horse figurine, attracted widespread attention after a consumer in Hangzhou shared her purchase online.The unusual design resulted from a worker mistakenly sewing the upturned mouth into a downward curve during production.The unexpected popularity of the defective design has led to a sharp increase in purchase orders,keeping factories working around the clock to fulfill demand.--> Next (1) (2) (3) (4) (5) LINE More Photo New giant panda pair makes public debut in Malaysia Exploring world's largest island Greenland Venezuelan people call on U.S. to release Nicolás Maduro and his wife Heavey snow hits Paris 'Southern Snow Town' draws tourists to Guizhou Province Global mayors attend dialogue in NE China on developing ice, snow economy ${visuals_2} ${visuals_3} More Video Comicomment: No country has the right to act as the world's police What's it like doing business in China? Check what foreign friends say More than a business hub: check how global merchants thrive in Yiwu Insights | Sanae Takaichi's erroneous remarks a grave 'diplomatic failure': Japanese scholar Insights丨From energy cooperation to industrial co-building: New momentum in Europe-China ties Insights丨China’s economy in UN official’s eyes: Resilience, exports, and high-tech transition ${new_video_hd2} ${new_video_hd3} LINE Media partners: People's Daily | Xinhua | CGTN | China Daily Back to top About Us | Jobs | Contact Us | Privacy Policy Copyright ©1999-2026 Chinanews.com. All rights reserved. Reproduction in whole or in part without permission is prohibited. [ 网上传播视听节目许可证（0106168) ] [ 京ICP证040655号 ] [ 京公网安备 11010202009201号 ] [ 京ICP备05004340号-1 ] --> --> | 2026-01-13T09:29:34 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3Ablock | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:34 |
https://gitstar-ranking.com/grafana | grafana - Gitstar Ranking Gitstar Ranking Users Organizations Repositories Rankings Users Organizations Repositories Sign in with GitHub grafana Star 207185 Rank 53 Go to GitHub Fetched on 2026/01/09 07:17 934 Repositories grafana 71616 k6 29600 loki 27339 pyroscope 11133 tempo 4981 mimir 4883 oncall 3861 alloy 2787 tanka 2641 grafana-zabbix 2181 mcp-grafana 2095 phlare 2034 helm-charts 1945 beyla 1894 agent 1668 docker-otel-lgtm 1579 grafana-operator 1245 grafonnet-lib 1080 faro-web-sdk 1009 grafana-infinity-datasource 984 k6-operator 744 awesome-k6 733 grizzly 716 jsonnet-libs 712 grafana-docker 654 metrictank 619 intro-to-mltp 600 k8s-monitoring-helm 585 augurs 556 dskit 549 simple-json-datasource 509 grafonnet 504 terraform-provider-grafana 482 grafana-image-renderer 473 carbon-relay-ng 473 xk6-dashboard 463 grafana-kiosk 451 k6-learn 423 kubernetes-app 403 k6-studio 400 logs-drilldown 388 xk6-browser 361 promql-anomaly-detection 342 worldmap-panel 314 dashboard-linter 309 k6-template-typescript 306 postman-to-k6 297 sobek 295 github-datasource 293 xk6 286 1 2 3 4 5 … › Released by @k0kubun in December 2014. Fork me on GitHub . | 2026-01-13T09:29:34 |
https://wordpress.com/zh-tw/support/github-deployments/ | 在 WordPress.com 上使用 GitHub 部署 – WordPress.com 支援 產品 功能 資源 方案與定價 登入 立即開始使用 選單 WordPress 主機 WordPress 代理商計畫 成為聯盟的一份子 網域名稱 AI 網站製作工具 網站建置工具 建立部落格 電子報 專業版電子郵件服務 網站設計服務 電子商務版 WordPress Studio 企業版 WordPress 概述 WordPress 佈景主題 WordPress 外掛程式 WordPress 版面配置 Google Apps 支援中心 WordPress 新聞 公司名稱產生器 標誌製作工具 發現新文章 熱門標籤 搜尋部落格 關閉導覽選單 立即開始使用 註冊 登入 關於 方案與定價 產品 WordPress 主機 WordPress 代理商計畫 成為聯盟的一份子 網域名稱 AI 網站製作工具 網站建置工具 建立部落格 電子報 專業版電子郵件服務 網站設計服務 電子商務版 WordPress Studio 企業版 WordPress 功能 概述 WordPress 佈景主題 WordPress 外掛程式 WordPress 版面配置 Google Apps 資源 支援中心 WordPress 新聞 公司名稱產生器 標誌製作工具 發現新文章 熱門標籤 搜尋部落格 Jetpack 應用程式 深入了解 支援中心 指南 課程 論壇 連絡人 搜尋 支援中心 / 指南 支援中心 指南 課程 論壇 連絡人 指南 / 管理帳號 / 工具 / 在 WordPress.com 上使用 GitHub 部署 在 WordPress.com 上使用 GitHub 部署 Github 部署可將 GitHub 儲存庫直接與 WordPress.com 網站整合，提供由版本控制的自動化工作流程，用於部署外掛程式、佈景主題或完成網站變更。本指引將說明設定流程，以及如何管理已連結的儲存庫。 此功能適用於使用 WordPress.com 商用版和電子商務版方案 的網站。如果你有商用版方案，請務必 啟用該方案 。若是免費網站和採用個人版及進階版方案的網站，只要 升級方案 即可存取此功能。 在此指南中 影片教學 連結儲存庫 管理部署設定 進階部署 部署程式碼 管理現有連結 部署執行記錄 中斷連結儲存庫 中斷 GitHub 與 WordPress.com 的連結 有任何疑問嗎？ 詢問我們的 AI 助理 回到頂端 影片教學 此影片使用英文字幕。 YouTube 提供自動翻譯功能，讓你可以用自己的語言觀看： 開啟自動翻譯字幕的方法： 播放影片。 點擊影片右下角的 ⚙️ 設定 圖示。 選擇 字幕/副本 。 選擇 自動翻譯 。 從清單中選擇你的偏好語言。 使用自動配音（測試版）的方法： 點擊 ⚙️ 設定 圖示。 選擇 音訊曲目 。 選擇你想收聽的語言： ℹ️ 翻譯與配音由 Google 自動產生，可能不夠精確，且自動配音功能仍在測試階段，暫未向所有語言開放。 連結儲存庫 在將 GitHub 儲存庫部署到 WordPress.com 網站之前，請先使用下列步驟設定兩者之間的連線： 前往「網站」頁面： https://wordpress.com/sites/ 按一下網站名稱，檢視網站概觀。 按一下「 部署 」分頁。 按一下「 連結儲存庫 」按鈕。如果接著看到系統列出儲存庫，則代表你已連結 Github 帳號。繼續步驟 11。 按一下「 安裝 WordPress.com 應用程式 」按鈕。 系統會開啟新視窗，並提示你登入 GitHub 帳號 (如果尚未登入)。然後你會看到這個畫面： 按一下「 授權適合開發人員的 WordPress.com 」按鈕。 選取儲存庫所在的 GitHub 組織或帳號。 選取要連結的儲存庫： 所有儲存庫： 選取此選項，會允許 WordPress.com 存取所有目前 和 未來由指定 GitHub 帳號擁有的儲存庫，包括唯讀的公開儲存庫。 僅限指定儲存庫： 選取此選項，就能選擇 WordPress.com 可在指定 GutHub 帳號中存取的儲存庫。 選定選項後，按一下「 安裝 」按鈕。 新視窗將會關閉，系統會將你帶回 WordPress.com。系統會列出你選取的儲存庫，以及與該儲存庫相關聯的 GitHub 帳號： 按一下要連結儲存庫旁的「 選取 」。 此時，你應該會在「 已授權的 GitHub 應用程式 」和「 已安裝的 GitHub 應用程式 」底下，看到「 適合開發人員的 WordPress.com 」。 管理部署設定 選取儲存庫後，就需要調整部署設定： 部署分支： 預設為儲存庫的預設分支 (通常為 main )，但可以變更為你想使用的分支。 目標目錄： 你想部署檔案的伺服器資料夾，外掛程式會是 /wp-content/plugins/my-plugin-name ，佈景主題則會是 /wp-content/themes/my-theme-name 。若為部分網站部署 (例如多個外掛程式或佈景主題)，則可使用 /wp-content 。儲存庫的內容會與 WordPress 網站在指定目錄中的現有內容合併。 自動部署： 部署至 WordPress.com 的方法有兩種： 自動： 程式碼一經確認，就會部署到你的 WordPress.com 網站。預備網站建議使用自動部署。 手動： 你需要 要求部署 ，程式碼才會部署。正式版網站建議使用手動部署。 部署模式： 部署分成兩種類型： 簡單： 這個模式會將 所有 檔案從儲存庫分支複製到網站，且無須後續處理即可部署。 進階： 在這個模式中，你可以用工作流程指令碼啟用自訂建置步驟，例如安裝編輯器相依性、執行部署前程式碼測試，以及控制檔案部署，適合需要編輯器或節點軟體的儲存庫。 如需詳細資訊，請參閱下方的「進階部署」 。 設定好所有項目後，按一下「 連結 」按鈕，系統就會新增你的儲存庫： 請注意，你必須 以自動或手動的方式 觸發第一項部署，接著只要按一下「 連結儲存庫 」按鈕，即可隨時連結其他儲存庫。 進階部署 透過「進階部署」，你可以提供工作流程指令碼，在部署前處理儲存庫中的檔案。這會帶進許多可能性，例如檢查程式碼是否符合團隊的程式碼標準、執行單元測試、從部署排除檔案、安裝相依性等等。若要開始使用，請查看 我們的工作流程方案 。 設定進階部署時： 系統會顯示一個表單，供你設定部署。 按一下儲存庫名稱，即可管理連線。 在右側的「 選擇你的部署模式 」下方，選擇「 進階 」。 如果儲存庫已包含工作流程檔案，則可在此選取。系統會檢查檔案是否有任何錯誤。如果找不到錯誤，請繼續步驟 7。 你也可以選取「 建立新工作流程 」選項，新增預先設定的工作流程檔案。如果儲存庫中已存在 wpcom.yml 工作流程檔案，選擇此選項會覆寫該檔案。 按一下「 為我安裝工作流程 」按鈕，將工作流程檔案提交至儲存庫。 新增並驗證工作流程後，按一下「 更新 」。現在你的儲存庫將使用進階部署。 部署程式碼 將 GitHub 儲存庫連結至網站後，下一個步驟就是部署程式碼。部署方法分為兩種： 自動 和 手動 。 不建議為已上線的正式版網站設定 自動 部署，因為儲存庫中任何程式碼變更，都會自動從 GitHub 部署到已上線網站。請考慮改為 預備網站 設定自動部署，準備就緒後再同步至正式版網站。 手動 部署可讓你進一步控制程式碼變更推送上線的時間，因為你需要手動觸發每項部署。如果你不想使用預備網站，建議設定手動部署。 若要手動觸發部署： 前往「網站」頁面： https://wordpress.com/sites/ 按一下網站名稱，檢視網站概觀。 按一下「 部署 」分頁。 按一下你要部署儲存庫上的省略符號選單 (⋮)。 選擇「 觸發手動部署 」。系統會顯示橫幅通知，上面寫著「已建立部署執行」，部署狀態會變更為「已排入佇列」。 等待部署完成 (狀態會變更為「已部署」)。 再次按下省略符號選單 (⋮)，然後選擇「 檢視部署執行 」。 部署執行記錄 會顯示「作者」和已部署的確認。按一下部署執行條目，即可檢視詳細資訊。 管理現有連結 若要管理現有的 GitHub 儲存庫連結： 前往「網站」頁面： https://wordpress.com/sites/ 按一下網站名稱，檢視網站概觀。 按一下「 部署 」分頁。 系統會隨即顯示連結清單。 只要 GitHub 儲存庫與你的網站之間至少有一個連結，系統就會顯示連結清單。這份清單包含每個連結的相關資訊，例如儲存庫名稱和分支、上次部署到網站的確認、發生時間、程式碼放置位置、部署執行時間長度及其狀態。 按一下省略符號選單 (⋮) 後，會顯示其他可用動作： 觸發手動部署： 開始在已設定分支的最新確認上 執行部署 。 檢視部署執行： 開啟已連結儲存庫的 部署執行記錄 視窗。 設定連結： 開啟儲存庫的 管理連結視窗 。 中斷連結儲存庫： 移除儲存庫與網站之間的連結。 部署執行記錄 部署執行記錄提供每個部署的詳細逐步記錄，包括自動觸發和手動觸發。這些記錄可協助你追蹤變更、監控部署狀態，以及疑難排解任何發生的問題。你可在 30 天內存取過去 10 次執行的記錄，輕鬆檢視每次部署期間的狀況，確保一切順利執行。 若要檢查部署記錄： 前往「網站」頁面： https://wordpress.com/sites/ 按一下網站名稱，檢視網站概觀。 按一下「 部署 」分頁。 按一下你要檢視記錄之儲存庫旁的省略符號選單 (⋮)。 選取「 檢視部署執行 」。 「 部署執行 」 清單檢視會顯示已部署到網站的確認、部署狀態、日期及持續時間。 按一下執行中的任何位置，即可展開並檢視部署的詳細資訊。 記錄檔會提供所有已執行命令的記錄，包括從 GitHub 擷取程式碼，到將其放置在目標目錄中。按一下「 顯示更多 」即可展開記錄行，檢視詳細資訊。 中斷連結儲存庫 中斷 GitHub 儲存庫與網站的連線時，儲存庫未來的變更將不會再影響你的網站。根據預設，已部署的檔案會保留在網站上，但你可以選擇在中斷連結的過程中移除這些檔案。 若要移除儲存庫： 前往「網站」頁面： https://wordpress.com/sites/ 按一下網站名稱，檢視網站概觀。 按一下「 部署 」分頁。 按一下儲存庫上的省略符號選單 (⋮)。 選取「 中斷連結儲存庫 」。 系統會顯示對話視窗。按一下切換，可將相關檔案自網站移除。 按一下「 中斷連結儲存庫 」可關閉對話視窗，中斷連結儲存庫。 請注意，「 適合開發人員的 WordPress.com 」仍會顯示在「 已安裝的 GitHub 應用程式 」和「 已授權的 GitHub 應用程式 」中，這是因為 WordPress.com 仍可存取儲存庫，但連結已刪除。 中斷 GitHub 與 WordPress.com 的連結 你也可以選擇撤銷 WordPress.com 對你 GitHub 帳號的存取權。你可以隨時前往 GitHub 的 「應用程式」設定 進行這項操作。 若要撤銷授權應用程式對你 GitHub 帳號的存取權： 前往「 已授權的 GitHub 應用程式 」。 按一下「 適合開發人員的 WordPress.com 」旁的「 撤銷 」。 按一下「 我了解，撤銷存取權 」按鈕。 即使撤銷授權應用程式的存取權，程式碼仍可部署，因為「 適合開發人員的 WordPress.com 」應用程式仍安裝在指定帳號中。 若要撤銷 WordPress.com 安裝的存取權，停用將程式碼部署到你 WordPress.com 網站的功能： 前往「 已安裝的 GitHub 應用程式 」。 按一下「 適合開發人員的 WordPress.com 」旁的「 設定 」。 在「 危險區域 」區段中，按一下「 解除安裝 」，並在系統提示時按下「 OK 」。 將 WordPress.com 從授權應用程式清單中移除， 不 代表系統會刪除或停用儲存庫；撤銷對 WordPress.com 的存取權後，你的儲存庫仍會存在於 GitHub 上，但 WordPress.com 將無法再部署程式碼。 相關指南 使用 WP 管理員儀表板 流量設定 活動 存取網站資料庫 在此指南中 影片教學 連結儲存庫 管理部署設定 進階部署 部署程式碼 管理現有連結 部署執行記錄 中斷連結儲存庫 中斷 GitHub 與 WordPress.com 的連結 有任何疑問嗎？ 詢問我們的 AI 助理 回到頂端 找不到需要的內容嗎？ 聯絡我們 透過 AI 助理取得答案，付費方案提供 24 小時全年無休的專家人力支援。 在論壇提問 瀏覽問題並向其他有經驗的使用者取得答案。 Copied to clipboard! WordPress.com 產品 WordPress 主機 WordPress 代理商計畫 成為聯盟的一份子 網域名稱 AI 網站製作工具 網站建置工具 建立部落格 專業版電子郵件服務 網站設計服務 WordPress Studio 企業版 WordPress 功能 概述 WordPress 佈景主題 WordPress 外掛程式 WordPress 版面配置 Google Apps 資源 WordPress.com 部落格 公司名稱產生器 標誌製作工具 WordPress.com 閱讀器 無障礙 移除訂閱 輔助說明 支援中心 指南 課程 論壇 連絡人 開發人員 公司 關於 新聞資源 使用規定 隱私權保護政策 請勿販賣或分享我的個人資訊 加州使用者的隱私權聲明 Deutsch Español Français Bahasa Indonesia Italiano Nederlands Português do Brasil Svenska Türkçe Русский العربية עִבְרִית 日本語 한국어 简体中文 繁體中文 English Deutsch Español Français Bahasa Indonesia Italiano Nederlands Português do Brasil Svenska Türkçe Русский العربية עִבְרִית 日本語 한국어 简体中文 繁體中文 English 手機 Apps 於此下載 App Store 在此取得 Google Play 社交媒體 WordPress.com 的 Facebook WordPress.com 的 X (Twitter) WordPress.com 的 Instagram WordPress.com 的 YouTube 頻道 Automattic Automattic 與我們合作 載入迴響中... 發表迴響… 電子郵件 (必要) 名稱 (必要) 網站 WordPress.com 支援 註冊 登入 複製短網址 回報此內容 管理訂閱 | 2026-01-13T09:29:34 |
https://www.ecns.cn/hd/2026-01-04/detail-iheymvap1612569.shtml#1 | International ice sculpture competition heats up in Harbin --> 中文 Home News Ecns Wire Business Travel Photo Video Voices RIGHT BG LINE Text: A A A Print Photo International ice sculpture competition heats up in Harbin ( 1 /10) 2026-01-04 10:20:27 Ecns.cn Editor :Zhao Li Members of a team from St. Petersburg, Russia, work on an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026.(Photo: China News Service/Zhao Yuhang) The competition has attracted 38 teams and 76 artists from 12 countries, including Australia, Poland, France, the United States, Spain, India and China. A Russian contestant creates an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026. (Photo: China News Service/Zhao Yuhang) A contestant from Mongolia works on an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026. (Aerial photo) (Photo: Yu Kun) A contestant from Mongolia works on an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026. (Aerial photo) (Photo: Yu Kun) Members of a China?Russia joint team carve an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, Jan. 3, 2026. (Aerial photo/ Yu Kun) The work was created to mark the 10th anniversary of the sister-city relationship between Harbin and Murmansk, Russia. (Photo: Yu Kun) A Russian contestant creates an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026. (Photo: China News Service/Zhao Yuhang) A Russian contestant creates an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026. (Photo: China News Service/Zhao Yuhang) A Spanish contestant works on an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026. (Photo: China News Service/Zhao Yuhang) A Spanish contestant works on an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026. (Photo: China News Service/Zhao Yuhang) A Russian contestant creates an ice sculpture during the 37th China Harbin International Ice Sculpture Competition in Harbin, northeast China’s Heilongjiang Province, Jan. 3, 2026. (Photo: China News Service/Zhao Yuhang) Previous The competition has attracted 38 teams and 76 artists from 12 countries, including Australia, Poland, France, the United States, Spain, India and China.--> The work was created to mark the 10th anniversary of the sister-city relationship between Harbin and Murmansk, Russia. (Photo: Yu Kun)--> Next (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) LINE More Photo Mourners pay tribute to Crans-Montana bar fire victims Venezuelan leader Maduro brought to New York Highlights of Chinese President Xi Jinping's 2026 New Year message Beijing-Tangshan intercity railway starts full-line operation First 'Grassland curling' attracts 350 competitors China launches two new satellites for space target detection test ${visuals_2} ${visuals_3} More Video (W.E. Talk) Experts on 2026: China's 15th Five-Year Plan significant for the World (W.E. Talk) Experts look to 2026: Seizing opportunities amid crises, forging ahead after breakthroughs The Awkward Chronicles of Uncle Sam: Claimed Glory, Met Chaos The Dunhuang Flying Dancers in the 1,360°C kiln fire The Awkward Chronicles of Uncle Sam: Tariff Bullying and Backfire (W.E. Talk) Experts' review on 2025: China serves as a stabilizing force in a world of turmoil and chaos ${new_video_hd2} ${new_video_hd3} LINE Media partners: People's Daily | Xinhua | CGTN | China Daily Back to top About Us | Jobs | Contact Us | Privacy Policy Copyright ©1999-2026 Chinanews.com. All rights reserved. Reproduction in whole or in part without permission is prohibited. [ 网上传播视听节目许可证（0106168) ] [ 京ICP证040655号 ] [ 京公网安备 11010202009201号 ] [ 京ICP备05004340号-1 ] --> --> | 2026-01-13T09:29:34 |
https://wordpress.com/sv/support/github-distributioner/ | Använd GitHub-distributioner på WordPress.com – WordPress.com Support Produkter Funktioner Resurser Paket och priser Logga in Kom igång Meny Webbhotell för WordPress WordPress för byråer Bli en affiliate Domännamn AI-webbplatsbyggare Webbplatsbyggare Skapa en blogg Nyhetsbrev Professional Email Webbdesigntjänster Commerce WordPress Studio Enterprise WordPress Översikt WordPress-teman WordPress-tillägg WordPress-mönster Google Apps Supportcenter Nyheter från WordPress Företagsnamngenerator Logotypskapare Upptäck nya inlägg Populära etiketter Bloggsökning Stäng navigationsmenyn Kom igång Registrera Logga in Om Paket och priser Produkter Webbhotell för WordPress WordPress för byråer Bli en affiliate Domännamn AI-webbplatsbyggare Webbplatsbyggare Skapa en blogg Nyhetsbrev Professional Email Webbdesigntjänster Commerce WordPress Studio Enterprise WordPress Funktioner Översikt WordPress-teman WordPress-tillägg WordPress-mönster Google Apps Resurser Supportcenter Nyheter från WordPress Företagsnamngenerator Logotypskapare Upptäck nya inlägg Populära etiketter Bloggsökning Jetpack-app Lär dig mer Supportcenter Guider Kurser Forum Kontakt Sök Supportcenter / Guider Supportcenter Guider Kurser Forum Kontakt Guider / Tillägg och verktyg / Verktyg / Använd GitHub-distributioner på WordPress.com Använd GitHub-distributioner på WordPress.com GitHub-distributioner integrerar dina GitHub-filförvar direkt med din WordPress.com-webbplats, vilket ger dig ett versionskontrollerat, automatiserat arbetsflöde för distribution av tillägg, teman eller fullständiga webbplatsändringar. I den här guiden kan du läsa mer om installationsprocessen och hur du hanterar anslutna filförvar. Den här funktionen är tillgänglig för webbplatser med WordPress.com Business- eller Commerce-paketet . Om du har ett Business-paket, se till att aktivera det . För gratis webbplatser och webbplatser med Personal- eller Premium-paketet kan du uppgradera ditt paket för att få åtkomst till den här funktionen. I denna guide Videohandledning Anslut ett filförvar Hantera distributionsinställningar Avancerad distribution Distribuera din kod Hantera befintliga anslutningar Distributionskörningsloggar Koppla från ett filförvar Koppla från WordPress.com från GitHub Har du några frågor? Fråga vår AI-assistent Tillbaka till toppen Videohandledning Den här videon är på engelska. YouTube har automatiska översättningsfunktioner så att du kan se videon på ditt eget språk: För att visa undertexter med automatisk översättning: Spela upp videon. Klicka på ⚙️ Inställningar (längst ner till höger i videon). Välj Undertexter/CC . Välj Automatisk översättning . Välj önskat språk. För att lyssna med automatisk dubbning (experimentell): Klicka på ⚙️ Inställningar . Välj Ljudspår . Välj språket du vill lyssna på: ℹ️ Översättningar och dubbning genereras automatiskt av Google, kan innehålla fel och den automatiska dubbningen är fortfarande under test, så den är inte tillgänglig för alla språk. Anslut ett filförvar Innan du kan distribuera ett GitHub-filförvar till din WordPress.com-webbplats måste du först ställa in anslutningen mellan de två med hjälp av följande steg: Gå till webbplatssidan på https://wordpress.com/sites/ Klicka på namnet på din webbplats för att visa webbplatsöversikten. Klicka på fliken Distributioner . Klicka på knappen Anslut filförvar . Om du därefter ser en lista över filförvar har du redan anslutit ditt GitHub-konto. Fortsätt till steg 11. Klicka på knappen Installera WordPress.com-appen . Ett nytt fönster öppnas och du uppmanas att logga in på ditt GitHub-konto om du inte redan har gjort det. Därefter visas den här skärmen: Klicka på knappen Auktorisera WordPress.com för utvecklare . Välj den GitHub-organisation eller det konto där ditt filförvar finns. Välj vilket eller vilka filförvar som du vill ansluta: Alla filförvar: Om du väljer det här alternativet får WordPress.com åtkomst till alla aktuella och framtida filförvar som ägs av det valda GitHub-kontot. Detta inkluderar offentliga filförvar som är skrivskyddade. Endast valda filförvar: Om du väljer det här alternativet kan du välja vilka filförvar som WordPress.com kan få åtkomst till på det valda GitHub-kontot. När du har valt ett alternativ klickar du på knappen Installera . Det nya fönstret stängs och du förs tillbaka till WordPress.com. Ditt eller dina valda filförvar bör listas tillsammans med det Github-konto som är associerat med filförvaret: Klicka på Välj bredvid det filförvar som du vill ansluta. Nu bör du se WordPress.com för utvecklare under Auktoriserade GitHub-appar och Installerade GitHub-appar . Hantera distributionsinställningar När du har valt ett filförvar behöver du justera distributionsinställningarna: Distributionsgren: Standardinställningen är standardgrenen i filförvaret (vanligtvis huvudgrenen ), men detta kan ändras till den gren som du vill använda. Målkatalog: Servermappen där du vill distribuera filerna. För tillägg är det /wp-content/plugins/my-plugin-name . För teman är det /wp-content/themes/my-theme-name . För en delvis webbplatsdistribution (dvs. flera tillägg eller teman) kan du använda /wp-content . Innehållet i ett filförvar sammanfogas med det befintliga innehållet på WordPress-webbplatsen i den specificerade katalogen. Automatiska distributioner: Det finns två sätt att distribuera till WordPress.com: Automatisk: När koden har checkats in (committed) distribueras den till din WordPress.com-webbplats. Automatisk distribution rekommenderas för utvecklingswebbplatser. Manuell: Koden distribueras när du begär en distribution . Manuell distribution rekommenderas för produktionswebbplatser. Distributionsläge: Det finns två typer av distribution: Enkel: I det här läget kopieras alla filer från en gren av filförvaret till webbplatsen och distribueras utan efterbehandling. Avancerad: Med det här läget kan du använda ett arbetsflödesskript och aktivera anpassade byggsteg, t.ex. installera Composer-beroenden, utföra kodtestning före distribution och styra fildistribution. Perfekt för filförvar som behöver Composer- eller Node-programvara. Se Avancerad distribution nedan för mer information . När alla inställningar har konfigurerats klickar du på knappen Anslut . Ditt filförvar kommer att läggas till: Observera att du måste utlösa den första distributionen, antingen automatiskt eller manuellt . Du kan sedan ansluta ett annat filförvar när som helst genom att klicka på knappen Anslut filförvar . Avancerad distribution Med Avancerad distribution kan du tillhandahålla ett arbetsflödesskript för att bearbeta filer i ditt filförvar före distribution. Detta öppnar upp för många möjligheter, som att kontrollera din kod för att säkerställa att den uppfyller teamets kodningsstandarder, köra enhetstester, exkludera filer från distributionen, installera beroenden och mycket annat. Titta närmare på våra arbetsflödesrecept för att komma igång. Så här ställer du in avancerad distribution: Ett formulär visas där du kan konfigurera distributionen. Klicka på filförvarets namn för att hantera anslutningen. Välj Avancerat på höger sida under Välj ditt distributionsläge . Om filförvaret redan innehåller en arbetsflödesfil kan du välja den här. Systemet kontrollerar filen för eventuella fel. Om inga fel hittas, fortsätt till steg 7. Du kan också välja alternativet Skapa nytt arbetsflöde för att lägga till en förkonfigurerad arbetsflödesfil. Om du väljer det här alternativet skrivs arbetsflödesfilen wpcom.yml över om den redan finns i ditt filförvar. Klicka på knappen Installera arbetsflöde åt mig för att checka in (commit) arbetsflödesfilen i filförvaret. När ett arbetsflöde har lagts till och verifierats klickar du på Uppdatera . Ditt filförvar kommer nu att använda avancerad distribution. Distribuera din kod När du har anslutit ditt GitHub-filförvar till en webbplats är nästa steg att faktiskt distribuera koden. Det finns två distributionsmetoder att välja mellan: Automatisk och Manuell . Automatisk distribution rekommenderas inte för live produktionswebbplatser, eftersom eventuella kodändringar i filförvaret distribueras automatiskt från GitHub till den live webbplatsen. Överväg istället att konfigurera automatisk distribution till en utvecklingswebbplats och synkronisera den till produktion när du är klar. Manuell distribution ger dig mer kontroll över när dina kodändringar skickas live, eftersom du måste utlösa varje distribution manuellt. Vi rekommenderar manuell distribution om du inte vill använda en utvecklingswebbplats. Så här utlöser du en distribution manuellt: Gå till webbplatssidan på https://wordpress.com/sites/ Klicka på namnet på din webbplats för att visa webbplatsöversikten. Klicka på fliken Distributioner . Klicka på ellipsmenyn (⋮) för det filförvar som du vill distribuera. Välj Utlös manuell distribution . Du bör se ett bannermeddelande med texten ”Körning av distribution skapad” och distributionsstatusen kommer att ändras till ”Köad”. Vänta tills distributionen har slutförts (statusen ändras till ”Distribuerad”). Klicka på ellipsmenyn (⋮) igen och välj Se distributionskörningar . I distributionskörningsloggen visas författaren och distribuerad incheckning (commit). Om du klickar på posten för distributionskörning kan du visa mer information. Hantera befintliga anslutningar Så här hanterar du dina befintliga GitHub-filförvaranslutningar: Gå till webbplatssidan på https://wordpress.com/sites/ Klicka på namnet på din webbplats för att visa webbplatsöversikten. Klicka på fliken Distributioner . Du bör sedan se anslutningslistan. Anslutningslistan visas om det finns minst en anslutning mellan ett GitHub-filförvar och din webbplats. Listan innehåller relevant information för varje anslutning, såsom filförvarets namn och gren, den senaste incheckning (commit) som distribuerades till en webbplats, när det hände, var koden placerades, hur lång tid distributionskörningen tog och dess status. Det finns ytterligare åtgärder tillgängliga om du klickar på ellipsmenyn (⋮): Utlös manuell distribution: Startar en distributionskörning på den senaste incheckningen (commit) av den konfigurerade grenen. Se distributionskörningar: Öppnar vyn för distributionskörningsloggar för det anslutna filförvaret. Konfigurera anslutning: Öppnar vyn Hantera anslutning för filförvaret. Koppla från filförvar: Tar bort anslutningen mellan filförvaret och webbplatsen. Distributionskörningsloggar Distributionskörningsloggar tillhandahåller ett detaljerat steg-för-steg-register för varje distribution, oavsett om den utlöstes automatiskt eller manuellt. Dessa loggar hjälper dig att spåra ändringar, övervaka distributionsstatus och felsöka eventuella problem som uppstår. Med åtkomst till loggar från de senaste 10 körningarna inom 30 dagar kan du enkelt granska vad som har hänt under varje distribution och säkerställa att allt fungerar smidigt. Så här kontrollerar du loggarna för en distribution: Gå till webbplatssidan på https://wordpress.com/sites/ Klicka på namnet på din webbplats för att visa webbplatsöversikten. Klicka på fliken Distributioner . Klicka på ellipsmenyn (⋮) bredvid det filförvar som du vill visa loggar för. Välj Se distributionskörningar . Listvyn Distributionskörningar visar incheckningar (commits) som har distribuerats till webbplatsen, distributionsstatus, datum och varaktighet. Klicka var som helst på en körning för att expandera och visa mer information om distributionen. Loggarna tillhandahåller ett register över alla utförda kommandon, från att hämta kod från GitHub till att placera den i målkatalogen. Du kan expandera logg-rader för att se mer information genom att klicka på Visa mer . Koppla från ett filförvar När du kopplar från ett GitHub-filförvar från din webbplats kommer eventuella framtida ändringar av filförvaret inte längre att påverka webbplatsen. Som standard stannar de distribuerade filerna kvar på din webbplats, men du har möjlighet att ta bort dem under frånkopplingsprocessen. Så här tar du bort ett filförvar: Gå till webbplatssidan på https://wordpress.com/sites/ Klicka på namnet på din webbplats för att visa webbplatsöversikten. Klicka på fliken Distributioner . Klicka på ellipsmenyn (⋮) för filförvaret. Välj Koppla från filförvar . Ett dialogfönster visas. Klicka på reglaget för att ta bort associerade filer från webbplatsen. Klicka på Koppla från filförvar för att stänga dialogrutan och koppla från filförvaret. Observera att WordPress.com för utvecklare fortfarande fortfarande visas i Installerade GitHub-appar och Auktoriserade GitHub-appar . Det beror på att WordPress.com fortfarande har åtkomst till filförvaret, men anslutningen har tagits bort. Koppla från WordPress.com från GitHub Du kan också välja att återkalla WordPress.coms åtkomst till ditt Github-konto. Du kan göra det när som helst genom att gå till dina applikationsinställningar på GitHub. Så här återkallar du auktoriserad appåtkomst till ditt GitHub-konto: Gå till Auktoriserade GitHub-appar . Klicka på Återkalla bredvid WordPress.com för utvecklare . Klicka på knappen Jag förstår, återkalla åtkomst . Även om du återkallar auktoriserad appåtkomst kan kod fortfarande distribueras eftersom appen WordPress.com för utvecklare fortfarande är installerad på de valda kontona. Så här återkallar du åtkomst till WordPress.com-installationen och inaktiverar möjligheten att distribuera kod till din WordPress.com-webbplats: Gå till Installerade GitHub-appar . Klicka på Konfigurera bredvid WordPress.com för utvecklare . Klicka på Avinstallera i området Farozon och sedan på OK när du uppmanas till det. Att ta bort WordPress.com från listan över auktoriserade appar betyder inte att filförvaren tas bort eller slutar att fungera. Dina filförvar kommer fortfarande att finnas på GitHub efter att du har återkallat WordPress.coms åtkomst, men WordPress.com kan inte längre distribuera kod. Relaterade guider Skapa en utvecklingswebbplats 7 minuters läsning Säkerhetskopiera och återställ din webbplats 8 minuters läsning Lägg till kod i sidhuvuden 2 minuters läsning Kom åt din webbplats databas 3 minuters läsning I denna guide Videohandledning Anslut ett filförvar Hantera distributionsinställningar Avancerad distribution Distribuera din kod Hantera befintliga anslutningar Distributionskörningsloggar Koppla från ett filförvar Koppla från WordPress.com från GitHub Har du några frågor? Fråga vår AI-assistent Tillbaka till toppen Kunde du inte hitta det du behövde? Kontakta oss Få svar från vår AI-assistent, med tillgång till mänsklig expertsupport dygnet runt för betalpaket. Ställ en fråga i vårt forum Bläddra bland frågor och få svar från andra erfarna användare. Copied to clipboard! WordPress.com Produkter Webbhotell för WordPress WordPress för byråer Bli en affiliate Domännamn AI-webbplatsbyggare Webbplatsbyggare Skapa en blogg Professional Email Webbdesigntjänster WordPress Studio Enterprise WordPress Funktioner Översikt WordPress-teman WordPress-tillägg WordPress-mönster Google Apps Resurser WordPress.com-blogg Företagsnamngenerator Logotypskapare WordPress.com-läsaren Tillgänglighet Ta bort prenumerationer Hjälp Supportcenter Guider Kurser Forum Kontakt Utvecklarresurser Företag Om Press Användarvillkor Integritetspolicy Sälj eller dela inte min personliga information Integritetsnotis för användare i Kalifornien Deutsch Español Français Bahasa Indonesia Italiano Nederlands Português do Brasil Svenska Türkçe Русский العربية עִבְרִית 日本語 한국어 简体中文 繁體中文 English Deutsch Español Français Bahasa Indonesia Italiano Nederlands Português do Brasil Svenska Türkçe Русский العربية עִבְרִית 日本語 한국어 简体中文 繁體中文 English Mobilappar Ladda ner på App Store Skaffa det på Google Play Sociala medier WordPress.com på Facebook WordPress.com på X (Twitter) WordPress.com på Instagram WordPress.com på YouTube Automattic Automattic Jobba med oss Laddar in kommentarer … Skriv en kommentar … E-post (Obligatorisk) Namn (Obligatorisk) Webbplats WordPress.com Support Registrera Logga in Kopiera kortlänk Rapportera detta innehåll Hantera prenumerationer | 2026-01-13T09:29:34 |
https://l.facebook.com/l.php?u=https%3A%2F%2Fwww.instagram.com%2F&h=AT1_vKZMitYOeQZ74EnQuhQT4T-BwHCNLNMCGBlcKmxA6t0nfPwQwtxn_vqJ1DblNiAA19De6TVwsTf2ZNYoSc3kq_RapkegO629XKbtHlMAv9cC-LMGVvAgw6D6zimX_TB_NRw-C7LY04D9 | Facebook Facebook 이메일 또는 휴대폰 비밀번호 계정을 잊으셨나요? 새 계정 만들기 일시적으로 차단됨 일시적으로 차단됨 회원님의 이 기능 사용 속도가 너무 빠른 것 같습니다. 이 기능 사용에서 일시적으로 차단되었습니다. Back 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T09:29:34 |
https://www.ecns.cn/video/2026-01-02/detail-iheymvap1610658.shtml | (W.E. Talk) Experts on 2026: China's 15th Five-Year Plan significant for the World --> 中文 Home News Ecns Wire Business Travel Photo Video Voices RIGHT BG LINE Text: A A A Print Video (W.E. Talk) Experts on 2026: China's 15th Five-Year Plan significant for the World 2026-01-02 08:41:18 Ecns.cn Editor : Meng Xiangjun ECNS App Download The year 2026 marks the start of China's 15th Five-Year Plan (2026–2030) period. Looking ahead to the new year, Su Hao, founding director of Center for Strategy and Peace Studies from China Foreign Affairs University, and associate dean of the Institute of Global Governance and Development of Renmin University of China, stated in the latest W.E. Talk that as the world's second-largest economy, China's economic development boasts a solid foundation and broad room for progress, while also providing important impetus and stable support for the global economy. Benjamin Norton, founder of the Geopolitical Economy Report, U.S. foreign policy expert, also emphasized that the 15th Five-Year Plan is not only crucial for China but also of great significance to the world. China's contributions in areas such as scientific and technological innovation benefit not only its own people but also people around the globe.（Guan Na, Gan Tian, Zhao Li） More Photo Beijing-Tangshan intercity railway starts full-line operation Passenger trips of 3 major Hainan airports exceed 50 million in 2025 First 'Grassland curling' attracts 350 competitors China launches two new satellites for space target detection test People perform 'circle dance' to pray for a bountiful new year in Qingha First batch of China's emergency humanitarian aid arrives in Cambodia Central London illuminated to welcome 2026 Chinese Foreign Minister meets Cambodian Deputy PM in Yunnan Exploring vivid sports competition throughout 2025 Exploring stunning winter scenery in Altay China's first L3 self-driving car debuts in Chongqin Grand bridge ready for traffic operation in Guizhou Harbin's celebrity snowman lights up winter night Southbound Travel for Guangdong Vehicles scheme implemented for entry into urban Hong Kong China's Feng/Huang claim mixed doubles title at BWF World Tour Finals Exploring overwintering migratory birds in Poyang Lake Xi presents orders to promote two military officers to rank of genera Inner Mongolia holds winter festival Memorial held for victims of Bondi Beach shooting in Sydney New year display unveiled at Times Square Night view of the 27th Harbin Ice and Snow World resembles fairy tale China launches island-wide special customs operations in Hainan FTP Why the world comes to Yiwu Exploring Hainan Free Trade Port before island-wide special customs operations Japanese bid farewell to the last two giant pandas Hainan's tallest building reaches key construction milestone Newly released Russia-transferred Japanese Unit 731 atrocity archives reveal human experiments, biological warfare committed by Japanese Imperial Army: FM Hainan FTP ready for island-wide independent customs operation Witnesses of a painful past, still waiting for an apology Geminid meteor shower seen across China Team China Sun Yingsha, Wang Chuqin win silver at the WTT Finals Hong Kong 2025 Kum Tag Desert welcomes its first snowfall this winter China's Lin Shidong advances to quarterfinals at WTT United States Smash Main tower of 27th Harbin Ice and Snow World topped out in NE China China launches sitellites for UAE, Egypt, Nepal Photo exhibition in Kazakhstan marks 70th founding anniversary of China's Xinjiang Uygur Autonomous Region Most popular in 24h More Top news (W.E. Talk) Experts on 2026: China's 15th Five-Year Plan significant for the World (W.E. Talk) Looking ahead to 2026: As geopolitical conflict risks intensify, all parties seek opportunities amid crisis through strategic moves (W.E. Talk) Experts look to 2026: Seizing opportunities amid crises, forging ahead after breakthroughs South Korea's presidential office moves back to Cheong Wa Dae The Dunhuang Flying Dancers in the 1,360°C kiln fire More Video (W.E. Talk) Experts on 2026: China's 15th Five-Year Plan significant for the World (W.E. Talk) Experts look to 2026: Seizing opportunities amid crises, forging ahead after breakthroughs LINE Media partners: People's Daily | Xinhua | CGTN | China Daily Back to top About Us | Jobs | Contact Us | Privacy Policy Copyright ©1999-2026 Chinanews.com. All rights reserved. Reproduction in whole or in part without permission is prohibited. [ 网上传播视听节目许可证（0106168) ] [ 京ICP证040655号 ] [ 京公网安备 11010202009201号 ] [ 京ICP备05004340号-1 ] --> --> | 2026-01-13T09:29:34 |
https://cloudflare.com/fr-fr/ai-solution/ | Solutions d'intelligence artificielle (IA) | Cloudflare S’inscrire Langues English English (United Kingdom) Deutsch Español (Latinoamérica) Español (España) Français Italiano 日本語 한국어 Polski Português (Brasil) Русский 繁體中文 简体中文 Plateforme Cloud de connectivité Le cloud de connectivité Cloudflare propose plus de 60 services d'amélioration des performances, de la sécurité et de la connectivité réseau. Enterprise Pour les grandes et moyennes entreprises PME Pour les petites entreprises Partenaire Devenez partenaire de Cloudflare Scénarios d'utilisation Moderniser les applications Accélérer les performances Garantir la disponibilité des applications Optimiser l'expérience web Moderniser la sécurité Remplacer les VPN Se protéger contre le phishing Sécuriser les applications et les API web Moderniser les réseaux Coffee shop networking Moderniser le WAN Simplifier votre réseau d'entreprise Sujets pour cadres dirigeants Adoptez l'IA Intégrez l'IA à vos effectifs et à vos expériences numériques Sécurité de l'IA Sécurisez vos applications d'IA agentique et d'IA générative Conformité des données Rationalisez la conformité et minimisez les risques Chiffrement post-quantique Protégez vos données et respectez les normes de conformité Secteurs Santé Banque Commerce Jeux Secteur public Ressources Guides produits Architectures de référence Rapports d'analyse S'informer Événements Démos Webinaires Ateliers Demander une démo Produits Produits Sécurité de l&#039;espace de travail Accès réseau Zero Trust Passerelle web sécurisée Sécurité du courrier électronique CASB (Cloud Access Security Broker) Sécurité des applications Protection anti-DDoS de la couche 7 Pare-feu applicatif web (WAF) Sécurité des API Gestion des bots Performances des applications CDN DNS Routage intelligent Load balancing Connectivité réseau et SASE Protection anti-DDoS des couches 3/4 NaaS/SD-WAN Pare-feu en tant que service Interconnexion réseau offres et tarifs Offres Enterprise Offres pour PME Offres pour particuliers Comparer les offres Services mondiaux Offres support et Success groupées Expérience Cloudflare optimisée Services professionnels Mise en œuvre dirigée par des experts Gestion de compte technique Gestion technique ciblée Service des opérations de sécurité Surveillance et réponse aux incidents de Cloudflare Enregistrement de nom de domaine Acheter et gérer des domaines 1.1.1.1 Résolveur DNS gratuit Ressources Guides produits Architectures de référence Rapports d'analyse Démonstrations et tours d'horizon des produits M'aider à choisir Développeurs Documentation Bibliothèque pour développeurs Documentation et guides Démos d'applications Découvrez ce que vous pouvez développer Didacticiels Didacticiels de développement étape par étape Architecture de référence Schémas et modèles de conception Produits Intelligence artificielle AI Gateway Observez et contrôlez les applications IA Workers AI Exécutez des modèles d'apprentissage automatique sur notre réseau Calcul Observability Journaux, indicateurs et traces Workers Développez et déployez des applications serverless Médias Images Transformez et optimisez les images Realtime Développez des applications audio/vidéo en temps réel Stockage et base de données D1 Créez des bases de données SQL serverless R2 Stockez vos données sans frais de trafic sortant élevés Offres et tarifs Workers Développez et déployez des applications serverless Workers KV Un espace de stockage clé-valeur serverless pour les applications R2 Stockez vos données sans les coûteux frais de trafic sortant Découvrez nos projets Témoignages de clients Démo de l'IA en 30 secondes Guide rapide de la prise en main Explorer Workers Playground Développez, testez et déployez Discord pour développeurs Rejoignez la communauté Commencer à développer Partenaires Réseau de partenaires Développez, innovez et répondez aux besoins de vos clients grâce à Cloudflare Portail des partenaires Localisez vos ressources et enregistrez vos contrats Types de partenariats Programme PowerUP Développez votre activité tout en assurant la connectivité et la sécurité de vos clients Partenaires technologiques Découvrez notre écosystème de partenaires technologiques et d'intégrateurs Intégrateurs de systèmes mondiaux Soutenez la fluidité de la transformation numérique à grande échelle Fournisseurs de services Découvrez notre réseau d'estimés fournisseurs de services. Programme Agency en libre-service Gérez des comptes en libre-service pour vos clients Portail peer-to-peer Informations sur le trafic pour votre réseau Trouvez un partenaire Dynamisez votre entreprise dans le cadre du programme de partenariat PowerUP : entrez en contact avec les partenaires Cloudflare Powered+. Ressources S'informer Démos et découvertes de produits Démos de produits à la demande Études de cas Favorisez votre réussite avec Cloudflare Webinaires Discussions instructives Ateliers Ateliers virtuels Bibliothèque Guides utiles, feuilles de route et autres Rapports Informations issues des recherches Cloudflare Blog Analyses techniques approfondies et actualités produits Centre d'apprentissage Outils de formation et contenu pratique Développer Architecture de référence Guides techniques Guides des solutions et des produits Documentation des produits Documentation Documentation pour les développeurs Explorer theNET Informations pour les dirigeants des entreprises numériques Cloudflare TV Séries et événements innovants Cloudforce One Recherche et opérations sur les menaces Radar Tendances en matière de trafic Internet et de sécurité Rapports d'analyse Rapports d'étude sectoriels Événements Événements régionaux à venir Confiance, confidentialité et conformité Informations et politiques en matière de conformité Assistance Nous contacter Forum de la communauté Vous avez perdu l'accès à votre compte ? Discord pour développeurs Obtenir de l'aide Entreprise Informations sur l'entreprise Leadership Découvrez nos dirigeants Relations investisseurs Informations pour les investisseurs Presse Explorez les actualités récentes Emploi Découvrez les postes vacants Confiance, confidentialité et sécurité Confidentialité Politiques, données et protection Confiance Politiques, processus et sécurité Conformité Certification et réglementation Transparence Politiques et déclarations Intérêt public Assistance humanitaire Projet Galileo Administration Projet Athenian Élections Cloudflare for Campaigns Santé Projet Fair Shot Réseau mondial Points d'implantation mondiaux et état du réseau Connexion Contacter le service commercial Accélérez votre parcours en matière d'IA Vous disposez de votre propre vision en matière d'IA. La plateforme unifiée de Cloudflare regroupe des services de sécurité, des services de connectivité et des services pour développeurs afin de vous aider à concrétiser cette vision en bénéficiant de davantage de vitesse et de sécurité. Demander un entretien Problème La complexité réduit les effets de l'IA Les entreprises disposent d'objectifs pour le moins ambitieux concernant l'IA. Toutefois, bon nombre de ces projets sont retardés par des lenteurs au niveau du développement, des problèmes en matière d'évolutivité et de nouveaux types de risques. Lenteurs au niveau du développement de l'IA L'innovation en matière d'IA est entravée par les chaînes d'outils complexes et les évolutions constantes au sein du paysage technologique. Les difficultés liées à l'évolutivité de l'IA La croissance de l'IA est freinée par les bases utilisateur mondiales, les pics d'utilisation et le manque de flexibilité des coûts en matière de calcul. Le risque croissant lié à l'IA Les effets de l'IA sont jugulés par les limitations en termes de visibilité, la complexité des processus de gestion des risques et les problèmes de mauvaise gouvernance en matière de données, notamment en ce qui concerne le code généré par IA. SOLUTION Cloudflare constitue votre point de contrôle unique en matière d'IA Le cloud de connectivité Cloudflare permet aux entreprises de développer, de connecter et de faire évoluer leurs applications IA, mais aussi de protéger l'ensemble du cycle de vie de ces dernières depuis une plateforme mondiale unique. Développez l'IA Une IA sécurisée Principaux besoins en matière d'IA Définissez une stratégie IA ou restez à la traîne Les avancées et les scénarios d'utilisation débloqués par l'IA au cours de l'année passée montrent le vaste potentiel de cette technologie pour transformer la manière dont nous travaillons et consommer de l'information. Les pressions sont de plus en plus élevées en faveur de la proposition d'une stratégie IA couvrant la manière dont votre entreprise consomme cette technologie, dont vous protégez votre propriété intellectuelle, ainsi que la manière dont vous ajoutez des composants assistés par IA à vos applications internes et externes. Innovez plus rapidement Développez des applications IA plus rapidement, à moindre coût et avec une agilité accrue, peu importe le modèle IA utilisé. Portée mondiale Assurez une expérience fiable et rapide sur des piles IA complexes et des bases utilisateur mondiales. Sécurité intégrée Comprenez mieux les risques liés à l'IA et gérez-les sans vous perdre dans plusieurs tableaux de bord ou le flot constant des mises à jour de vos politiques. E-book : Guide pour entreprises de la sécurisation et de l'évolutivité de l'IA Découvrez pourquoi les entreprises connaissent des difficultés pour développer et sécuriser efficacement une infrastructure IA à grande échelle, les raisons pour lesquelles l'infrastructure IA des hyperscalers ne parviennent souvent pas à assurer ses fonctions, ainsi que les solutions qui permettent de surmonter ces problèmes. Lire l'e-book Les leaders mondiaux, dont 30 % des entreprises classées au Fortune 1000, s'appuient sur Cloudflare Prêts à avoir une conversation avec un spécialiste ? Demander un entretien Fonctionnement Une plateforme unifiée de services de sécurité, de services de connectivité et de services pour développeurs Déjà utilisés par 80 % des 50 principales entreprises du secteur de l'IA générative, les services IA proposés par Cloudflare sont conçus pour s'exécuter partout sur notre réseau mondial, implanté dans plus de 330 villes. Développer Développez des applications IA full-stack disposant d'un accès à plus de 50 modèles IA disponibles sur notre réseau mondial. Développez et exécutez des agents sans débourser quoi que ce soit pour le temps d'attente. En savoir plus Connecter Contrôlez et observez vos applications soutenues par IA, tout en réduisant vos coûts d'inférence et en routant votre trafic de manière dynamique. Mettez en place des serveurs MCP qui s'exécuteront sur l'ensemble de notre réseau mondial. En savoir plus Protéger Étendez votre visibilité, atténuez les risques et protégez vos données tout au long du cycle de vie de l'IA. Contrôlez la manière dont les robots d'exploration IA peuvent accéder à votre contenu web. En savoir plus Cloudflare aide Indeed à identifier et à gérer l'utilisation du Shadow AI (IA fantôme) Indeed, l'un des principaux sites consacrés à l'emploi, souhaitait disposer d'une meilleure visibilité et d'un plus haut degré de contrôle sur les applications IA utilisées par ses collaborateurs. Il a alors déployé l'AI Security Suite proposée par Cloudflare , qui aide l'entreprise à identifier les schémas d'utilisation de l'IA et à appliquer des politiques régissant l'utilisation des données. Indeed est désormais sur la bonne voie pour réaliser le juste équilibre entre l'innovation et le contrôle. « Cloudflare nous aide à identifier les risques liés à l'IA fantôme, mais aussi à bloquer les applications IA non autorisées et les chatbots. » DÉMARRAGE Offre gratuite Offres pour PME Pour les entreprises Bénéficiez d'une recommandation Demandez une démo Contacter le service commercial SOLUTIONS Cloud de connectivité Services pour applications SASE et sécurité de l'espace de travail Services réseau Plateforme pour développeurs SUPPORT Centre d'aide Support client Forum de la communauté Développeurs Discord Vous avez perdu l'accès à votre compte ? Statut Cloudflare CONFORMITÉ Ressources en conformité Confiance RGPD IA responsable Rapport de transparence Signaler un abus INTÉRÊT PUBLIC Projet Galileo Projet Athenian Cloudflare for Campaigns Projet Fair Shot ENTREPRISE À propos de Cloudflare Carte du réseau Notre équipe Logos et dossier de presse Diversité, équité et inclusion Impact/ESG © 2026 Cloudflare, Inc. Politique de confidentialité Conditions d’utilisation Signaler des problèmes de sécurité Fiabilité et sécurité Préférences relatives aux cookies Marque commerciale | 2026-01-13T09:29:34 |
https://www.atlassian.com/es/software/jira/guides/projects/tutorials | Tutoriales sobre proyectos de Jira Software | Atlassian Close ¿Quieres ver esta página en tu idioma ? Todos los idiomas Elige tu idioma 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Obtener gratis Funciones Todas las funciones Rovo en Jira Back Soluciones Equipos Casos prácticos Tamaño de la empresa Equipos Marketing Ingeniería Diseño Operaciones TI Casos prácticos Inicio Planificación Gestión de campañas Gestión ágil de proyectos Gestión de programas Tamaño de la empresa Enterprise Back Guía del producto Plantillas Plantillas Todas las plantillas Desarrollo de software Marketing Diseño Ventas Operaciones Gestión de asistencia RR. HH. Legal Operaciones de TI Finanzas Plantillas de Jira Service Management Back Precios Más + Menos - Obtener gratis Back Obtener gratis Inicio Introducción a Jira Jira para equipos 7 pasos para ponerse en marcha con Jira Proyectos Presentación Tutoriales Recursos Paneles Presentación Tutoriales Recursos Actividades/incidencias Presentación Tutoriales Recursos Flujos de trabajo Presentación Tutoriales Recursos Integraciones Presentación Tutoriales Recursos Informes y cuadros de mandos Presentación Tutoriales Recursos Información Presentación Tutoriales Recursos Permisos Presentación Tutoriales Recursos JQL Presentación Tutoriales Chuleta Recursos Navegación Overview Tutorials Resources Automatización Presentación Tutoriales Recursos "Timeline" (Cronograma) Presentación Tutoriales Recursos Advanced Roadmaps Presentación Tutoriales Recursos Jira para móviles Presentación Tutoriales Recursos Más información sobre Jira Ediciones de Jira Opciones de alojamiento Tutoriales sobre creación de proyectos en Jira Crea un nuevo proyecto en Jira Selecciona "Crear proyecto" en la sección "Proyectos" en la barra de navegación superior. Ten en cuenta que no verás esta opción si no tienes los permisos para crear proyectos. Estructura un proyecto en Jira No existe un enfoque único para estructurar un proyecto en Jira. Sin embargo, sería útil reconocer que los proyectos de Jira no pretenden llegar a un solo resultado específico o exclusivo. Más bien, capturan los procesos continuos. Con eso en mente, aquí tienes algunas estrategias para considerar a la hora de pensar cómo estructurar tu proyecto en Jira: Por equipo: los proyectos basados en equipos son otro modelo organizativo común. Esto permite que tu trabajo refleje tu organización social y es práctico en configuraciones menos interdisciplinares, ya que facilita la gestión de los permisos de proyecto. Por unidad de negocio: puedes organizarte en unidades empresariales más grandes (marketing, TI, etc.). Es posible que los tipos de trabajo sigan patrones similares, lo que facilitará la configuración de los flujos de trabajo y, sobre todo, los tipos de incidencias. Por producto: si tu equipo de desarrollo de software va a hacer un uso intensivo del sistema de publicaciones y versiones de Jira, tendrás que considerar seriamente la posibilidad de organizar tus proyectos por productos que se puedan publicar o grupos de trabajo que compartan un ciclo de publicación común. Incluso dentro de estas categorías, puedes ser todo lo específico o todo lo generalizado que quieras. Por ejemplo, si estructuras por producto, puedes seguir subcategorizando por funciones específicas. Compañía Resumen Eventos Blogs Relaciones con los inversores Atlassian Foundation Kit de prensa Ponte en contacto con nosotros. Productos Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Ver todos los productos Recursos Servicio técnico Compra y licencia Comunidad de Atlassian Base de conocimientos Marketplace Mi cuenta Crear tique de asistencia Tutorial Socios Formación y certificación Documentación Recursos para desarrolladores Servicios empresariales Ver todos los recursos Copyright © 2025 Atlassian Política de privacidad Términos Impressum Selecciona un idioma Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:34 |
https://issues.jenkins.io/secure/CreateSubTaskIssue!default.jspa?parentIssueId={0}&returnUrl=/secure/issues#sidebar | Log into Atlassian - Jenkins Jira Log in Skip to main content Skip to sidebar Dashboards Projects Issues Give feedback to Atlassian Help Keyboard Shortcuts About Jira Jira Credits Log In 📢 Jenkins core issues have been migrated to GitHub , no new core issues can be created in Jira Atlassian Jira Project Management Software About Jira Report a problem Powered by a free Atlassian Jira open source license for The Linux Foundation. Try Jira - bug tracking software for your team. Atlassian | 2026-01-13T09:29:34 |
https://www.atlassian.com/zh/software/jira/guides/projects/tutorials | Jira Software 项目教程 | Atlassian Close 是否使用 您的语言 查看此页面？ 所有语言 选择您的语言 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 免费获取 功能 所有功能 Jira 中的 Rovo Back 解决方案 Teams 用例 公司规模 Teams 营销 工程 设计 运营 IT 用例 入门 规划 活动管理 敏捷项目管理 计划管理 公司规模 Enterprise Back 产品指南 模板 模板 所有模板 软件开发 营销 设计 销售 运营 服务管理 人力资源 法律 IT 运营 金融 Jira Service Management 模板 Back 定价 更多 + 更少 - 免费获取 Back 免费获取 入门 Jira 简介 适用于团队的 Jira 开始使用 Jira 的 7 个步骤 项目 概述 教程 资源 板 概述 教程 资源 工作项/事务 概述 教程 资源 工作流 概述 教程 资源 集成 概述 教程 资源 报告和仪表盘 概述 教程 资源 洞察信息 概述 教程 资源 权限 概述 教程 资源 JQL 概述 教程 速查表 资源 导航 Overview Tutorials Resources 自动化 概述 教程 资源 时间表 概述 教程 资源 Advanced Roadmaps 概述 教程 资源 Jira 移动应用 概述 教程 资源 有关 Jira 的更多信息 Jira 的版本 托管选项 在 Jira 中创建项目教程 在 Jira 中创建新项目 从顶部导航栏的“项目”中选择“创建项目”。请注意，如果您没有创建项目的权限，则看不到此选项。 在 Jira 中组织项目 在 Jira 中组织项目没有普适性方法。但是，认识到 Jira 项目并非针对单一结果量身定制或专有可能会有所帮助。然而，它们记录了持续的努力。考虑到这一点，以下是您在思考如何在 Jira 中组织项目时可能要考虑的几种方法： 按团队 - 基于团队的项目是另一种常见的组织模式。这使您的工作能够反映您的社会组织，并且在较少跨职能的设置中很方便，因为它允许更直接的项目权限管理。 按业务部门 - 您可能想要围绕较大的业务部门（例如市场营销、IT 等）进行组织。工作类型可能会属于相似的模式，这使得设置工作流（尤其是事务类型）更加方便。 按产品 - 如果你们是一个想要大量使用 Jira 发布和版本控制系统的软件开发团队，您将需要认真考虑按可发布的产品或共享相同发布周期的工作组来组织项目。 即使在这些类别中，您也可以根据需要实现精细度或广度。例如，如果您按产品进行组织，则可以继续按特定功能进行子分类。 企业 诚聘英才 活动 博文 投资者关系 Atlassian Foundation 徽标 新闻资料袋 联系我们 产品 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket 查看所有免费产品 资源 技术支持 购买和许可 Atlassian 社区 知识库 Marketplace 我的帐户 创建支持请求单 学习 合作伙伴 培训和认证 文档 开发人员资源 企业服务 查看全部资源 版权所有 © 2025 Atlassian 隐私政策 条款 Impressum 选择语言 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:34 |
https://pt-br.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT2sNMHYzitoPSEfJsXkqvloqRUxIJIopp28rQfaItrhz2aN24BUXCxLByo7RN0rtEGnzmfDjJvzUhkboKt6Otzh5ksbYAnTsKOxnBOv_JCKZKKQjl3T5Sp4HoTs5V-POj4uS0aXV3zLAErg | Facebook Facebook Email ou telefone Senha Esqueceu a conta? Criar nova conta Você está bloqueado temporariamente Você está bloqueado temporariamente Parece que você estava usando este recurso de forma indevida. Bloqueamos temporariamente sua capacidade de usar o recurso. Back Português (Brasil) 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Français (France) Deutsch Cadastre-se Entrar Messenger Facebook Lite Vídeo Meta Pay Meta Store Meta Quest Ray-Ban Meta Meta AI Mais conteúdo da Meta AI Instagram Threads Central de Informações de Votação Política de Privacidade Central de Privacidade Sobre Criar anúncio Criar Página Desenvolvedores Carreiras Cookies Escolhas para anúncios Termos Ajuda Upload de contatos e não usuários Configurações Registro de atividades Meta © 2026 | 2026-01-13T09:29:34 |
https://www.atlassian.com/zh/software/jira/guides/issues/tutorials | Jira Software 事务教程 | Atlassian Close 是否使用 您的语言 查看此页面？ 所有语言 选择您的语言 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 免费获取 功能 所有功能 Jira 中的 Rovo Back 解决方案 Teams 用例 公司规模 Teams 营销 工程 设计 运营 IT 用例 入门 规划 活动管理 敏捷项目管理 计划管理 公司规模 Enterprise Back 产品指南 模板 模板 所有模板 软件开发 营销 设计 销售 运营 服务管理 人力资源 法律 IT 运营 金融 Jira Service Management 模板 Back 定价 更多 + 更少 - 免费获取 Back 免费获取 入门 Jira 简介 适用于团队的 Jira 开始使用 Jira 的 7 个步骤 项目 概述 教程 资源 板 概述 教程 资源 工作项/事务 概述 教程 资源 工作流 概述 教程 资源 集成 概述 教程 资源 报告和仪表盘 概述 教程 资源 洞察信息 概述 教程 资源 权限 概述 教程 资源 JQL 概述 教程 速查表 资源 导航 Overview Tutorials Resources 自动化 概述 教程 资源 时间表 概述 教程 资源 Advanced Roadmaps 概述 教程 资源 Jira 移动应用 概述 教程 资源 有关 Jira 的更多信息 Jira 的版本 托管选项 Jira 工作项教程 创建工作项 在顶部导航栏中选择“创建”。您的工作项将出现在项目的待办事项列表或面板中。 查找工作项 进行全局搜索并在整个站点中查找工作项 借助顶部导航栏中的搜索栏，您可以通过工作项 ID 或关键字快速搜索整个实例中的工作项。您可以按项目、经办人和/或状态缩小搜索范围。 进行上下文搜索，在项目的面板、路线图或待办事项列表视图中查找工作项 搜索栏可在路线图、待办事项列表和面板视图中找到。如果可以在该特定视图中找到这些工作项，则工作项就会出现在搜索结果中。 通过工作项导航器在给定项目中查找工作项 导航到侧边栏导航中的“工作项”。在屏幕右上角的“基本”或“JQL”模式之间切换。在“基本”模式下，您可以在搜索栏中输入关键字和/或使用下拉菜单按项目、工作类型、状态、经办人以及工作项可能包含的任何字段筛选工作项。在“JQL”模式下，您可以使用 JQL（Jira 查询语言） 构建结构化查询来搜索工作项。 请注意，默认情况下工作项导航器在团队管理的项目中不可用。可前往 项目设置 > 功能 > 工作项导航器 启用此功能。 向项目添加工作类型 在团队管理的项目中： 在左侧边栏导航中选择“项目设置”，再选择“工作类型”，然后点击“+ 添加工作类型”。 拖放您想要在工作类型中包含的字段类型，然后为每个字段类型提供一个名称。您也可以根据需要为每个字段设置默认值。 在公司管理的项目中： 如何链接工作项 打开工作项。 选择工作项模式顶部的 链接工作项 。 选择工作项链接的类型（例如，“此工作项被...屏蔽”）。 通过输入完整的工作项关键字来指定要链接的工作项（例如，ABC-123）。 选择 链接 。 配置工作项的布局 从您的面板中选择任何工作项。 在工作项视图的右下角，选择 配置 。 将工作项字段拖放到相应的区域中。 企业 诚聘英才 活动 博文 投资者关系 Atlassian Foundation 徽标 新闻资料袋 联系我们 产品 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket 查看所有免费产品 资源 技术支持 购买和许可 Atlassian 社区 知识库 Marketplace 我的帐户 创建支持请求单 学习 合作伙伴 培训和认证 文档 开发人员资源 企业服务 查看全部资源 版权所有 © 2025 Atlassian 隐私政策 条款 Impressum 选择语言 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:34 |
https://cn.chinadaily.com.cn/a/202304/26/WS6448baf2a310537989371b37.html | 和评理 - 中国日报网 China Daily Homepage 中文网首页 时评 资讯 C财经 生活 视频 专栏 双语 --> 原创 观天下 地方 --> 登录 注册 观天下 移动新媒体 站内搜索 站内搜索 观天下 China Daily Homepage 中文网首页 时评 资讯 C财经 生活 视频 专栏 双语 --> 漫画 原创 观天下 地方 和评理 和评理 和评理｜有序扩大金融对外开放：为国内经济提供动力，为国际合作搭建桥梁 7 个月 前 和评理 | 美国增兵中东加剧紧张 对话协商方是正道 7 个月 前 和评理 | 阿斯塔纳峰会将为构建更加紧密的中国－中亚命运共同体注入新动力 7 个月 前 和评理 | 北约抹黑中国 意在染指亚太 7 个月 前 和评理｜从“蓝图愿景”到“落地生根” 中非合作论坛结出累累硕果 7 个月 前 和评理｜解决贸易争端，还需美国回归理性 7 个月 前 和评理｜中国稀土行业规范、有序、可持续发展，终将惠及全球 7 个月 前 和评理｜平等、尊重、互利，仍是中美关系走向的关键 7 个月 前 和评理｜用对话沟通妥处中欧经贸分歧：站在历史正确的一边，向新而行 7 个月 前 和评理 | 加强建设性对话 推动中美经贸关系健康发展 7 个月 前 和评理 | 排除各种干扰破坏 校正中美关系航向 7 个月 前 和评理 | 平等尊重是中美交往前提，对话合作是唯一正确选择 7 个月 前 和评理｜单边关税，注定让美国“无尽胜利”的梦想变幻想 7 个月 前 和评理｜严格落实日内瓦经贸会谈共识，切实维护中方权益 7 个月 前 和评理 | 部署武器煽风点火制造紧张 美国将亚太变成“火药桶” 7 个月 前 1 2 3 4 5 6 7 8 9 10 Next >>| 1/40 Next 热点 美联储风波叠加地缘政治不确定性 黄金白银期价再创新高 大型撞击造成月幔“蒸发”？嫦娥六号样品又有新发现 八部门发文助力培育养老服务经营主体 国际金价去年涨幅约70%金价持续上涨如何看 扩大内需 统一大市场建设 优化营商环境： 多地敲定今年发展改革工作重点 美国青年看“窑洞之问” CES现场观察 中美企业海外合作共赢 AdSame ShowCode: 新版中文1227 / 观天下频道首页19.7.17 / C1 Begin AdSame ShowCode: 新版中文1227 / 观天下频道首页19.7.17 / C1 End --> AdSame ShowCode: 新版中文1227 / 观天下频道首页19.7.17 / C2 Begin AdSame ShowCode: 新版中文1227 / 观天下频道首页19.7.17 / C2 End --> AdSame ShowCode: 新版中文1227 / 观天下频道首页19.7.17 / C3 Begin AdSame ShowCode: 新版中文1227 / 观天下频道首页19.7.17 / C3 End --> 为你推荐 换一批 神奇的中国 海外手记 和评理 中国那些事儿 世界说 中国观察 新华社 中国日报网评 侨一瞧 事事关心 每日一词 中国经济网 中国新闻网 环球时报 中央电视台 中央人民广播电台 解放军报 中国新闻周刊 人民日报海外版 中国青年网 经济日报 光明日报 中国军网 求是 中国侨网 消费日报网 中国警察网 参考消息网 中国搜索 海外网 法制网 环球网 中青在线 中工网 中国西藏网 中国台湾网 央广网 光明网 人民网 国际在线 中国网 未来网 每日一词 一财网 新华网 更多 美国贸易霸凌行径正在殃及全球 金沙滩 | 中美经贸摩擦的这些问题你真的清楚吗？（之六）——关于“制造业回流 连遮羞布都不要了！日本将恢复中断30余年的商业捕鲸活动 --> 关于我们 | 联系我们 首页 时评 资讯 财经 生活 视频 专栏 漫画 独家 招聘 地方频道： 北京 天津 河北 山西 辽宁 吉林 黑龙江 上海 江苏 浙江 福建 江西 山东 河南 湖北 湖南 广东 广西 海南 重庆 四川 贵州 云南 西藏 陕西 新疆 深圳 友情链接： 人民网 新华网 中国网 国际在线 央视网 中国青年网 中国经济网 中国台湾网 中国西藏网 央广网 光明网 中国军网 中国新闻网 人民政协网 法治网 网上有害信息举报专区 防范网络诈骗 --> 违法和不良信息举报 互联网新闻信息服务许可证10120170006 信息网络传播视听节目许可证0108263号 京公网安备11010502032503号 京网文[2011]0283-097号 京ICP备13028878号-6 12300电信用户申诉受理中心 12318全国文化市场举报 网站网络110报警网站 --> 中国日报网版权说明：凡注明来源为“中国日报网：XXX（署名）”，除与中国日报网签署内容授权协议的网站外，其他任何网站或单位未经允许禁止转载、使用，违者必究。如需使用，请与010-84883777联系；凡本网注明“来源：XXX（非中国日报网）”的作品，均转载自其它媒体，目的在于传播更多信息，其他媒体如需转载，请与稿件来源方联系，如产生任何问题与本网无关。 版权保护：本网登载的内容（包括文字、图片、多媒体资讯等）版权属中国日报网（中报国际文化传媒（北京）有限公司）独家所有使用。 未经中国日报网事先协议授权，禁止转载使用。给中国日报网提意见：rx@chinadaily.com.cn 首页 时评 资讯 财经 文化 漫画 视频 地方 中文 | English 中国日报版权所有 Content@chinadaily.com.cn | 2026-01-13T09:29:34 |
https://id-id.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT2sNMHYzitoPSEfJsXkqvloqRUxIJIopp28rQfaItrhz2aN24BUXCxLByo7RN0rtEGnzmfDjJvzUhkboKt6Otzh5ksbYAnTsKOxnBOv_JCKZKKQjl3T5Sp4HoTs5V-POj4uS0aXV3zLAErg | Facebook Facebook Email atau telepon Kata Sandi Lupa akun? Buat Akun Baru Anda Diblokir Sementara Anda Diblokir Sementara Sepertinya Anda menyalahgunakan fitur ini dengan menggunakannya terlalu cepat. Anda dilarang menggunakan fitur ini untuk sementara. Back Bahasa Indonesia 한국어 English (US) Tiếng Việt ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch Daftar Masuk Messenger Facebook Lite Video Meta Pay Meta Store Meta Quest Ray-Ban Meta Meta AI Konten Meta AI lainnya Instagram Threads Pusat Informasi Pemilu Kebijakan Privasi Pusat Privasi Tentang Buat Iklan Buat Halaman Developer Karier Cookie Pilihan Iklan Ketentuan Bantuan Pengunggahan Kontak & Non-Pengguna Pengaturan Log aktivitas Meta © 2026 | 2026-01-13T09:29:34 |
https://cn.chinadaily.com.cn/a/202501/20/WS678e23bda310be53ce3f2971.html | 【C财经】农业农村部：多措并举拓宽农民增收致富渠道 - 中国日报网 【C财经】农业农村部：多措并举拓宽农民增收致富渠道 近日，国家统计局公布了最新数据，去年全国农村居民人均可支配收入实现稳步增长。 站内搜索 搜狗搜索 中国搜索 --> 订阅 移动 English 首页 时政 时政要闻 评论频道 理论频道 学习时代 两岸频道 资讯 独家 中国日报专稿 传媒动态 每日一词 法院公告 C财经 证券 独家 科技 产业 视频 专栏 双语 双语财讯 每日一词 双语新闻 新闻热词 译词课堂 --> 漫画 观天下 中国观察 中国日报网评 中国那些事儿 海外手记 侨一瞧 地方 文创 文旅 生活 中国有约 China Daily Homepage 中文网首页 时评 资讯 C财经 生活 视频 专栏 双语 --> 漫画 原创 观天下 地方频道 --> 关闭 中国日报网 > “中国经济高质量发展成效”系列发布会 > 【C财经】农业农村部：多措并举拓宽农民增收致富渠道 来源：中国日报网 2025-01-20 18:21 --> 分享到微信 1月20日，国务院新闻办公室举行“中国经济高质量发展成效”系列新闻发布会，农业农村部副部长张兴旺，农业农村部总农艺师、种植业管理司（农药管理司）司长潘文博，发展规划司司长陈邦勋介绍“夯实‘三农’基本盘，扎实推进乡村全面振兴”有关情况，并答记者问。 农业农村部发展规划司司长陈邦勋 增加农民收入是“三农”工作的中心任务。前不久的中央经济工作会议上提到，要千方百计拓展农民增收渠道。对此，农业农村部发展规划司司长陈邦勋表示，2024年，农业农村部门贯彻落实党中央、国务院部署要求，多措并举拓宽农民增收致富渠道： 常态化开展产销对接、品牌推广和消费促进等活动，促进农产品顺畅销售；积极发展新产业新业态，推介乡村休闲旅游精品线路和精品景点，促进农民就地就近就业；会同有关部门加强农民工服务保障工作，扩大以工代赈规模，稳住就业规模；完善强农惠农富农政策体系，加大对农民增收支持力度。 他表示，近日，国家统计局公布了最新数据，去年全国农村居民人均可支配收入实现稳步增长。下一步，农业农村部门将在继续拓宽农民增收致富渠道上下力气： 一是在提高农业综合效益上下功夫。家庭经营性收入仍然是农民收入的重要来源。农业农村部将积极发展绿色、特色农产品种养，加力抓好农产品加工、农业企业培育、农业品牌塑造等延链强链措施，实施好农业产业融合发展项目，推动农业增效带动农民增收。 二是在发展乡村新产业新业态上下功夫。做足“土特产”文章，大力发展休闲农业、农村电商、文化体验等新产业新业态，健全联农带农机制，把产业增值收益更多留在农村、留给农民。 三是在提升农民就业创业质量上下功夫。加大农村创业培训和支持力度，以创业促就业、促增收。针对当前农民工素质结构、职业技能不匹配问题，农业农村部会同有关部门推广用好订单、定向、定岗培训等管用模式，想方设法稳住农民务工就业岗位和收入。 四是在提高财产性收入上下功夫。积极探索农民闲置住房通过出租、入股、合作等方式盘活利用的有效实现形式。推进农村产权流转交易规范化建设，让农民更多分享改革红利。 陈邦勋表示，马上就是春节了，农业农村部门正配合有关部门，加大工作力度，保障年末岁尾农民工工资足额发放，让他们高高兴兴的过年。 （编辑：曹静 李海鹏） 【责任编辑：曹静】 COMPO WS678e23bda310be53ce3f2971 https://cn.chinadaily.com.cn/a/202501/20/WS678e23bda310be53ce3f2971.html 专题 人类命运共同体漫画插画大展 中国有约 全运会 2025世界互联网大会乌镇峰会 推荐阅读 新研究：十字花科蔬菜成分有助于抗癌治疗 东航全球最长单程航线首个航班回程 中拉“生鲜速运”再添新通道 马斯克抨击欧盟对社交媒体平台X巨额罚款 中国商业航天“在商言商”培育生态 护好“钱袋子”！多方警示虚拟货币交易炒作风险 “中国文化日—武术”专场展演在科伦坡成功举办 美乌结束3天会谈 主要讨论领土和安全保障问题 美加墨世界杯赛程公布：6月11日打响揭幕战 7月19日进行决赛 推荐阅读 新研究：十字花科蔬菜成分有助于抗癌治疗 东航全球最长单程航线首个航班回程 中拉“生鲜速运”再添新通道 马斯克抨击欧盟对社交媒体平台X巨额罚款 中国商业航天“在商言商”培育生态 护好“钱袋子”！多方警示虚拟货币交易炒作风险 “中国文化日—武术”专场展演在科伦坡成功举办 美乌结束3天会谈 主要讨论领土和安全保障问题 美加墨世界杯赛程公布：6月11日打响揭幕战 7月19日进行决赛 关于我们 | 联系我们 首页 时评 资讯 财经 生活 视频 专栏 漫画 独家 招聘 地方频道： 北京 天津 河北 山西 辽宁 吉林 黑龙江 上海 江苏 浙江 福建 江西 山东 河南 湖北 湖南 广东 广西 海南 重庆 四川 贵州 云南 西藏 陕西 新疆 深圳 友情链接： 人民网 新华网 中国网 国际在线 央视网 中国青年网 中国经济网 中国台湾网 中国西藏网 央广网 光明网 中国军网 中国新闻网 人民政协网 法治网 违法和不良信息举报 互联网新闻信息服务许可证10120170006 信息网络传播视听节目许可证0108263号 京公网安备11010502032503号 京网文[2011]0283-097号 京ICP备13028878号-6 中国日报网版权说明：凡注明来源为“中国日报网：XXX（署名）”，除与中国日报网签署内容授权协议的网站外，其他任何网站或单位未经允许禁止转载、使用，违者必究。如需使用，请与010-84883777联系；凡本网注明“来源：XXX（非中国日报网）”的作品，均转载自其它媒体，目的在于传播更多信息，其他媒体如需转载，请与稿件来源方联系，如产生任何问题与本网无关。 版权保护：本网登载的内容（包括文字、图片、多媒体资讯等）版权属中国日报网（中报国际文化传媒（北京）有限公司）独家所有使用。 未经中国日报网事先协议授权，禁止转载使用。给中国日报网提意见：rx@chinadaily.com.cn C财经客户端 扫码下载 Chinadaily-cn 中文网微信 首页 时评 资讯 C财经 生活 视频 专栏 地方 漫画 观天下 PC版 中文 English 中国日报版权所有 Content@chinadaily.com.cn × | 2026-01-13T09:29:34 |
https://th-th.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT2sNMHYzitoPSEfJsXkqvloqRUxIJIopp28rQfaItrhz2aN24BUXCxLByo7RN0rtEGnzmfDjJvzUhkboKt6Otzh5ksbYAnTsKOxnBOv_JCKZKKQjl3T5Sp4HoTs5V-POj4uS0aXV3zLAErg | Facebook Facebook อีเมลหรือโทรศัพท์ รหัสผ่าน ลืมบัญชีใช่หรือไม่ สร้างบัญชีใหม่ คุณถูกบล็อกชั่วคราว คุณถูกบล็อกชั่วคราว ดูเหมือนว่าคุณจะใช้คุณสมบัตินี้ในทางที่ผิดโดยการใช้เร็วเกินไป คุณถูกบล็อกจากการใช้โดยชั่วคราว Back ภาษาไทย 한국어 English (US) Tiếng Việt Bahasa Indonesia Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch สมัคร เข้าสู่ระบบ Messenger Facebook Lite วิดีโอ Meta Pay Meta Store Meta Quest Ray-Ban Meta Meta AI เนื้อหาเพิ่มเติมจาก Meta AI Instagram Threads ศูนย์ข้อมูลการลงคะแนนเสียง นโยบายความเป็นส่วนตัว ศูนย์ความเป็นส่วนตัว เกี่ยวกับ สร้างโฆษณา สร้างเพจ ผู้พัฒนา ร่วมงานกับ Facebook คุกกี้ ตัวเลือกโฆษณา เงื่อนไข ความช่วยเหลือ การอัพโหลดผู้ติดต่อและผู้ที่ไม่ได้ใช้บริการ การตั้งค่า บันทึกกิจกรรม Meta © 2026 | 2026-01-13T09:29:34 |
https://www.tumblr.com/support?language=es_ES | Centro de ayuda | Tumblr Inicia sesión Regístrate © Tumblr, Inc. Ayuda Acerca de Tumblr Aplicaciones Desarrolladores Temas Empleo Información legal Condiciones Copyright Privacidad English Deutsch Français Italiano 日本語 Türkçe Español Pусский Polski Português (PT) Português (BR) Nederlands 한국어 简体中文 繁體中文 (台灣) 繁體中文 (香港) Bahasa Indonesia हिंदी | 2026-01-13T09:29:34 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3AdropdownListBlock | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:34 |
https://www.atlassian.com/hu/software/jira/guides/projects/tutorials | Tutorials on Jira Project Spaces | Atlassian Close View this page in your language ? All languages Choose your language 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Get it free Features All Features Rovo in Jira Back Solutions Teams Use cases Company size Teams Marketing Engineering Design Operations IT Use cases Getting started Planning Campaign Management Agile Project Management Program Management Company size Enterprise Back Product guide Templates Templates All Templates Software Development Marketing Design Sales Operations Service Management HR Legal IT Operations Finance Jira Service Management templates Back Pricing More + Less - Get it free Back Get it free Getting started Introduction to Jira Jira for Teams 7 Steps to Get Started in Jira Projects Overview Tutorials Resources Boards Overview Tutorials Resources Work items/issues Overview Tutorials Resources Workflows Overview Tutorials Resources Integrations Overview Tutorials Resources Reports and Dashboards Overview Tutorials Resources Insights Overview Tutorials Resources Permissions Overview Tutorials Resources JQL Overview Tutorials Cheat sheet Resources Navigation Overview Tutorials Resources Automation Overview Tutorials Resources Timeline Overview Tutorials Resources Advanced planning Overview Tutorials Resources Jira Mobile Overview Tutorials Resources More about Jira Editions of Jira Hosting options Creating projects in Jira tutorials Create a new project in Jira Select ‘Create project’ from the ‘Projects’ in the top navigation. Please note that you won’t see this option if you don’t have permissions to create projects. Structure a project in Jira There is no one-size fits all approach to structuring a project in Jira. However, it may be helpful to recognize that Jira projects are not intended to be bespoke or unique to a single outcome. Rather, they capture ongoing efforts. With that in mind, here are a few approaches you may want to consider when thinking about how to structure your project in Jira: By team - Team-based projects are another common organizational model. This allows your work to mirror your social organization and is convenient in less cross-functional setups, as it allows for more straight forward project permission management. By business unit - You may want to organize around larger business units such as marketing, IT, etc. Types of work will likely fall into similar patterns, making setting up workflows - and issue types particularly - more convenient. By product - If you're a software development team looking to make heavy use of the Jira release and versioning system, you'll want to give strong consideration to organizing your projects by releasable product or groups of work that share a common release cycle. Even within these categories, you can get as granular or as broad as you want. For example, if you structure by product, you can continue to sub-categorize by specific features. Company Careers Events Blogs Investor Relations Atlassian Foundation Press kit Contact us products Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket See all products Resources Technical support Purchasing & licensing Atlassian Community Knowledge base Marketplace My account Create support ticket Learn Partners Training & certification Documentation Developer resources Enterprise services See all resources Copyright © 2025 Atlassian Privacy Policy Terms Impressum Choose language Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:34 |
https://issues.jenkins.io/secure/CreateSubTaskIssue!default.jspa?parentIssueId={0}&returnUrl=/secure/issues#main | Log into Atlassian - Jenkins Jira Log in Skip to main content Skip to sidebar Dashboards Projects Issues Give feedback to Atlassian Help Keyboard Shortcuts About Jira Jira Credits Log In 📢 Jenkins core issues have been migrated to GitHub , no new core issues can be created in Jira Atlassian Jira Project Management Software About Jira Report a problem Powered by a free Atlassian Jira open source license for The Linux Foundation. Try Jira - bug tracking software for your team. Atlassian | 2026-01-13T09:29:34 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3Ahetero-list | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:34 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3AenumSet | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:34 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.