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://service.weibo.com/share/share.php?appkey=2152474398&type=3&title=Burning questions for 2020&pic=http://img2.chinadaily.com.cn/images/201912/30/5e09673ba310cf3e97ae30ab.jpeg&url=https://www.chinadaily.com.cn/a/201912/29/WS5e080122a310cf3e35581466.html | 分享到微博-微博-随时随地分享身边的新鲜事儿 微博 加入微博一起分享新鲜事 登录 | 注册 140 请登录并选择要私信的好友 300 赞一下这个内容 公开 分享 获取分享按钮 正在发布微博，请稍候 | 2026-01-13T09:29:33 |
http://www.chinadaily.com.cn/world/211flash | World top pics - Chinadaily.com.cn Search HOME CHINA WORLD BUSINESS LIFESTYLE CULTURE TRAVEL VIDEO SPORTS OPINION REGIONAL NEWSPAPER MOBILE Global Edition ASIA 中文 双语 Français HOME CHINA WORLD BUSINESS LIFESTYLE CULTURE TRAVEL VIDEO SPORTS OPINION REGIONAL NEWSPAPER China Daily PDF China Daily E-paper MOBILE World Asia-Pacific Americas Europe Middle East Africa China-US China-Europe China-Japan China-Africa Home World / World top pics Home / World / World top pics Chinese EV makers steer global auto innovation 2026-01-13 10:18 US foreign policy shift threatens global order, stability: Experts 2026-01-13 09:54 Europe's farmers march against EU's deal with South American trade bloc 2026-01-13 09:50 Unrest under total control, claims Iran 2026-01-13 09:47 Hamas signals readiness to hand over Gaza governance 2026-01-13 09:26 EU commissioner reaffirms Greenland security, warning US takeover would end NATO 2026-01-13 09:16 Trade tensions threaten green goals, scholars warn 2026-01-13 09:11 2025 in review: Resilience amid headwinds 2026-01-13 09:04 CES 2026: Hong Kong tech companies showcase innovation with a focus on real-world applications 2026-01-13 07:09 Spotlight shines on AI, EVs at electronics trade show 2026-01-12 10:43 Japan's historical amnesia endangers regional peace 2026-01-12 09:47 Clean energy push 2026-01-12 09:38 ICE feels heat after Minneapolis shooting 2026-01-12 09:26 Myanmar begins 2nd phase of election 2026-01-12 08:14 Threat on Greenland irks European allies 2026-01-12 08:09 Japan's Takaichi may call early election 2026-01-12 07:35 Storm leaves 380,000 households without power in France -- AFP 2026-01-09 14:55 Trump signals he may let last US-Russia nuclear treaty expire 2026-01-09 13:30 Senate aims to curb Trump's power of war 2026-01-09 11:12 Washington's Greenland ambitions alarm Europe, threaten future of NATO 2026-01-09 10:20 1 2 3 4 5 6 7 8 9 10 Next >>| 1/952 Next Most Viewed in 24 Hours World in Focus Clean energy push Across Asia + Match online Himalayas warming 50 percent faster than global average: Study Special Coverage + 2025 A Date with China GMD SCO Summit Cities Tianjin Reporter's Journal + Shandong puts ancient philosophers into tourism draw A divergence of fates for two illustrious American newspapers Friends Afar + Blogger aims to bridge France, China links Ties That Bind + Vital pass to boost China-Pakistan trade Top BACK TO THE TOP English 中文 HOME CHINA WORLD BUSINESS LIFESTYLE CULTURE TRAVEL VIDEO SPORTS OPINION REGIONAL NEWSPAPER China Daily PDF China Daily E-paper MOBILE Copyright 1994 - . All rights reserved. The content (including but not limited to text, photo, multimedia information, etc) published in this site belongs to China Daily Information Co (CDIC). Without written authorization from CDIC, such content shall not be republished or used in any form. Note: Browsers with 1024*768 or higher resolution are suggested for this site. License for publishing multimedia online 0108263 Registration Number: 130349 About China Daily Advertise on Site Contact Us Job Offer Expat Employment FOLLOW US Copyright 1994 - . All rights reserved. The content (including but not limited to text, photo, multimedia information, etc) published in this site belongs to China Daily Information Co (CDIC). Without written authorization from CDIC, such content shall not be republished or used in any form. --> | 2026-01-13T09:29:33 |
https://reports.jenkins.io/jelly-taglib-ref.html#hudson.3Aactions | 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://issues.jenkins.io/issues/#main | Loading... 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 Export Tools Export - CSV (All fields) Export - CSV (Current fields) Choose a delimiter Comma (,) Semicolon (;) Vertical bar (|) Caret (^) Export Cancel [{"id":-1,"name":"My open issues","jql":"assignee = currentUser() AND resolution = Unresolved order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-2,"name":"Reported by me","jql":"reporter = currentUser() order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-4,"name":"All issues","jql":"order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-5,"name":"Open issues","jql":"resolution = Unresolved order by priority DESC,updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-9,"name":"Done issues","jql":"statusCategory = Done order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-3,"name":"Viewed recently","jql":"issuekey in issueHistory() order by lastViewed DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-6,"name":"Created recently","jql":"created >= -1w order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-7,"name":"Resolved recently","jql":"resolutiondate >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-8,"name":"Updated recently","jql":"updated >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false}] 0.3 0 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://service.weibo.com/share/share.php?appkey=2152474398&type=3&title=Burning questions for 2020&pic=http://img2.chinadaily.com.cn/images/201912/30/5e09673ba310cf3e97ae30ab.jpeg&url=https://www.chinadaily.com.cn/a/201912/29/WS5e080122a310cf3e35581466.html | 分享到微博-微博-随时随地分享身边的新鲜事儿 微博 加入微博一起分享新鲜事 登录 | 注册 140 请登录并选择要私信的好友 300 赞一下这个内容 公开 分享 获取分享按钮 正在发布微博，请稍候 | 2026-01-13T09:29:33 |
https://docs.aws.amazon.com/zh_cn/cost-management/latest/userguide/ce-api.html | 使用 AWS Cost Explorer API - AWS 成本管理 使用 AWS Cost Explorer API - AWS 成本管理 文档 AWS Billing and Cost Management 用户指南 服务终端节点 授予 IAM 权限以使用 AWS Cost Explorer API 本文属于机器翻译版本。若本译文内容与英语原文存在差异，则一律以英文原文为准。 使用 AWS Cost Explorer API Cost Explorer 允许您通过编程方式查询费用和使用量数据。您可以查询每月总费用或每日总使用量等汇总数据。还可以查询更精细数据，例如您生产环境中的 DynamoDB 数据库表的每日写入操作数量。 如果 AWS 为您使用的编程语言提供了开发工具包，建议您使用该开发工具包。与使用 AWS Cost Explorer API 相比，所有 AWS 开发工具包都会大大简化签名请求的过程，从而为您节省大量时间。此外，开发工具包还可轻松与您的开发环境集成，并可让您轻松访问相关命令。 有关可用软件开发工具包的更多信息，请参阅 适用于 Amazon Web Services 的工具 。有关 AWS Cost Explorer API 的更多信息，请参阅 AWS 账单与成本管理 API 参考 。 服务终端节点 Cost Explorer API 提供以下终端节点： https://ce.us-east-1.amazonaws.com 授予 IAM 权限以使用 AWS Cost Explorer API 用户必须获得显式权限才能查询 AWS Cost Explorer API。有关向用户授予所需权限的策略，请参阅 查看成本和使用情况 。 Javascript 在您的浏览器中被禁用或不可用。 要使用 Amazon Web Services 文档，必须启用 Javascript。请参阅浏览器的帮助页面以了解相关说明。 文档惯例 使用 IAM 控制访问 AWS Cost Explorer API 的最佳实践 此页面对您有帮助吗？- 是 感谢您对我们工作的肯定！ 如果不耽误您的时间，请告诉我们做得好的地方，让我们做得更好。 此页面对您有帮助吗？- 否 感谢您告诉我们本页内容还需要完善。很抱歉让您失望了。 如果不耽误您的时间，请告诉我们如何改进文档。 | 2026-01-13T09:29:33 |
https://www.ecns.cn/business/ | Business --> 中文 Home News Ecns Wire Business Travel Photo Video Voices RIGHT BG LINE Business --> China to adjust or cancel export tax rebates for photovoltaic and battery products Jan 10, 2026 China announced on Friday that it will change export tax rebates for a range of products, including photovoltaic and battery products.Meanwhile, the export tax rebate rate for the value added tax of battery products will be reduced from 9 percent to 6 percent starting from April 1, 2026, and will be eliminated starting from Jan 1, 2027, according to the announcement. China investigates Meta's acquisition of agentic AI startup Manus Jan 9, 2026 China's Ministry of Commerce (MoC) is officially looking into Meta's deal to buy the AI platform Manus, a so-called "general-purpose AI agent" capable of autonomously handling complex digital tasks just like a human. 450-ton freight train brings Gansu seeds to Europe Jan 7, 2026 A new freight route linking northwestern China with Europe began operations with a train carrying hundreds of tons of agricultural seeds departing from Gansu province, underscoring the region's growing role in global farm supply chains. China curbs dual-use item exports to Japan Jan 7, 2026 China announced on Tuesday an immediate ban on exporting dual-use items to Japan, in response to Japanese Prime Minister Sanae Takaichi's erroneous remarks hinting at the possibility of military intervention in the Taiwan Strait. China in elite global manufacturing club Dec 31, 2025 The growth in China's manufacturing sector in 2024 propelled it to the elite club of the world's leading manufacturing powers, surpassing Japan for the first time, according to a report released on Tuesday. China firmly opposes U.S. additional tariff on semiconductors from China Dec 26, 2025 The measure will come into force with an initial tariff rate of zero percent and increase within 18 months to a level to be announced no fewer than 30 days before June 23, 2027. China has noted the relevant situation and lodged stern representations with the U.S. side through the China-U.S. Airbus delivers 800th A320 assembled in China Dec 17, 2025 Airbus on Wednesday delivered its 800th A320 Family aircraft assembled in China, underscoring the European planemaker's long-term manufacturing presence in the country. Departure tax refund applications surge 285% as inbound tourism rebounds Dec 8, 2025 Tourists claim an instant tax refund in Shanghai.Sales of tax-refundable goods and the total value of tax refunds both increased 98.8 percent year-on-year over the same period. Trade-in program likely to continue next year Nov 20, 2025 China is likely to extend the consumer goods trade-in program into 2026, as analysts said there is still substantial, unmet demand among Chinese households to upgrade home appliances and digital devices, as well as ample fiscal headroom to underpin the consumption campaign. Road map sets out 2040 transport vision Nov 10, 2025 China will advance electrification to reduce automotive carbon emissions and improve energy efficiency, with new energy vehicles set to become the market mainstay. Unlocking Xinjiang Charms | From the Tianshan foothills to global tables — a small crop with a big flavor Nov 6, 2025 In Yuepuhu County, Xinjiang, the tiny seed of cumin is moving beyond the Tianshan Mountains, marching into global markets from local fields. Powered by digital production lines and international trading platforms, this aroma from China’s northwest is becoming a taste shared by the world. China, Singapore reaffirm growing economic ties Nov 4, 2025 The economic partnership between Singapore and China is poised for robust growth, setting new benchmarks for regional cooperation as both nations commemorate significant anniversaries, industry experts said. State Grid Shanghai launches smart power protection 8.0 to secure 8th CIIE Nov 3, 2025 State Grid Shanghai launches smart power protection 8.0 to secure 8th CIIE Oct 31, 2025 State Grid Shanghai Municipal Electric Power Company held a mobilization rally on October 30, signaling the start of full operational readiness for securing electricity supply during the 8th China International Import Expo (CIIE). Over 200 personnel from 20 support units pledged to ensure secure and reliable electricity throughout the international event. China to improve financial services further: official Oct 28, 2025 BEIJING - China will continue improving financial services in the fields of financing, investment and industrial development, as well as in the domestic and international markets, according to Li Yunze, head of the National Financial Regulatory Administration (NFRA), on Monday. Li calls for enhanced regional growth, peace Oct 28, 2025 Premier Li Qiang has warned of the risks arising from mounting unilateralism and protectionism, and called for joint efforts to foster an environment conducive to regional development and safeguard peace and stability in East Asia. Beijing set to host 2025 Financial Street Forum from Monday Oct 27, 2025 The 2025 Financial Street Forum will be held on Beijing's Financial Street in the city's Xicheng District from October 27 to 30 under the theme of "Global Financial Development in an Era of Innovation, Transformation and Restructuring." More than 400 distinguished guests from over 30 countries and regions are expected to attend the event. Jiangsu's first regionally decentralized grid-side energy storage project successfully connected to grid Oct 22, 2025 On September 30, the 49.8MW/99.6MWh grid-side energy storage power station of Suqian Zhonghe East Line New Energy in Jiangsu was officially connected to the grid. This marks the official operation of Jiangsu's first grid-side independent energy storage project constructed in a regionally decentralized manner, providing a new model for the development of grid-side energy storage. China's digital finance push reshapes capital markets Oct 19, 2025 China's accelerating drive of finance digitalization is shifting from technology-driven innovation to deepening institutional reforms, with digital assets expected to redefine the logic of capital market operations, said experts participating at a high-level forum in Beijing on Saturday. Apple CEO commits to increase investment and cooperation in China Oct 15, 2025 Apple CEO Tim Cook said on Wednesday that the U.S. tech company will continue to increase its investment in China and further expand its cooperation with the country, aiming for mutual benefits and shared success. Ghana promotes key investment opportunities for Chinese investors Oct 15, 2025 "Every inch of Ghana is ready." The words of Simon Madjie, chief executive officer of the Ghana Investment Promotion Center, resonated across the conference hall in Beijing, capturing Ghana's eagerness to welcome Chinese investors and the surging vitality of China-Ghana economic ties. China urges sincerity from U.S. in trade talks Oct 15, 2025 China on Tuesday urged the United States to "correct its wrong practices and show sincerity" to preserve the hard-won results of previous trade talks and work with China in the same direction, a day after working-level talks were held between Beijing and Washington. China regulator says Qualcomm investigation is routine Oct 13, 2025 China's top market regulator has described its investigation into Qualcomm's unapproved acquisition of Autotalks as a routine law enforcement activity conducted under the country's anti-monopoly law. China defends export controls on rare earths Oct 13, 2025 China's latest step to tighten export controls on rare earths and related items will bolster global supply-chain security and ensure trade compliance, rather than curb exports, government officials and analysts said on Sunday. China becomes global hub for two-way investment Oct 13, 2025 As global supply chains undergo transformation and investment patterns shift, China has taken on a dual role in the world economy — as both a magnet for foreign enterprises and an increasingly influential outbound investor, said experts and executives. Rare earth controls boost stability, security Oct 13, 2025 China's latest step to tighten export controls on rare earths and related items will bolster global supply-chain security and ensure trade compliance, rather than curb exports, said a government official and analysts on Sunday. New policy targets EV exporters Oct 7, 2025 China's move to bring exports of pure electric passenger vehicles under a licensing regulation is expected to enhance overseas user experience and protect brand reputation by ensuring stronger quality control, better after-sales services and a more orderly export environment, industry experts said. China's pledge sets green stage for ASEAN Oct 7, 2025 China's commitment to further reducing emissions and boosting renewable energy production is expected to encourage Southeast Asian economies to accelerate their low-carbon transition, analysts said. New reception hall aims to transform Guangzhou into international trade hub Oct 5, 2025 The recent establishment of the "Guangzhou International Reception Hall" is expected to provide crucial support for the Guangdong provincial capital city to build itself into an international trade hub. Chinese brands burst onto global stage Oct 3, 2025 The global frenzy for the Labubu doll has shone a light on how Chinese brands are crossing borders and growing in popularity worldwide. --> First Previous 1 2 3 4 5 Next Last Most popular in 24h More Top news Greenland says U.S. takeover unacceptable 'under any circumstances' China files over 200,000 satellite frequency, orbit applications with ITU John Ross: China's 14th Five-Year Plan has enabled a qualitative breakthrough and reshaped its relationship with the world economy China's Tianma-1000 cargo drone able to deliver 1 metric ton of supplies to plateau China bans medical institutions from offering funeral services in crackdown on sector abuses More Video The Source Keeper Season 3 | Episode 1: The Whispers of Mountains and Rivers Comicomment: Wings clipped, Latin America left to suffer 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://www.ecns.cn/privacy-policy.shtml | Privacy Policy - Headlines, stories and photos from ecns.cn If you can read Chinese, please visit our Chinese website www.chinanews.com Share the news or just email us your thoughts. Save your time reading the web? Click the RSS and we will help you. more HOME NEWS FEATURE BUSINESS MILITARY EXPERIENCE VIDEO PHOTO Privacy Policy ����This privacy policy applies to information we collect from all sources in connection with the Ecns.cn Website, our mobile sites, and applications that link to this Privacy Policy. ���� The Information We Collect ����We may seek to collect from you various forms of personal information, including name, address, email address, telephone number, and interests in and use of products, programs and services. ����We, our third-party service providers, advertisers and partners may collect various types of non-personally identifiable information. The information may include: Internet protocol address, type of operating system you are using, type of mobile device used to view this site, location information, and the content and advertisements you have accessed. ����When you engage with our content through social networking sites, plug-ins or applications, you may allow us to have access to certain information from your social media profile and non-personally identifiable information from your interaction with our content. ���� How We Use the Information ����We use the information that we collect to provide and manage our services, to improve the design and content of our sites, to deliver relevant marketing messages and advertisements, and to enable us to personalize your Internet experience. ���� Information Sharing and Disclosure ����We are committed to protecting your information in a manner that is consistent with this Privacy Policy. ����We use the information only for purposes of carrying out the services. However, we may share your personal information when permitted or required by law. Non-personally identifiable information may be aggregated for data statistical purposes, such as number of estimated total users or software downloads. ���� Contact us ����For questions or concerns regarding our Privacy Policy, you may write to ����en@chinanews.com.cn. ���� Updates and Effective Dates ����We may revise our Privacy Policy periodically. Please look at the effective date at the bottom of this Privacy Policy to see when it was last revised. �� Links ���� About Us ���� Jobs ���� Contact Us ���� Privacy Policy Copyright ©1999-2011 Chinanews.com. All rights reserved. Reproduction in whole or in part without permission is prohibited. | 2026-01-13T09:29:33 |
https://pix.webm.ink/site/kb/sharing-media#collapse4 | Pixelfed Help Center minkpix Help Center — Sharing Photos & Videos Getting Started Sharing Media Profile Hashtags Discover Timelines Instagram Import Community Guidelines Safety Tips Sharing Photos & Videos How do I create a post? To create a post using a desktop web browser: Go to https://pix.webm.ink . Click on the link at the top of the page. Upload your photo(s) or video(s), add an optional caption and set other options. Click on the Create Post button. To create a post using a mobile web browser: Go to https://pix.webm.ink . Click on the button at the bottom of the page. Upload your photo(s) or video(s), add an optional caption and set other options. Click on the Create Post button. How do I share a post with multiple photos or videos? During the compose process, you can select multiple files at a single time, or add each photo/video individually. How do I add a caption before sharing my photos or videos on Pixelfed? During the compose process, you will see the Caption input. Captions are optional and limited to 500 characters. How do I add a filter to my photos? This is an experimental feature, filters are not federated yet! To add a filter to media during the compose post process: Click the Options button if media preview is not displayed. Select a filter from the Select Filter dropdown. How do I add a description to each photo or video for the visually impaired? This is an experimental feature! You need to use the experimental compose UI found here . Add media by clicking the Add Photo/Video button. Set a image description by clicking the Media Description button. Image descriptions are federated to instances where supported. What types of photos or videos can I upload? You can upload the following media types: image/jpeg image/png image/gif video/mp4 image/webp How can I disable comments/replies on my post? To enable or disable comments/replies using a desktop or mobile browser: Open the menu, click the button Click on Enable Comments or Disable Comments How many people can I tag or mention in my comments or posts? You can tag or mention up to 5 profiles per comment or post. What does archive mean? You can archive your posts which prevents anyone from interacting or viewing it. Archived posts cannot be deleted or otherwise interacted with. You may not recieve interactions (comments, likes, shares) from other servers while a post is archived. How can I archive my posts? To archive your posts: Navigate to the post Open the menu, click the or button Click on Archive How do I unarchive my posts? To unarchive your posts: Navigate to your profile Click on the ARCHIVES tab Scroll to the post you want to unarchive Open the menu, click the or button Click on Unarchive About Help Terms Privacy Language © 2026 pix.webm.ink · Powered by Pixelfed · v0.12.6 | 2026-01-13T09:29:33 |
http://www.chinadaily.com.cn/a/202601/12/WS6964a542a310d6866eb333fa.html | China-Austria winter carnival kicks off in Shanxi 中文 Search Nav Search X HOME ABOUT SHANXI + Overview Regions Videos MEDIA CENTER + News Specials Reports in PDF DISCOVER SHANXI + Culture Attractions Dining Hotels Transportation Shopping Travel Agencies DOING BUSINESS + Why Shanxi Guide Policies Industries Industrial Parks Companies LIVING + Visa Education Healthcare Marriage Adoption Useful Info Home > News 1153887 2026-01-09 13:07:07.0 Zhu Xingxin and Zhou Huiying China-Austria winter carnival kicks off in Shanxi Shanxi,winter carnival 48 14965 News 2@shanxi /enpproperty--> China-Austria winter carnival kicks off in Shanxi By Zhu Xingxin and Zhou Huiying (chinadaily.com.cn) Updated: 2026-01-09 Print Mail Large Medium Small The 2nd China-Austria Ice and Snow Culture Carnival kicks off on Tuesday in Lingchuan county, Jincheng, Shanxi province. [Photo provided to chinadaily.com.cn] The 2nd China-Austria Ice and Snow Culture Carnival kicked off on Tuesday in Lingchuan county, Jincheng, Shanxi province, tapping into the growing enthusiasm for winter sports. Julian Gale, a senior official from Klagenfurt, Austria, praised the event as a spectacular experience and emphasized its role in strengthening exchanges between different cultures. Gale also highlighted the consistently positive impact of bilateral cooperation in sports, culture, and the economy, affirming that Klagenfurt will continue to deepen collaboration with Shanxi. Located at the southern end of the Taihang Mountains, Lingchuan boasts a unique climate and ample ecological resources, making it an ideal winter destination for ice-snow recreation and health and wellness. Cooperation between Lingchuan and the Austrian province of Carinthia has deepened in recent year. In 2024, Lingchuan established sister-city ties with Feistritz an der Gail and co-hosted the first Ice and Snow Culture Carnival in 2025. The 2nd China-Austria Ice and Snow Culture Carnival kicks off on Tuesday in Lingchuan county, Jincheng, Shanxi province. [Photo provided to chinadaily.com.cn] Friedrich Alois Lienz, a former Austrian national team skier, visited China for the first time and taught skiing techniques to local primary school students during the event. He remarked that such activities greatly enhance friendly exchanges between China and Austria. The two-month carnival features six winter tourism routes tailored to Lingchuan's seasonal highlights, the distribution of local scenic spots, and market demand for tourism products. "The ice-and-snow economy represents a new growth driver for Lingchuan's high-quality development, and cooperation with Carinthia serves as a vital link in our opening-up strategy," said Wang Li, head of the county. She added that the county will leverage the carnival as a starting point to amplify its advantages in winter resources and promote the internationalization, branding, and integrated development of its ice-and-snow economy. The county is planning to launch a voucher program totaling 5 million yuan ($716,000) to boost winter tourism. It will gather local delicacies and organize public skiing competitions, primary and secondary school skiing contests, and winter camps, all designed to fuel winter cultural and tourism consumption. Sun Shuyue contributed to this story. Specials Shanxi unveils 14th Five-Year Plan highlights 'A Date with China' International Media Tour 2025 TOP ABOUT SHANXI Overview Regions Videos MEDIA CENTER News Specials Reports in PDF DISCOVER SHANXI Culture Attractions Dining Hotels Transportation Shopping Travel Agencies DOING BUSINESS Why Shanxi Guide Policies Industries Industrial Parks Companies LIVING Visa Education Healthcare Marriage Adoption Useful Info LINKS > Official Website of People’s Government of Shanxi Province Taiyuan Datong Yangquan Ancient City of Pingyao Beijing Shanghai Copyright © The Publicity Department of the CPC Shanxi Provincial Committee. All Rights Reserved. 京ICP备13028878号-6 | 2026-01-13T09:29:33 |
http://groovy-lang.org/syntax.html#_slashy_string | 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://pix.webm.ink/site/kb/getting-started#collapse5 | Pixelfed Help Center minkpix Help Center — Getting Started Getting Started Sharing Media Profile Hashtags Discover Timelines Instagram Import Community Guidelines Safety Tips Getting Started Welcome to Pixelfed! How do I create a Pixelfed account? To create an account using a web browser: Go to https://pix.webm.ink . Click on the register link at the top of the page. Enter your name, email address, username and password. How to I update profile info like name, bio, email? You can update your account by visiting the account settings page. What can I do if a username I want is taken but seems inactive? If your desired username is taken you can add underscores, dashes, or numbers to make it unique. Why can't I change my username? Pixelfed is a federated application, changing your username is not supported in every federated software so we cannot allow username changes. Your best option is to create a new account with your desired username. I received an email that I created an account, but I never signed up for one. Someone may have registered your email by mistake. If you would like your email to be removed from the account please contact an admin of this instance. I can't create a new account because an account with this email already exists. You might have registered before, or someone may have used your email by mistake. Please contact an admin of this instance. About Help Terms Privacy Language © 2026 pix.webm.ink · Powered by Pixelfed · v0.12.6 | 2026-01-13T09:29:33 |
https://www.chinadaily.com.cn/a/202511/12/WS6913f7faa310fc20369a4a46.html | Charming Beijing TV Series promotion event in quotes (I) - Chinadaily.com.cn Search HOME CHINA WORLD BUSINESS LIFESTYLE CULTURE TRAVEL WATCHTHIS SPORTS OPINION REGIONAL FORUM NEWSPAPER MOBILE Home World Latest News Home / World / Latest News Charming Beijing TV Series promotion event in quotes (I) chinadaily.com.cn | Updated: 2025-11-12 10:58 Share Share - WeChat --> CLOSE "Charming Beijing, Shared with the World" Overseas Promotion and Sharing Event of the Charming Beijing TV Series has been successfully held in Beijing. --> --> Photo Coming up: A sour journey into Shanxi's liquid heritage What? Clothes made from fish skin? Calls and conservation China'a micro-dramas a screen saver for film world AI boosts Singles Day sales, shopping experience China's digital leap empowering the world --> --> Top BACK TO THE TOP English 中文 HOME CHINA WORLD BUSINESS LIFESTYLE CULTURE TRAVEL VIDEO SPORTS OPINION REGIONAL NEWSPAPER China Daily PDF China Daily E-paper MOBILE Copyright 1995 - . All rights reserved. The content (including but not limited to text, photo, multimedia information, etc) published in this site belongs to China Daily Information Co (CDIC). Without written authorization from CDIC, such content shall not be republished or used in any form. Note: Browsers with 1024*768 or higher resolution are suggested for this site. License for publishing multimedia online 0108263 Registration Number: 130349 About China Daily Advertise on Site Contact Us Job Offer Expat Employment FOLLOW US Copyright 1995 - . All rights reserved. The content (including but not limited to text, photo, multimedia information, etc) published in this site belongs to China Daily Information Co (CDIC). Without written authorization from CDIC, such content shall not be republished or used in any form. --> | 2026-01-13T09:29:33 |
https://www.ecns.cn/video/2026-01-06/detail-iheyrzrv3835398.shtml | Insights丨China’s economy in UN official’s eyes: Resilience, exports, and high-tech transition --> 中文 Home News Ecns Wire Business Travel Photo Video Voices RIGHT BG LINE Text: A A A Print Video Insights丨China’s economy in UN official’s eyes: Resilience, exports, and high-tech transition 2026-01-06 13:58:39 Ecns.cn Editor : Meng Xiangjun ECNS App Download Benjamin Rae, senior economist at the UN Resident Coordinator’s Office in China, noted during an exclusive interview with China News Network that despite various challenges in 2025, China’s economy grew 5.2% in the first three quarters, and exports increased dramatically, reflecting diversification in China’s export markets. He highlighted that China is transitioning toward a consumption-oriented economy and high-tech sectors, requiring adjustments to growth models that have worked over the past 15 to 20 years as it moves from a developing to an emerging, mature market economy as China initiates its 15th Five-Year Plan in 2026. (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 Protests erupt across U.S. against military strikes on Venezuela Nvidia CEO Huang says next generation of chips in full production Chinese troops step up combat-focused drills Maduro pleads not guilty in N.Y. court UN Security Council holds emergency meeting on Venezuela More Video Insights丨Portuguese economist sees stability and opportunity in China’s long-term planning (W.E. Talk) Experts on 2026: China's 15th Five-Year Plan significant for the World 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://www.chinadaily.com.cn/a/202512/12/WS693bdb72a310d6866eb2e5f2.html | Metasequoia avenue in Changsha showcases nature's splendor - Chinadaily.com.cn Search HOME CHINA WORLD BUSINESS LIFESTYLE CULTURE TRAVEL WATCHTHIS SPORTS OPINION REGIONAL FORUM NEWSPAPER MOBILE Home China China Photos Home / China / China Photos Metasequoia avenue in Changsha showcases nature's splendor By LI MUYUN and ZHU YOUFANG in Changsha | chinadaily.com.cn | Updated: 2025-12-12 17:07 Share Share - WeChat --> CLOSE A five-kilometer stretch of metasequoia trees along the Sancha River in Jiangbei town, Changsha county, Hunan province, is widely regarded as "the most beautiful metasequoia avenue" in Changsha. [Photo by Wu Yunxuan/for chinadaily.com.cn] A five-kilometer stretch of metasequoia trees lines the Sancha River in Jiangbei town, Changsha county, Hunan province. Acclaimed by many as "the most beautiful metasequoia avenue" in Changsha, it has recently been drawing crowds of visitors and photographers. These trees are now about half a century old. According to the local government, the best viewing period will last until the end of December. --> 1 2 3 4 5 6 7 8 Next >>| --> 1/8 Next Photo Beijing welcomes its first snowfall this winter IMF chief: China should step up consumption-led growth Yanshiping, Xizang's highest railway station, begins service Salt of the earth Moment of truth 'Golden name cards' help China, EU forge market bonds --> --> Top BACK TO THE TOP English 中文 HOME CHINA WORLD BUSINESS LIFESTYLE CULTURE TRAVEL VIDEO SPORTS OPINION REGIONAL NEWSPAPER China Daily PDF China Daily E-paper MOBILE Copyright 1994 - . All rights reserved. The content (including but not limited to text, photo, multimedia information, etc) published in this site belongs to China Daily Information Co (CDIC). Without written authorization from CDIC, such content shall not be republished or used in any form. Note: Browsers with 1024*768 or higher resolution are suggested for this site. License for publishing multimedia online 0108263 Registration Number: 130349 About China Daily Advertise on Site Contact Us Job Offer Expat Employment FOLLOW US Copyright 1994 - . All rights reserved. The content (including but not limited to text, photo, multimedia information, etc) published in this site belongs to China Daily Information Co (CDIC). Without written authorization from CDIC, such content shall not be republished or used in any form. --> | 2026-01-13T09:29:33 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3Arepeatable | 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://pix.webm.ink/site/kb/getting-started#collapse1 | Pixelfed Help Center minkpix Help Center — Getting Started Getting Started Sharing Media Profile Hashtags Discover Timelines Instagram Import Community Guidelines Safety Tips Getting Started Welcome to Pixelfed! How do I create a Pixelfed account? To create an account using a web browser: Go to https://pix.webm.ink . Click on the register link at the top of the page. Enter your name, email address, username and password. How to I update profile info like name, bio, email? You can update your account by visiting the account settings page. What can I do if a username I want is taken but seems inactive? If your desired username is taken you can add underscores, dashes, or numbers to make it unique. Why can't I change my username? Pixelfed is a federated application, changing your username is not supported in every federated software so we cannot allow username changes. Your best option is to create a new account with your desired username. I received an email that I created an account, but I never signed up for one. Someone may have registered your email by mistake. If you would like your email to be removed from the account please contact an admin of this instance. I can't create a new account because an account with this email already exists. You might have registered before, or someone may have used your email by mistake. Please contact an admin of this instance. About Help Terms Privacy Language © 2026 pix.webm.ink · Powered by Pixelfed · v0.12.6 | 2026-01-13T09:29:33 |
https://www.chinadaily.com.cn/a/202507/08/WS686cf3dfa31000e9a573ad80.html | SCO members impressed by Tianjin's smart eco-city - World - Chinadaily.com.cn Search HOME CHINA WORLD BUSINESS LIFESTYLE CULTURE TRAVEL VIDEO SPORTS OPINION REGIONAL FORUM NEWSPAPER MOBILE Global Edition ASIA 中文 双语 Français HOME CHINA WORLD BUSINESS LIFESTYLE CULTURE TRAVEL VIDEO SPORTS OPINION REGIONAL FORUM NEWSPAPER China Daily PDF China Daily E-paper MOBILE World Asia-Pacific Americas Europe Middle East Africa China-US China-Europe China-Japan China-Africa Home World / Amazing Tianjin Home / World / Amazing Tianjin SCO members impressed by Tianjin's smart eco-city By Yan Dongjie in Tianjin | chinadaily.com.cn | Updated: 2025-07-08 18:33 Share Share - WeChat --> CLOSE A panoramic view of China-Singapore Tianjin Eco-City in Tianjin's Binhai New Area. [Photo provided to CHINA DAILY] A representative from Kyrgyzstan expressed willingness to cooperate with China in smart city construction when visiting the Sino-Singapore Tianjin Eco-City on Monday. "I have rarely seen an eco-city with such a high level of intelligence, especially the smart waste sorting technology, which is very much worth learning," said Aziz Kanatbek, director of the Institute of Geostrategic Studies of Kyrgyzstan. Representatives from five Shanghai Cooperation Organization member countries gathered in Tianjin for the Global Mayors Dialogue · SCO Summit Cities, which opened on Tuesday. The Sino-Singapore Tianjin Eco-City is a joint project between China and Singapore. Initiated in 2008, it is the world's first intergovernmental cooperative eco-city. In this city, data from smart communities, smart education, smart healthcare, and other scenarios are monitored in real-time by the City Brain. "The entire city is like being integrated into a supercomputer," said Zhao Kejie, a staff member at the City Brain. "The City Brain system can process over 100,000 data points per second and promptly push alerts for situations such as heavy rain warnings or elevator malfunctions," she explained. Kanatbek was also impressed by the experience of riding an autonomous bus. In the eco-city, people can book rides on self-driving buses, which navigate safely using lidar and omnidirectional cameras. "Even in rainy or foggy weather, the buses can accurately detect pedestrians, vehicles, and even stray cats that suddenly appear," said Wang Hongxi, the head of operations and scheduling at Tianjin Eco-city Green Transportation. "I hope and believe that Kyrgyzstan will cooperate more deeply with China in the construction of eco-cities," Kanatbek said. Bao Yan contributed to this story. yandongjie@chinadaily.com.cn --> --> --> Photos South Korea responds to renewed US tariff threat Thailand sets sights on building kingdom into wellness destination Japan says US 25% tariff is 'truly regrettable' China urges international community to boost support for Afghanistan China's visa push opens ASEAN skies At least 10 killed, 28 injured as fresh protests erupts in Kenya Most Viewed in 24 Hours World in Focus Shutting the doors Across Asia + Student deaths point at increasing campus violence in Indonesia Questions raised over South Korea's 4.5-day workweek proposal Special Coverage + Live: Middle East truce stands amid claims of victory My China Album --> Friends Afar + Ballet maestro's fond China memories Ties That Bind + Vital pass to boost China-Pakistan trade Top BACK TO THE TOP English 中文 HOME CHINA WORLD BUSINESS LIFESTYLE CULTURE TRAVEL VIDEO SPORTS OPINION REGIONAL FORUM NEWSPAPER China Daily PDF China Daily E-paper MOBILE Copyright 1995 - . All rights reserved. The content (including but not limited to text, photo, multimedia information, etc) published in this site belongs to China Daily Information Co (CDIC). Without written authorization from CDIC, such content shall not be republished or used in any form. Note: Browsers with 1024*768 or higher resolution are suggested for this site. License for publishing multimedia online 0108263 Registration Number: 130349 About China Daily Advertise on Site Contact Us Job Offer Expat Employment FOLLOW US Copyright 1995 - . All rights reserved. The content (including but not limited to text, photo, multimedia information, etc) published in this site belongs to China Daily Information Co (CDIC). Without written authorization from CDIC, such content shall not be republished or used in any form. --> | 2026-01-13T09:29:33 |
https://www.chinadaily.com.cn/world/special_coverage/68f1f858a310f735438b59d7 | Latest News - Chinadaily.com.cn Search HOME CHINA WORLD BUSINESS LIFESTYLE CULTURE TRAVEL VIDEO SPORTS OPINION REGIONAL NEWSPAPER MOBILE Global Edition ASIA 中文 双语 Français HOME CHINA WORLD BUSINESS LIFESTYLE CULTURE TRAVEL VIDEO SPORTS OPINION REGIONAL NEWSPAPER China Daily PDF China Daily E-paper MOBILE World Asia-Pacific Americas Europe Middle East Africa China-US China-Europe China-Japan China-Africa Home World / Latest News Home / World / Latest News Charming Beijing TV Series promotion event in quotes (IV) 2025-11-15 09:00 Charming Beijing TV Series promotion event in quotes (III) 2025-11-14 09:00 Charming Beijing TV Series promotion event in quotes (II) 2025-11-13 09:00 Charming Beijing TV Series promotion event in quotes (I) 2025-11-12 10:58 'Charming Beijing' TV Series overseas promotion event held in Oct 2025-10-31 17:47 Foreign media spotlight Beijing's innovation at Zhongguancun Life Science Park 2025-10-28 09:57 'Charming Beijing, Shared with the World' Overseas Promotion and Sharing Event of the Charming Beijing TV Series successfully held at Beijing Longfu Cultural Center 2025-10-24 21:11 Opening soon: Charming Beijing, Shared with the World 2025-10-24 14:08 International film crews explore Beijing's Shougang Park 2025-10-23 20:51 One day to go: Charming Beijing, Shared with the World 2025-10-23 09:06 Film crews explore medical miracles in Beijing 2025-10-22 16:53 Two days to go: Charming Beijing, Shared with the World 2025-10-22 09:18 International film crews explore Beijing's AI innovation 2025-10-21 16:13 Three days to go: Charming Beijing, Shared with the World 2025-10-21 09:58 Foreign TV crews tour Beijing's Temple of Heaven 2025-10-20 18:09 Four days to go: Charming Beijing, Shared with the World 2025-10-20 09:34 Five days to go: Charming Beijing, Shared with the World 2025-10-19 09:54 Six days to go: Charming Beijing, Shared with the World 2025-10-18 17:03 1 1/1 Most Viewed in 24 Hours World in Focus Clean energy push Across Asia + Match online Himalayas warming 50 percent faster than global average: Study Special Coverage + 2025 A Date with China GMD SCO Summit Cities Tianjin Reporter's Journal + Shandong puts ancient philosophers into tourism draw A divergence of fates for two illustrious American newspapers Friends Afar + Blogger aims to bridge France, China links Ties That Bind + Vital pass to boost China-Pakistan trade Top BACK TO THE TOP English 中文 HOME CHINA WORLD BUSINESS LIFESTYLE CULTURE TRAVEL VIDEO SPORTS OPINION REGIONAL NEWSPAPER China Daily PDF China Daily E-paper MOBILE Copyright 1994 - . All rights reserved. The content (including but not limited to text, photo, multimedia information, etc) published in this site belongs to China Daily Information Co (CDIC). Without written authorization from CDIC, such content shall not be republished or used in any form. Note: Browsers with 1024*768 or higher resolution are suggested for this site. License for publishing multimedia online 0108263 Registration Number: 130349 About China Daily Advertise on Site Contact Us Job Offer Expat Employment FOLLOW US Copyright 1994 - . All rights reserved. The content (including but not limited to text, photo, multimedia information, etc) published in this site belongs to China Daily Information Co (CDIC). Without written authorization from CDIC, such content shall not be republished or used in any form. --> | 2026-01-13T09:29:33 |
https://wiki.documentfoundation.org/WikiAction/history/Design | Design: Revision history - 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 Design: Revision history Help 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 Atom RSS Special pages Page information Appearance move to sidebar hide View logs for this page ( view abuse log ) Filter revisions Expand Collapse To date: Tag filter: Blanking blanking categories removed coi-spam large unwikified new article Manual revert New redirect possible link spam possible vandalism Redirect target changed Removed redirect Replaced Reverted Rollback Section blanking Server-side upload translate-translation-pages (hidden tag) Undo very short new article wikieditor (hidden tag) Invert selection Show revisions Diff selection: Mark the radio buttons of the revisions to compare and hit enter or the button at the bottom. Legend: (cur) = difference with latest revision, (prev) = difference with preceding revision, m = minor edit. ( newest | oldest ) View ( newer 50 | older 50 ) ( 20 | 50 | 100 | 250 | 500 ) 25 December 2025 cur prev 08:54 08:54, 25 December 2025 Beluga talk contribs 7,106 bytes −73 Beautify BZ URLs a bit just to be able to update the page after zh-hant -> zh-tw move 24 April 2024 cur prev 08:53 08:53, 24 April 2024 Htietze talk contribs 7,179 bytes −52 Matrix 7 March 2024 cur prev 08:17 08:17, 7 March 2024 Htietze talk contribs 7,231 bytes +68 Balsamiq -> Penpot cur prev 01:16 01:16, 7 March 2024 Chtfn talk contribs m 7,163 bytes −42 replace dead link about Balsamiq 24 March 2023 cur prev 17:55 17:55, 24 March 2023 Beluga talk contribs m 7,205 bytes −34 Text replacement - "{{#translation:}}" to "" cur prev 17:45 17:45, 24 March 2023 Beluga talk contribs m 7,239 bytes +12 Text replacement - "{{portal box|" to "{{portal box|1=" 28 February 2023 cur prev 06:45 06:45, 28 February 2023 Beluga talk contribs m 7,227 bytes −4 Text replacement - "{{TNT|TopMenu}}" to "{{TopMenu}}" 17 February 2023 cur prev 10:05 10:05, 17 February 2023 Beluga talk contribs m 7,231 bytes −13 Text replacement - "{{TopMenu{{#translation:}}}}" to "{{TNT|TopMenu}}" 16 February 2023 cur prev 07:40 07:40, 16 February 2023 Beluga talk contribs m 7,244 bytes 0 Text replacement - "repeat(auto-fit, minmax(350px, 1fr))" to "repeat(auto-fit, minmax(310px, 1fr))" 9 December 2022 cur prev 07:39 07:39, 9 December 2022 Beluga talk contribs 7,244 bytes +12 Marked this version for translation cur prev 07:39 07:39, 9 December 2022 Beluga talk contribs 7,232 bytes +649 More task definitions, cleanups 10 June 2022 cur prev 12:27 12:27, 10 June 2022 Beluga talk contribs 6,583 bytes +303 Marked this version for translation cur prev 12:27 12:27, 10 June 2022 Beluga talk contribs 6,280 bytes +344 Move to Translate extension 22 April 2022 cur prev 09:48 09:48, 22 April 2022 Htietze talk contribs 5,936 bytes −45 Matrix 12 November 2021 cur prev 09:21 09:21, 12 November 2021 Beluga talk contribs 5,981 bytes −6 Nabble no more 3 June 2021 cur prev 03:58 03:58, 3 June 2021 Fito talk contribs m 5,987 bytes +13 No edit summary 31 May 2021 cur prev 11:00 11:00, 31 May 2021 Beluga talk contribs 5,974 bytes −12 drop freenode mention 3 September 2020 cur prev 11:35 11:35, 3 September 2020 Fito talk contribs m 5,986 bytes −2,136 No edit summary 19 August 2020 cur prev 19:44 19:44, 19 August 2020 Wget talk contribs 8,122 bytes +143 Undo revision 294073 by Wget ( talk ) The scrolling position is broken on the website. Not a linking problem then. Undoing. Tag : Undo cur prev 18:16 18:16, 19 August 2020 Wget talk contribs m 7,979 bytes −143 libreoffice-ux-advise is deprecated and now ~only used for Bugzilla notifications. Don't encourage new subscriptions to this list. 14 July 2020 cur prev 10:07 10:07, 14 July 2020 Htietze talk contribs 8,122 bytes +210 Matrix 6 July 2020 cur prev 12:02 12:02, 6 July 2020 Fito talk contribs 7,912 bytes −592 Undo revision 277849 by Mpumrlova ( talk ) Use a subpage Tag : Undo cur prev 10:25 10:25, 6 July 2020 Mpumrlova talk contribs 8,504 bytes +592 No edit summary 2 February 2020 cur prev 10:11 10:11, 2 February 2020 Mikekaganski talk contribs 7,912 bytes +7,912 Undo revision 245406 by PulkitKrishna00 ( talk ) - undo malicious edit Tag : Undo cur prev 07:11 07:11, 2 February 2020 PulkitKrishna00 talk contribs empty −7,912 Hey! Hey! :) Tag : Blanking 16 January 2020 cur prev 16:01 16:01, 16 January 2020 Htietze talk contribs 7,912 bytes +2 Times corrected cur prev 13:49 13:49, 16 January 2020 Beluga talk contribs 7,910 bytes +6 Fix Jitsi link 19 December 2019 cur prev 13:20 13:20, 19 December 2019 Htietze talk contribs 7,904 bytes +41 Biweekly 11 April 2019 cur prev 13:03 13:03, 11 April 2019 Mike.saunders talk contribs 7,863 bytes −63 Removing dead Google+ link 23 July 2018 cur prev 08:14 08:14, 23 July 2018 Htietze talk contribs m 7,926 bytes −37 CEST cur prev 08:13 08:13, 23 July 2018 Htietze talk contribs m 7,963 bytes +38 CEST 25 June 2018 cur prev 06:21 06:21, 25 June 2018 Htietze talk contribs m 7,925 bytes −14 Telegram link update 14 November 2017 cur prev 13:08 13:08, 14 November 2017 Htietze talk contribs 7,939 bytes +1 New call time 27 October 2017 cur prev 17:55 17:55, 27 October 2017 Htietze talk contribs m 7,938 bytes −1 CEST -> CET cur prev 16:17 16:17, 27 October 2017 Philipz talk contribs m 7,939 bytes −44 fix link to weekly meetup 26 September 2017 cur prev 07:58 07:58, 26 September 2017 Beluga talk contribs 7,983 bytes −93 Changed IRC link to use the IRC template 14 September 2017 cur prev 09:46 09:46, 14 September 2017 K-j talk contribs 8,076 bytes −161 No need for a table for header. Getting the whole thing a little bit nearer to Heading. 9 August 2017 cur prev 21:04 21:04, 9 August 2017 Htietze talk contribs m 8,237 bytes −12 New meeting time 7 June 2017 cur prev 18:29 18:29, 7 June 2017 Vsfoote talk contribs 8,249 bytes +96 added link to archive of Design meeting minutes in the contact adjusted meeting time for CEST 25 April 2017 cur prev 12:08 12:08, 25 April 2017 Dennisroczek talk contribs 8,153 bytes +20 test 24 April 2017 cur prev 12:30 12:30, 24 April 2017 Philipz talk contribs m 8,133 bytes +56 add telegram link 4 January 2017 cur prev 12:50 12:50, 4 January 2017 Htietze talk contribs m 8,077 bytes −4 Reference fixed 17 November 2016 cur prev 08:54 08:54, 17 November 2016 Htietze talk contribs 8,081 bytes −4 New meeting time 22 October 2016 cur prev 13:43 13:43, 22 October 2016 Philipz talk contribs 8,085 bytes −95 added space between the sections cur prev 13:17 13:17, 22 October 2016 Htietze talk contribs m 8,180 bytes 0 Missing pipe cur prev 13:16 13:16, 22 October 2016 Htietze talk contribs m 8,180 bytes +1 Closing bracket cur prev 13:15 13:15, 22 October 2016 Htietze talk contribs 8,179 bytes −55 Full redesign; more into text, updated links, layout internally changed 27 August 2016 cur prev 03:25 03:25, 27 August 2016 Tagezi talk contribs m 8,234 bytes +21 added Category:Design using HotCat 26 August 2016 cur prev 21:18 21:18, 26 August 2016 Tagezi talk contribs m 8,213 bytes −20 removed Category:Design using HotCat 8 March 2016 cur prev 12:55 12:55, 8 March 2016 CleanupBot talk contribs 8,233 bytes +2 fix external links / use https links ( newest | oldest ) View ( newer 50 | older 50 ) ( 20 | 50 | 100 | 250 | 500 ) Retrieved from " https://wiki.documentfoundation.org/Design " Privacy policy About The Document Foundation Wiki Imprint | 2026-01-13T09:29:33 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3Abreadcrumb-config-outline | 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://www.chinadaily.com.cn/regional/#myCarousel | Regional - China Local News, Headlines &#38; Regional Economy - Chinadaily.com.cn Search HOME CHINA WORLD BUSINESS LIFESTYLE CULTURE TRAVEL VIDEO SPORTS OPINION REGIONAL NEWSPAPER MOBILE Global Edition ASIA 中文 双语 Français HOME CHINA WORLD BUSINESS LIFESTYLE CULTURE TRAVEL VIDEO SPORTS OPINION REGIONAL NEWSPAPER China Daily PDF China Daily E-paper MOBILE Regional Home > Regional Advertorial Cold front coats Guizhou mountains in rime China-Austria winter carnival kicks off in Shanxi Freight train brings Gansu seeds to Europe Shanghai retains world's busiest container port title for 16th year 1 2 3 4 Cold front coats Guizhou mountains in rime China-Austria winter carnival kicks off in Shanxi Freight train brings Gansu seeds to Europe Shanghai retains world's busiest container port title for 16th year Zodiac Longquan celadon gains popularity as Year of the Horse nears Transportation leap propels Jinan toward national hub A taste of Chile brightens Changchun's winter Provinces, Municipalities and Autonomous Regions Cities and Districts Business --> Institutes Events Culture and Tourism Special + Advertorial --> Intl investment and innovation highlighted by Weichai Group Xiaogan ICH XianHitechZone2025 130th Anniversary of Tianjin University Hangzhou Ningbo Wenzhou Huzhou Jiaxing Shaoxing Jinhua Quzhou Zhoushan Taizhou Lishui Latest + --> Advertorial Shandong enterprises thrive in global supply chains with RCEP Guiyang selected as City of the Year Xizang reports strong cultural and tourism growth Liangjiang accelerates NEV exports UK Garden takes root in Wenzhou Winter comes alive at Chagan Lake festival Qingdao airport sets new records in 2025 with enhanced global connectivity Florence welcomes cultural showcase from Ningbo Xizang's South Asia freight service sees strong growth in 2025 Guest from Indonesian business school visits Nantong Vocational University Top BACK TO THE TOP English 中文 HOME CHINA WORLD BUSINESS LIFESTYLE CULTURE TRAVEL VIDEO SPORTS OPINION REGIONAL NEWSPAPER China Daily PDF China Daily E-paper MOBILE Copyright 1994 - . All rights reserved. The content (including but not limited to text, photo, multimedia information, etc) published in this site belongs to China Daily Information Co (CDIC). Without written authorization from CDIC, such content shall not be republished or used in any form. Note: Browsers with 1024*768 or higher resolution are suggested for this site. License for publishing multimedia online 0108263 Registration Number: 130349 About China Daily Advertise on Site Contact Us Job Offer Expat Employment FOLLOW US Copyright 1994 - . All rights reserved. The content (including but not limited to text, photo, multimedia information, etc) published in this site belongs to China Daily Information Co (CDIC). Without written authorization from CDIC, such content shall not be republished or used in any form. --> | 2026-01-13T09:29:33 |
https://www.chinadaily.com.cn/a/202510/31/WS690485ada310f735438b81e9.html | 'Charming Beijing' TV Series overseas promotion event held in Oct - Chinadaily.com.cn Search HOME CHINA WORLD BUSINESS LIFESTYLE CULTURE TRAVEL WATCHTHIS SPORTS OPINION REGIONAL FORUM NEWSPAPER MOBILE Home World Beijing in Eyes of Foreign Reporters Home / World / Beijing in Eyes of Foreign Reporters 'Charming Beijing' TV Series overseas promotion event held in Oct chinadaily.com.cn | Updated: 2025-10-31 17:47 Share Share - WeChat --> CLOSE The 2025 "Charming Beijing" TV series overseas promotion event was successfully held in Beijing from Oct 19 to Oct 25. --> --> Photo Tracing China's icebreaker Tansuo 3 Xi meets Japanese PM Xi meets Thai PM Xi meets Canadian PM At 3,000m, I found a 'bridged' future Highlights of Xi's remarks during his meeting with Trump --> --> Top BACK TO THE TOP English 中文 HOME CHINA WORLD BUSINESS LIFESTYLE CULTURE TRAVEL VIDEO SPORTS OPINION REGIONAL NEWSPAPER China Daily PDF China Daily E-paper MOBILE Copyright 1995 - . All rights reserved. The content (including but not limited to text, photo, multimedia information, etc) published in this site belongs to China Daily Information Co (CDIC). Without written authorization from CDIC, such content shall not be republished or used in any form. Note: Browsers with 1024*768 or higher resolution are suggested for this site. License for publishing multimedia online 0108263 Registration Number: 130349 About China Daily Advertise on Site Contact Us Job Offer Expat Employment FOLLOW US Copyright 1995 - . All rights reserved. The content (including but not limited to text, photo, multimedia information, etc) published in this site belongs to China Daily Information Co (CDIC). Without written authorization from CDIC, such content shall not be republished or used in any form. --> | 2026-01-13T09:29:33 |
https://global.chinadaily.com.cn/business/5c23362ba310d91214051083 | Technology - Chinadaily.com.cn Global Edition China Edition ASIA 中文 双语 Français Global Edition HOME OPINION VIDEO WORLD TECH CHINA BUSINESS CULTURE TRAVEL SPORTS HOME OPINION VIDEO WORLD CHINA TECHNOLOGY BUSINESS CULTURE TRAVEL SPORTS SERVICE NEWSPAPER China Daily PDF China Daily E-paper Subscribe Home | Technology Hard-tech firms spearhead new IPO listing wave 2026-01-13 14:08 HK sees innovation, tech efforts bear fruit 2026-01-13 09:21 Satellite industry set for rapid expansion 2026-01-13 09:06 City eyes eVTOL dominance positioning 2026-01-13 09:02 China files plans for 200,000-plus satellites with global body 2026-01-12 18:07 Meta rings opening bell in age of AI agents 2026-01-12 09:15 AI prowess redefining business niches 2026-01-12 09:07 MiniMax sees market value cross HK$100b after shares jump 100% on debut 2026-01-10 19:19 Massive year-end bonuses at Chinese internet, tech companies 2026-01-09 09:55 China unfazed by Japan's possible bans 2026-01-09 09:48 White paper details Shanghai's rise as AI manufacturing hub 2026-01-08 22:34 Qingdao Port pushes intelligence deployment 2026-01-08 09:14 China sets 2027 goal for breakthrough in core AI tech 2026-01-07 19:26 Foreign tech giants sanguine on China ops 2026-01-07 09:46 Cool dancing robots bust a move in Guangxi 2026-01-06 09:37 Embodied intelligence industry shows big leap forward in 2025 2026-01-05 09:14 AI has finger on pulse of healthcare advances 2026-01-05 07:20 AI unlocks silver screen for people with disabilities 2026-01-03 08:39 Generative AI driving computer power demand: researchers 2025-12-31 20:14 From plateau to hard drives: documentary tests NAS technology 2025-12-30 17:17 1 2 3 4 5 6 7 8 9 10 Next >>| 1/537 Next Most Popular Columnists World should condemn naked US imperialism FTP has given Sanya a complete makeover A plea for the sake of left-behind kids Editor's Pick Women seen at forefront of AI adoption Foreign firms bullish on China opportunities Special 2025 'Charming Beijing' GMD SCO Summit Cities Tianjin Grow with SCO Russia-Ukraine conflict: Three years on Global Edition Copyright 1994 - . All rights reserved. The content (including but not limited to text, photo, multimedia information, etc) published in this site belongs to China Daily Information Co (CDIC). Without written authorization from CDIC, such content shall not be republished or used in any form. Note: Browsers with 1024*768 or higher resolution are suggested for this site. 中文 Desktop BACK TO THE TOP China Edition 中文 HOME OPINION VIDEO WORLD CHINA TECHNOLOGY BUSINESS CULTURE TRAVEL SPORTS SERVICE NEWSPAPER China Daily PDF China Daily E-paper Subscribe Copyright 1995 - . All rights reserved. The content (including but not limited to text, photo, multimedia information, etc) published in this site belongs to China Daily Information Co (CDIC). Without written authorization from CDIC, such content shall not be republished or used in any form. Note: Browsers with 1024*768 or higher resolution are suggested for this site. License for publishing multimedia online 0108263 Registration Number: 130349 About China Daily Advertise on Site Contact Us Job Offer Expat Employment --> | 2026-01-13T09:29:33 |
https://chromewebstore.google.com/detail/category/top-charts/detail/askbelynda-sustainable-sh/category/extensions/productivity/detail/compose-ai-ai-powered-wri/ddlbpiadoechcolndfeaonajmngmhblj | 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/gtx/5d63917ba31099ab995dbb29/worldnews | 世界说 - 中国日报网 China Daily Homepage 中文网首页 时评 资讯 C财经 生活 视频 专栏 双语 --> 原创 观天下 地方 --> 登录 注册 观天下 移动新媒体 站内搜索 站内搜索 观天下 China Daily Homepage 中文网首页 时评 资讯 C财经 生活 视频 专栏 双语 --> 漫画 原创 观天下 地方 世界说 世界说 【世界说】国际法专家密集发声：美对委行动是于法无据的“强权即公理”行径 损害国际秩序根基 5 天 前 【世界说】对委军事行动遭美国国内声讨 议员警告：终将给美民众带来灾难性后果 6 天 前 【世界说】美国媒体2025年终回顾：贸易战最大教训——消费者被迫承受更高生活成本 2 周 前 【世界说】外媒：美对台军售只为敲骨吸髓满足自身利益 2 周 前 【世界说】美媒：必需品通胀吞噬购买力，美国消费者感受到寒意 2 周 前 【世界说・年终观察】2025年美国枪暴“多棱镜”：被压制的研究，被贩卖的恐惧，被撕裂的校园 2 周 前 【世界说】日本官员“拥核言论”暴露危险野心 多方警告勿蹈覆辙 3 周 前 【世界说】“我们亲历过核事故风险，不能轻视它” 外媒：日本将重启其最大核电站，当地民众谨慎存疑 3 周 前 【世界说】日本防卫费“野蛮生长”引国际担忧，专家警告威胁地区安全且民生在“防卫优先”下承压 4 周 前 【世界说】日本网络平台“嫌中”视频招聘暴露右翼水军产业化链条 4 周 前 【世界说】当美国假日季遭遇通胀 美最新民调：近七成民众坦言财务焦虑让节日计划“缩水” 4 周 前 【世界说】菲学者：高市早苗涉台错误言论犹如打开亚太地缘安全“潘多拉魔盒” 1 个月 前 【世界说】“存亡危机”言论成自困预言 日本经济恐因高市挑衅言论承受沉重代价 1 个月 前 【世界说】外媒：日本“和平假面”下防卫预算13连增 应警惕军国主义幽灵复现 1 个月 前 【世界说】日学者及国际政界人士批高市涉台错误言论：触碰多重红线 违背历史正义与外交共识 2 个月 前 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://www.atlassian.com/es/jira/solutions/planning | Planificación del software de gestión de proyectos | 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 ¡Atlassian ha obtenido el reconocimiento de líder en el Magic Quadrant™ de Gartner® de 2025 en la categoría de gestión del trabajo colaborativo! Más información JIRA PARA LA PLANIFICACIÓN Planificación flexible para cualquier equipo Mantén a los equipos y a las partes interesadas sincronizados, asíncronos y alineados con tus objetivos. Consigue Jira gratis Súmate a los más de 300 000 clientes que fomentan la colaboración en equipo con Atlassian ¿Por qué utilizar Jira para la planificación? Visualiza tu trabajo Divide los proyectos complejos en partes pequeñas y gestionables. Añade y ajusta el trabajo sin esfuerzo para visualizar los plazos y la secuencia de las diferentes tareas. Comparte fácilmente Los plazos se actualizan en tiempo real a medida que avanza el trabajo, lo que permite compartirlos al instante con los equipos, los líderes y las partes interesadas. Tu plan, tu estilo Tanto si empiezas desde cero como si utilizas una plantilla, tienes libertad para personalizar tu plan según tus condiciones y necesidades. Descubre cómo tu trabajo contribuye a los objetivos de la empresa Compara las funciones de planificación Advanced Basic Planes , una función de planificación avanzada de Jira Premium, permite a varios equipos colaborar en objetivos o programas compartidos. El cronograma , una vista de proyecto disponible en todas las ediciones de Jira, te permite planificar y hacer un seguimiento del trabajo dentro de un solo equipo. Impulsa el trabajo interdisciplinar con Jira Seguimiento del panorama general Compara las funciones de planificación Advanced Basic Planes ayuda a hacer un seguimiento del trabajo en varios equipos y proyectos . En la pantalla de resumen de un plan, puedes obtener una visión global del progreso del trabajo, las dependencias y la capacidad del equipo. La vista de cronograma te permite planificar el trabajo y hacer un seguimiento de las dependencias de un solo equipo . Adelántate a las dependencias Compara las funciones de planificación Advanced Basic Asigna las dependencias en los distintos equipos, proyectos y demás para adelantarte a los posibles conflictos de recursos o planificación. Indica las dependencias a las partes interesadas insertando tu plan en una página de Confluence. Asigna las dependencias entre los elementos de trabajo de tu proyecto para identificar y tener en cuenta los posibles impedimentos. Align delivery across multiple teams Advanced only Use program boards to bring teams of teams onto a single plan. Align delivery across multiple sprints and keep complex projects progressing smoothly and on schedule. Planifica con la capacidad del equipo en mente Solo Advanced Determina si tus equipos cuentan con el ancho de banda suficiente para llevar a cabo el trabajo y no desviarse del objetivo. Consulta la capacidad de varios equipos sprint por sprint. Prevé varias situaciones Solo Advanced Elabora una descripción más completa de los posibles resultados creando varias versiones de tu plan en función de las diferentes opciones o de los mejores y peores escenarios. Release with confidence Advanced only Use releases to track progress, manage timelines, and keep every launch focused. Achieve smoother, more predictable releases that move the business forward. Plantillas diseñadas para planificar Descubre las plantillas personalizables de Jira para cada tipo de plan. Planificación de alto nivel Planifica, supervisa e informa sobre los esfuerzos de toda la empresa, como un programa o una iniciativa. Planificación entre equipos Planifica y asigna el trabajo, gestiona la capacidad y monitoriza el progreso en varios equipos de scrum. Gestión de proyectos Desde la organización de tareas hasta la visualización de plazos, permite a los equipos tener una visión general del progreso del proyecto. Explorar más plantillas Recursos de planificación Consulta artículos, guías y tutoriales gratuitos para obtener más información. Cómo utilizar Jira para la planificación Tutoriales sobre cómo planificar el trabajo, hacer un seguimiento del progreso y asignar dependencias. Ver la guía Planificación estratégica con Jira Conoce el marco de planificación estratégica y cómo puede ayudarte a lograr grandes objetivos. Más información Aspectos básicos de la planificación de sprints Lo esencial para aplicar la metodología scrum en los flujos de trabajo de tu equipo. Descubrir ahora Transforma tu forma de trabajar Donde las organizaciones y los equipos puedan trabajar como uno solo. Obtener gratis 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:33 |
https://giantrabbit.com/our-work?client=tor-project | 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://chromewebstore.google.com/detail/category/top-charts/detail/askbelynda-sustainable-sh/category/extensions/productivity/detail/wordtune-ai-paraphrasing/nllcnknpjnininklegdoijpljgdjkijc | 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://ace.atlassian.com/companyusergroup | Launch a company user group and transform your organization | 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 Join now Be the change that transforms your organization Company user groups are found in organizations around the world and exist to create stronger teams, improve product adoption, and deepen collaboration. Start organizing your own group with our all-in-one kit. Download now Power a thriving organization Get the most out of your tools Host a company user group to address FAQs, common use cases, and improve product onboarding. Shift corporate culture from within Enable connected and engaged teamwork, streamline tooling, and scale solutions throughout the organization. Build & boost your career Establish yourself as a thought leader, and get direct access to Atlassian teams, training, and certification. Become a Success Champion Become a Success Champion and lead the way in adopting Atlassian apps with dedicated resources, support, and recognition from Atlassian. Learn more Getting started is easy Whether you’re an Atlassian beginner, admin, or just a fan, anyone can spark change at their company and promote better teamwork. STEP 1 Download our all-in-one kit Get group templates, best practices, a sample presentation, and other content for group management in this starter pack. Download now STEP 2 Meet others organizers Swap ideas, get inspired, and share your advices with other Company User Group Leaders. Count me in STEP 3 Plan your first event Included in the kit is a first-meeting planning template. Identify objectives that ladder back to company goals, set an agenda, and more. Meet the changemakers Hear how other Company User Group Leaders are helping their teams (and companies) to unleash their full potential. Company user groups allow us to challenge the way we work and think. And great ideas come out of them for the benefit of our organizations, teams, and individuals. Siddharth Pareek Vice President for Natwest Group DevOps CoE Practice Company user groups help break silos, create stronger business relationships, and bring in diverse experience and expertise. Saurabh Sharma Senior Manager, Technology & Operations Leading Financial Institution, North America Connect with other company user group leaders Get everything you need to organize an event Fill out this form to get our all-in-one kit sent straight to your inbox. Get templates, sample agendas, checklists, and more! First name Last name Email address * By signing up on this form, I acknowledge Atlassian’s Privacy Policy . Yes! I would like to receive promotional emails including product news, events and more from Atlassian and its affiliates. Download kit Thank you! As you get acquainted with the contents of your kit, feel free to post questions or ideas in our dedicated Community group. Download kit Reach out with any questions: communitymanagers@atlassian.com Connect globally, meet locally Build a network of mentors and peers through virtual events and local meetups. Find your chapter Supercharge your events Take your events to the next level with additional support and resources. The Atlassian Playbook Get free workshops called Plays that help address common team challenges to run during an event. Explore Plays Atlassian Community Promote continuous learning and join our active community. Get product advice, earn badges, and much more. Learn more Atlassian Learning Bring your entire organization up to speed with tools to help distribute product training at scale. Get training Need more support? Our team is here every step of the way. Contact us 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.ecns.cn/video/2026-01-07/detail-iheyrzrv3837406.shtml | More than a business hub: check how global merchants thrive in Yiwu --> 中文 Home News Ecns Wire Business Travel Photo Video Voices RIGHT BG LINE Text: A A A Print Video More than a business hub: check how global merchants thrive in Yiwu 2026-01-07 13:40:32 Ecns.cn Editor : Ren Shuai ECNS App Download In Yiwu, the "World Capital of Small Commodities," most foreign merchants shuttle day and night between the trading markets and are occupied with cross-border orders. Yet beyond the hustle, their lives are really enriched by diverse passions—some practice martial arts, while some are avid cyclists. These hidden pursuits are not merely daily diversions but vital "energy boosts," fueling them with renewed enthusiasm and vibrant energy to help sell their products to the rest of the world. More Photo 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 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 Most popular in 24h More Top news Shanghai supermarkets become must-visit stops for South Korean tourists Ex-Gansu vice-governor convicted of bribery, insider trading Science fuels farm yields in Shaanxi Lithium-ion battery experiment conducted aboard Chinese space station Subsidies aid cross-Strait integration More Video Comicomment: Save or Slave? Hegemony at play Insights | Sanae Takaichi's erroneous remarks a grave 'diplomatic failure': Japanese scholar 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 |
http://www.goshanxi.com.cn/yangquan/ | Yangquan, China search Advertorial 中文 Home About Yangquan Overview Advantages Gallery Contact Us Government Officials Departments Media Center News Specials Investment Why Yangquan Investment Guide Key Projects Industrial Parks Enterprises Visiting Attractions Routes Transportation Foods & Restaurants Hotels & Shopping Culture Cultural Heritage Notable Citizens Living Visa Education Health Care Marriage & Adoption Useful Numbers 1 2 3 4 5 6 Prev Next Share your views on 2026 China's Government Work Report Yangquan fuels economic transformation with digital momentum During the 14th Five-Year Plan period (2021-25), Yangquan city in Shanxi province prioritized the development of the digital economy. Yangquan explores new pathways for industry-education integration Yangquan promotes selenium products in Beijing More.. Investment Yangquan harnesses IP to drive technological innovation Yangquan pioneers green energy revolution Yangquan pioneers future of smart cities Huayang Group advances green development in Yangquan city Visiting Cuifeng Mountain: A free summer retreat in Yangquan Explore Yangquan's enchanting rural wonders Cuifeng Mountain Scenic Area boostsgears up for ice, snow economy Inaugural 'Taihang No 1' cycling open kicks off in Yangquan Culture Yangquan revitalizes industrial heritage Yangquan hosts Longzhong painted pottery exhibition Shanxi TV Drama Week kicks off in Niangziguan Bringing Wukong to life: Yangquan artist blends tradition and pop culture Living Yangquan enhances urban landscape Yangquan enhances elderly care services New Year hike in Yangquan attracts over 3,000 participants Visa-free entry coming for more countries Specials Xi Up-close: Inspiring young minds with the power of the past China's public holidays for 2025 Favorable policies boost 'China Travel' trend Gallery Yangquan sand pottery industry thrives Overview Yangquan economy sees steady growth in 2024 search Links :   Shanghai Beijing Taiyuan Shanxi About Government Media Center Investment Why Yangquan Investment Guide Key Projects Industrial Parks Enterprises Visiting Attractions Routes Transportation Foods & Restaurants Hotels & Shopping Culture Cultural Heritage Notable Citizens Living Visa Education Health Care Marriage & Adoption Useful Numbers Copyright © The Publicity Department of the CPC Yangquan Municipal Committee. All Rights Reserved. Presented by China Daily. | 2026-01-13T09:29:33 |
https://english.www.gov.cn/policies/featured/202512/15/content_WS693febc1c6d00ca5f9a081ad.html | A look at China's economy in November, 2025 App HOME NEWS INSTITUTIONS POLICIES ARCHIVE 中文 HOME NEWS INSTITUTIONS POLICIES ARCHIVE 中文 A look at China's economy in November, 2025 Updated: December 15, 2025 19:06 english.www.gov.cn Copyright© www.gov.cn | About us | Contact us Website Identification Code bm01000001 Registration Number: 05070218 All rights reserved. The content (including but not limited to text, photo, multimedia information, etc) published in this site belongs to www.gov.cn. Without written authorization from www.gov.cn, such content shall not be republished or used in any form. Mobile Desktop Copyright© www.gov.cn | Contact us Website Identification Code bm01000001 Registration Number: 05070218 | 2026-01-13T09:29:33 |
https://cn.chinadaily.com.cn/5b753f9fa310030f813cf408/5bd7efdfa3101a87ca8ff812/2025charmingbeijing | --> 2025“魅力北京”海外传播活动 - 中国日报网 China Daily Homepage 中国日报中文网 English logo --> logo --> 魅力北京世界共享”—“魅力北京”系列电视片海外传播分享会成功在京举行（四） 魅力北京世界共享”—“魅力北京”系列电视片海外传播分享会成功在京举行（三） 魅力北京世界共享”—“魅力北京”系列电视片海外传播分享会成功在京举行（二） 魅力北京世界共享”—“魅力北京”系列电视片海外传播分享会成功在京举行（一） 详细>> 2025“魅力北京”系列电视片海外传播活动于10月19日至10月25日在北京成功举办 详细>> “魅力北京 世界共享”分享会在京举行 详细>>     外媒看北京 更多>> 2025“魅力北京”系列电视片海外传播活动于10月19日至10月25日在北京成功举办 “魅力北京 世界共享”分享会在京举行 【魅力北京】俄哈两国电视台摄制组来京采风拍摄 俄哈两国摄制组深入首都，探索科技前沿与历史记忆   多语种报道 更多>>   最新消息 更多>> 魅力北京世界共享”—“魅力北京”系列电视片海外传播分享会成功在京举行（四） 魅力北京世界共享”—“魅力北京”系列电视片海外传播分享会成功在京举行（三） 魅力北京世界共享”—“魅力北京”系列电视片海外传播分享会成功在京举行（二） 魅力北京世界共享”—“魅力北京”系列电视片海外传播分享会成功在京举行（一）   往届专题 更多>> --> --> --> -->   关于我们 | 联系我们 | 2026-01-13T09:29:33 |
https://www.chinanews.com.cn/common/footer/aboutus.shtml | About us 关于我们 About us 联系我们 广告服务 供稿服务 法律声明 招聘信息 网站地图 China News Service Chinanews.com Contact us China News Service (CNS) is a state-level news agency in China providing news coverage to the world. Its main subscribers include those from Taiwan, Hong Kong and Macao special administrative regions, overseas Chinese and related foreigners. CNS was sponsored and established by Chinese journalists and renowned overseas Chinese experts on October 1, 1952. Liao Chengzhi, former vice chairman of the Standing Committee of the National People's Congress, was the founder as well as leader of CNS.JinZhonghua, a famous expert on international issues, served as the first president of CNS. Formerly, CNS was known as International News Service, established by Fan Changjiang, Hu Yuzhi and Yu Guilin in 1938. Based on a multi-channel, multi-level and multi-function system, CNS provides all kinds of products regarding news and information, namely articles, photos, videos, infographics, social media, etc, without pause 24 hours a day. Its subscribers can be found all over the world, forming an all-media client network covering major overseas Chinese media. As a Chinese-language media outlet, CNS was the first in Asia to set up an Internet portal. The website Chinanews.com was launched in Hong Kong in 1995. On January 1, 1999, the headquarters of CNS launched its official website www.chinanews.comand affiliated website www.chinaqw.com for overseas Chinese and Chinese with foreign nationalities. Chinanews.com is an important state-level news website in China. CNS edits and publishes China News Weekly, China News, The China Journalism Yearbook, China Philanthropist and other newspapers and periodicals. Other than the Chinese version, China News Weekly is published in seven languages, nine versions, including the American, British, Japanese, Korean, Italian, South Asian, French, Russian and Arabic editions. "The Forum on Global Chinese Language Media" hosted by CNS every two years is the largest summit attended by heads of Chinese language media worldwide. Eleven sessions have taken place in Nanjing, Wuhan, Changsha, Chengdu, Shanghai, Chongqing, Qingdao, Guiyang, Fuzhou,Shijiazhuang, and Chengdu by far. The secretariat of the Global Chinese Media Cooperation Union is located in CNS. Chinanews Chinese Introduction>> 地址：北京百万庄南街12号中国新闻社 邮编：100037 微信公众号 手机移动版 新闻客户端 Established on October 1, 1952, China News Service (CNS) is one of the two state-level news agencies in China. Its predecessor, International News Agency, was founded in 1938. CNS has 31 branches in provinces and municipalities on the Chinese Mainland and 21 outbound branches or report stations in regions and countries including the United States, Canada, the UK, France, Germany, Belgium, Russia, the Republic of Korea, Japan, Australia, Thailand and Kazakhstan. As a Chinese-language media source, CNS has been an Asian pioneer since it first set up its internet portal. Its website, www.chinanews.com, was launched in Hong Kong in 1995. At present, it boasts subscribers in more than 100 countries and regions across the world. As the official website of CNS, China News Network provides news products around the clock based on its sound domestic and foreign news collection and release system, and three news centers in Beijing, New York and Hong Kong. It is now one of the world’s most prominent providers of news content, photos, and videos. Its media matrix contains affiliated websites, including CNS Video, Economic View, www.chinaqw.com and Qiaobao App for overseas Chinese and Chinese with foreign nationalities, Overseas Chinese Language and Culture Education Online, and ECNS, its official English website. Its articles cover major domestic online media and reach over 100 countries around the world, making China News Network one of the top influential official state websites in the country. In recent years, various new media platforms under China News Service (CNS) have accelerated the integrated development and the construction of comprehensive media matrix centered around websites, mobile apps, and social media accounts, accumulating nearly 500 million users in total. The China News Network’s official website has daily views of 230 million on average, with more than 60 million APP installations. In addition, China News Network has more than 80 million followers on Weibo, with more than 100 million average daily views. Its official WeChat public account has published over 3,000 articles with over 100,000 views annually. Across platforms including Douyin, Kuaishou, and WeChat Channels and Wesee, it has a total fan base of over 75 million, with a daily playback volume of 200 million. Besides, there are nearly 10 million followers on overseas social media platforms like Facebook, X (formerly known as Twitter) and YouTube. In 2019 White Paper on the Social Value of China's Online Media, published by the State Information Center (Administration Center of China E-government Network), China News Network came out on top in the “Most Socially Attractive websites” and harvested a bunch of significant awards, including “Top 10 Chinese News Websites”, “Leading News Website”, and “Most Influential Website”. Chinanews Chinese Introduction>> 地址：北京百万庄南街12号中国新闻社 邮编：100037 微信公众号 手机移动版 新闻客户端 Edit Dept Address: Floor 3, No.12 Baiwanzhuang South Street,Xicheng District,Beijing 100037,P.R.China Email: gaojian#chinanews.com.cn (Please change # to @) Tel: 15699788000 Fax: 86-10-68327649 Editing Management Dept Address: Floor 3, No.12 Baiwanzhuang South Street,Xicheng District,Beijing 100037,P.R.China Email: gaojian#chinanews.com.cn (Please change # to @) Tel: 86-10-68311579 Fax: 86-10-68327649 Human Resources Dept. Address: Floor 3, No.12 Baiwanzhuang South Street,Xicheng District,Beijing 100037,P.R.China Email: zhaopin#chinanews.com.cn (Please change # to @) Tel: 86-10-88311167 Fax: 86-10-68327649 Technique Dept. Address: Floor 3, No.12 Baiwanzhuang South Street,Xicheng District,Beijing 100037,P.R.China Email: tech#chinanews.com.cn (Please change # to @) Tel: 86-10-88311167 Fax: 86-10-68327649 地址：北京百万庄南街12号中国新闻社 邮编：100037 微信公众号 手机移动版 新闻客户端 --> | 2026-01-13T09:29:33 |
https://gitstar-ranking.com/NVIDIA | NVIDIA - Gitstar Ranking Gitstar Ranking Users Organizations Repositories Rankings Users Organizations Repositories Sign in with GitHub NVIDIA Star 350086 Rank 23 Go to GitHub Fetched on 2026/01/09 05:17 647 Repositories nvidia-docker 17471 open-gpu-kernel-modules 16597 Megatron-LM 14844 DeepLearningExamples 14678 TensorRT-LLM 12587 TensorRT 12575 FastPhotoStyle 11183 cutlass 9078 apex 8889 vid2vid 8707 cuda-samples 8677 Cosmos 8068 pix2pixHD 6936 garak 6732 FasterTransformer 6379 warp 6008 Isaac-GR00T 5852 DALI 5592 tacotron2 5300 thrust 4998 nccl 4366 DIGITS 4186 nvidia-container-toolkit 3968 GenerativeAIExamples 3699 k8s-device-plugin 3613 flownet2-pytorch 3271 cuda-python 3124 ChatRTX 3096 TransformerEngine 3073 MinkowskiEngine 2860 nv-ingest 2796 gpu-operator 2477 waveglow 2335 libcudacxx 2309 CUDALibrarySamples 2274 physicsnemo 2271 stdexec 2184 cccl 2114 Stable-Diffusion-WebUI-TensorRT 1994 semantic-segmentation 1815 cub 1814 cutile-python 1794 Model-Optimizer 1779 aistore 1719 DeepRecommender 1703 Cosmos-Tokenizer 1697 NeMo-Agent-Toolkit 1688 trt-samples-for-hackathon-cn 1650 dcgm-exporter 1562 OpenSeq2Seq 1557 1 2 3 4 5 … › Released by @k0kubun in December 2014. Fork me on GitHub . | 2026-01-13T09:29:33 |
https://www.chinadaily.com.cn/a/202507/09/WS686e5ec0a31000e9a573b1c2.html | A story of trust discovered at Tianjin Port - Chinadaily.com.cn Search HOME CHINA WORLD BUSINESS LIFESTYLE CULTURE TRAVEL WATCHTHIS SPORTS OPINION REGIONAL FORUM NEWSPAPER MOBILE Home World Videos Home / World / Videos A story of trust discovered at Tianjin Port By Yan An and Zheng Chenxiao | chinadaily.com.cn | Updated: 2025-07-09 20:21 Share Share - WeChat --> CLOSE What do ancient shells and modern global trade have in common? At the bustling smart zero-carbon terminal of Tianjin Port, China Daily reporter Yan An uncovered a timeless truth: trust fuels trade. There, she met Serik Korzhumbayev, editor-in-chief of the newspaper Delovoy Kazakhstan, who shared his insights on cooperation and trust among SCO member countries. Follow her to learn a trust story behind the smart port. --> --> Photo A story of trust discovered at Tianjin Port Bishkek seeks deeper ties with Chinese cities Nishan Forum in Shandong explores civilization's future Mayor of St. Petersburg: China is a strategic partner Watch it again: SCIO briefing on achievements of 14th Five-Year Plan Great Wall explorer records unmapped ruins --> --> --> --> Top BACK TO THE TOP English 中文 HOME CHINA WORLD BUSINESS LIFESTYLE CULTURE TRAVEL VIDEO SPORTS OPINION REGIONAL FORUM NEWSPAPER China Daily PDF China Daily E-paper MOBILE Copyright 1995 - . All rights reserved. The content (including but not limited to text, photo, multimedia information, etc) published in this site belongs to China Daily Information Co (CDIC). Without written authorization from CDIC, such content shall not be republished or used in any form. Note: Browsers with 1024*768 or higher resolution are suggested for this site. License for publishing multimedia online 0108263 Registration Number: 130349 About China Daily Advertise on Site Contact Us Job Offer Expat Employment FOLLOW US Copyright 1995 - . All rights reserved. The content (including but not limited to text, photo, multimedia information, etc) published in this site belongs to China Daily Information Co (CDIC). Without written authorization from CDIC, such content shall not be republished or used in any form. --> | 2026-01-13T09:29:33 |
https://wiki.documentfoundation.org/QA/Easy_Hacks | QA/Easy Hacks - 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 Contents move to sidebar hide Beginning 1 Easy Hacks about Quality Assurance Toggle Easy Hacks about Quality Assurance subsection 1.1 Skill Level: Beginner 1.2 Skill Level: Medium 1.3 Skill Level: Interesting 1.4 Skill Level: Unknown 1.5 Development EasyHacks Toggle the table of contents QA/Easy Hacks 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 < QA 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 Bug Report Bug Triage Projects Regression Test Automated Tests Bibisect QA Meetings QA FAQs This is a list of things to do to get started in QA for LibreOffice. Note that there is also a more narrow-scoped list of tasks at QA/Bugzilla/Gardening . Easy Hacks about Quality Assurance These lists contain the bugs with Keyword "topicQA". Skill Level: Beginner This list contains the bugs with keywords "difficultyBeginner" and "topicQA". Please enable JavaScript in your browser. Skill Level: Medium This list contains the bugs with keywords "difficultyMedium" and "topicQA". Please enable JavaScript in your browser. Skill Level: Interesting This list contains the bugs with keywords "difficultyInteresting" and "topicQA". Please enable JavaScript in your browser. Skill Level: Unknown This list contains the bugs with keywords "easyHack" and "topicQA". Please enable JavaScript in your browser. Development EasyHacks Here are the Developer EasyHacks ! Retrieved from " https://wiki.documentfoundation.org/index.php?title=QA/Easy_Hacks&oldid=324853 " Category : QA This page was last edited 16:06, 3 January 2021 by Ilmari Lauhakangas . Based on work by Robinson Tryon and Dennis Roczek 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:33 |
https://reports.jenkins.io/jelly-taglib-ref.html#form | 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://www.chinadaily.com.cn/a/202508/18/WS68a2853aa310b236346f21e1.html | Showcasing heritage - Chinadaily.com.cn Search HOME CHINA WORLD BUSINESS LIFESTYLE CULTURE TRAVEL WATCHTHIS SPORTS OPINION REGIONAL FORUM NEWSPAPER MOBILE Home World World in Focus Home / World / World in Focus Showcasing heritage Festival revives nomadic culture that shaped civilizations along the Silk Road China Daily | Updated: 2025-08-18 09:43 Share Share - WeChat --> CLOSE Kyrgyz hunters ride horses with their golden eagles during the Salbuurun Festival on the southern shore of Lake Issyk-Kul in Bishkek, Kyrgyzstan, on Aug 2. VLADIMIR VORONIN/AP Crowds gathered on the southern shore of Kyrgyzstan's Lake Issyk-Kul recently to witness the vibrant spectacle of the Salbuurun Festival — a spirited celebration of nomadic heritage. Held in the village of Bokonbaevo, the festival offered a whirlwind of traditional sports, art, and music, all rooted in centuries-old customs. --> 1 2 3 4 5 6 7 8 Next >>| --> 1/8 Next Photo Watch it again: Updates on preparations for the upcoming victory anniversary events Beef production hits its prime on grasslands SCO family: Together toward a shared future Tracking a mountain of history Avenue blooms with flowers to mark victory China Daily's 'Stories across the Strait' wins recommendation --> --> Top BACK TO THE TOP English 中文 HOME CHINA WORLD BUSINESS LIFESTYLE CULTURE TRAVEL VIDEO SPORTS OPINION REGIONAL FORUM NEWSPAPER China Daily PDF China Daily E-paper MOBILE Copyright 1995 - . All rights reserved. The content (including but not limited to text, photo, multimedia information, etc) published in this site belongs to China Daily Information Co (CDIC). Without written authorization from CDIC, such content shall not be republished or used in any form. Note: Browsers with 1024*768 or higher resolution are suggested for this site. License for publishing multimedia online 0108263 Registration Number: 130349 About China Daily Advertise on Site Contact Us Job Offer Expat Employment FOLLOW US Copyright 1995 - . All rights reserved. The content (including but not limited to text, photo, multimedia information, etc) published in this site belongs to China Daily Information Co (CDIC). Without written authorization from CDIC, such content shall not be republished or used in any form. --> | 2026-01-13T09:29:33 |
https://wiki.documentfoundation.org/Special:MyLanguage/Documentation | Documentation - 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 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 Documentation Home Official Publications Other Resources FAQ HowTo Macros Docs Development Other languages: Bahasa Indonesia Deutsch English Esperanto Jawa Nederlands Oromoo Türkçe asturianu català dansk español français galego italiano polski português português do Brasil română čeština монгол русский українська עברית العربية فارسی नेपाली தமிழ் ไทย བོད་ཡིག 中文（中国大陆） 中文（臺灣） 日本語 한국어 The LibreOffice Documentation Team is responsible for the development of the English language user documentation. This page serves as a portal both for the various forms of user documentation and the development thereof. To join the team and help out, start here . View and Download Documentation Official publications The official user guides and related publications are currently hosted at: LibreOffice documentation website (view online, download, or purchase) If you can't find what you're looking for, try the archive on the wiki: Recent publications Old publications Help pages Online help (same as built-in help, if installed ) In the wiki Extensive Description of Calc Functions Tutorials HowTo FAQ Macros Release Notes Other Resources Third Party Resources (including video tutorials) Developer's Guide (UNO API) LibreOffice Template System See Category:Documentation to find pages not yet linked here. Contribute to Guide Books Contributor's guide The Contributor's Guide is the reference for writing and updating LibreOffice Guides books. The guide includes the following chapters: Preface Joining the Documentation Team Producing LibreOffice User Guides Using the LibreOffice Documentation Team Website Style Guide for Writers (including preferred terminology) Using the Chapter Template (includes list of paragraph and character styles and when to use them, plus other information) Other information Tracking Tasks with Nextcloud Deck Getting Access to the Cloud Service The NextCloud client for desktop and tablets User Guide development Taking screenshots of LibreOffice dialogs Guides Website LibreOffice Guides Translation Using Kanban-like application for LibreOffice Guides Team Translation Translation using TDF Weblate service Contribute to Help Pages Help content LibreOffice Help Editing Rules for writing Help pages contents A Help XML editor How to create a collateral file for help pages Adding Rich Contents to Help Pages Basic Syntax Diagrams Editing source help pages directly in gerrit Help Content Modernization Proposed Extensions for XHP XHP Code Snippets for KDE Editors Understanding, Authoring and Editing LibreOffice Help (Book) This resource was originally written for OpenOffice.org, so a lot of its contents are obsolete. However, sections like the Help File XML reference are still relevant and updated. Understanding, Authoring and Editing LibreOffice Help (Book) How LibreOffice Help Works Help File XML format Basics Help File XML Reference Authoring Help With OpenOffice.org (please refer to Documentation/Help instead) Appendix More on Contributing Coordination Meet the Documentation Team Documentation Team meetings Documentation Forum Tasks General documentation wish list Bugs related to documentation All open bugs regarding documentation Top meta bug for documentation Meta bugs for missing documentation and documentation needing updating Further resources Divio's Documentation System Daniele Procida's PyCon AU talk on the topic: "What nobody tells you about documentation" Writing Extended Tips in LibreOffice Dialogs See also Contribute to Websites About the TDF Wiki Google Season of Docs 2023 edition 2022 edition 2021 edition 2020 edition 2019 edition Retrieved from " https://wiki.documentfoundation.org/index.php?title=Documentation&oldid=790808 " Category : Documentation This page was last edited 10:34, 31 March 2025 by Olivier Hallot . Based on work by Ady and Pierre 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:33 |
http://groovy-lang.org/syntax.html#_string_summary_table | 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://www.atlassian.com/ko/gartner/magic-quadrant-collaborative-work-management | Gartner® Magic Quadrant™ for Collaborative Work Management Platforms Close 선택한 언어 로 이 페이지를 보고 계십니까? 모든 언어 언어를 선택합니다. 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 무료로 시작 제품 추천 개발자 제품 매니저 IT 전문가 비즈니스 팀 리더십 팀 추천 개발자 제품 매니저 IT 전문가 비즈니스 팀 리더십 팀 모든 앱 보기 추천 추천 앱 Jira 유연한 프로젝트 관리 Confluence 공동 작업 중심의 지식 작업 영역 Jira Service Management 빠른 속도의 서비스 제공 Atlassian Collection 원활하게 팀워크 강화 Jira • Confluence • Loom • Rovo 전략 및 결과를 자신 있게 최적화 Focus • Talent • Align 신속한 서비스 제공 Jira Service Management • Customer Service Management • 자산 • Rovo 고품질 소프트웨어를 신속하게 제공 Rovo Dev • DX • Pipelines • Bitbucket • Compass 제공: Rovo 팀의 지식으로 구동되는 AI 기반 앱. 개발자 Jira 유연한 프로젝트 관리 Compass 팀을 위한 소프트웨어 카탈로그 파이프라인 확장 가능한 CI/CD 자동화 Bitbucket 소스 코드 및 CI/CD DX (인수 보류 중) 생산성 및 AI 영향 측정 Rovo Dev 개발자를 위한 에이전틱 AI 고품질 소프트웨어를 신속하게 제공 Rovo Dev • DX • Pipelines • Bitbucket • Compass Rovo 팀의 지식으로 구동되는 AI 기반 앱. 제품 매니저 Jira 유연한 프로젝트 관리 Confluence 모두 한곳에 있는 지식 Jira Product Discovery 신규 아이디어 캡처 및 우선 순위 지정 원활하게 팀워크 강화 Jira • Confluence • Loom • Rovo Rovo 팀의 지식으로 구동되는 AI 기반 앱. IT 전문가 Jira Service Management 빠른 속도의 서비스 제공 Guard 신규 향상된 클라우드 보안 Rovo 팀의 지식으로 구동되는 AI 기반 앱. 비즈니스 팀 Jira 유연한 프로젝트 관리 Confluence 모두 한곳에 있는 지식 Trello 체계적이고 시각화된 작업 Loom 신규 빠른 비동기식 동영상 업데이트 Jira Service Management 빠른 속도의 서비스 제공 Customer Service Management Customer experiences reimagined 원활하게 팀워크 강화 Jira • Confluence • Loom • Rovo Rovo 팀의 지식으로 구동되는 AI 기반 앱. 리더십 팀 Focus 신규 엔터프라이즈급 전략 계획 Talent 신규 지식 인력 계획 Jira Align 엔터프라이즈 전체에 걸친 작업 계획 및 가치 전략 및 결과를 자신 있게 최적화 Focus • Talent • Align Rovo 팀의 지식으로 구동되는 AI 기반 앱. Back 솔루션 솔루션 사용 사례별 팀 협업 전략 및 계획 서비스 매니지먼트 소프트웨어 개발 팀별 소프트웨어 마케팅 IT 크기별 Enterprise 소규모 비즈니스 Startup 비영리 기관 업계별 리테일 통신 프로페셔널 서비스 정부 Rovo 팀의 지식으로 구동되는 AI 기반 앱. Back Atlassian을 선택하는 이유 Atlassian을 선택하는 이유 업무 시스템 신규 팀 협업 방식에 대한 Atlassian의 블루프린트 통합 수천 개의 앱을 Atlassian 제품에 연결 고객 팀워크 기반의 사례 연구 및 스토리 FedRAMP 공공 부문을 위한 규정 준수 솔루션 복원력 엔터프라이즈급 및 고성능 인프라 플랫폼 고도로 통합되고 신뢰할 수 있는 안전한 플랫폼 Trust Center 데이터의 보안, 컴플라이언스 및 가용성 보장 Back 리소스 리소스 고객 지원 질문하고 버그를 신고하고 피드백을 제공 파트너 찾기 컨설팅, 교육 및 제품 사용자 지정 지원 Atlassian Ascend 전환을 위한 리소스 및 지원 커뮤니티 Atlassian 커뮤니티와 함께 배우고 소통하며 성장하세요 지원 일반적인 질문 제품 조언 파트너 지원 Enterprise 지원 기술 지원 가격 및 청구 개발자 지원 구매 및 라이선싱 리소스 프로젝트 관리 애자일 Atlassian Learning 시작하기 프로젝트 협업 팀 플레이북 제품 문서 Back Enterprise 자세한 내용 + 간략히 보기 - 무료로 시작 Jira 유연한 프로젝트 관리 Jira Service Management 빠른 속도의 서비스 제공 Confluence 모두 한곳에 있는 지식 제품 모두 보기 무료로 시작 Back 무료로 시작 Atlassian named a Leader in the 2025 Gartner ® Magic Quadrant TM for Collaborative Work Management We're proud to be recognized by Gartner as a Leader in Collaborative Work Management — we believe this is a testament to how Atlassian is transforming teamwork for the modern enterprise. Atlassian's work management solution connects planning, execution, and organizational knowledge through a unified, AI-powered system of work. This gives organizations the connectivity, visibility, and intelligence to align work to goals, accelerate execution, and improve continuously — so teams can focus less on managing work and more on driving impact. Download the report to learn: What defines a modern Collaborative Work Management solution How your organization should evaluate vendors Why Atlassian ranked as a Leader Access the complimentary report You’re logged in as: Update contact info > * Required fields Thank you! View the Report “To stay ahead of the curve, we needed to innovate faster, better, and more sharply. Atlassian’s Teamwork Collection, plus Rovo, provide a clear ‘factory-floor view' for our leaders and a single hub for teams to collaborate. This has helped improve our strategic alignment, focus, efficiency, and visibility – saving more than 4,000+ meetings and $500k+ in time in just four months. This transformation in turn is empowering our customers to make better deals, faster.” – Doug Cullen, CPO/CSO, Datasite The foundation for collaborative, intelligent work management Move faster, work smarter, and achieve greater outcomes together with Atlassian’s AI-Powered Teamwork Collection Jira provides the system of record for work—helping every team plan, coordinate, and deliver with clarity and confidence. Confluence is the collaborative workspace where teams and AI come together to create, share, and access knowledge seamlessly. Loom keeps information flowing between teams through video communication and makes meetings actionable. Rovo brings AI directly into workflows, intuitively surfacing context and driving faster outcomes. GARTNER is a registered trademark and service mark of Gartner, Inc. and/or its affiliates in the U.S. and internationally, Magic Quadrant is a registered trademark of Gartner, Inc. and/or its affiliates and is used herein with permission. All rights reserved. Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner’s research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose. 회사 구직 이벤트 블로그 투자자 관계 Atlassian Foundation 보도 자료 문의하기 제품 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket 제품 모두 보기 리소스 기술 지원 구매 및 라이선싱 Atlassian 커뮤니티 기술 자료 Marketplace 내 계정 지원 티켓 생성하기 자세히 알아보기 파트너 교육 및 인증 설명서 개발자 리소스 Enterprise 서비스 모든 리소스 보기 Copyright © 2025 Atlassian 개인정보보호 이용 약관 소유권 정보 언어 선택 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:33 |
https://chromewebstore.google.com/detail/category/top-charts/detail/askbelynda-sustainable-sh/category/extensions/productivity/detail/cheerie-you-search-we-don/hhiffohlmhfhobhohllphmiamcbbmlkl | 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://pix.webm.ink/site/kb/getting-started#collapse3 | Pixelfed Help Center minkpix Help Center — Getting Started Getting Started Sharing Media Profile Hashtags Discover Timelines Instagram Import Community Guidelines Safety Tips Getting Started Welcome to Pixelfed! How do I create a Pixelfed account? To create an account using a web browser: Go to https://pix.webm.ink . Click on the register link at the top of the page. Enter your name, email address, username and password. How to I update profile info like name, bio, email? You can update your account by visiting the account settings page. What can I do if a username I want is taken but seems inactive? If your desired username is taken you can add underscores, dashes, or numbers to make it unique. Why can't I change my username? Pixelfed is a federated application, changing your username is not supported in every federated software so we cannot allow username changes. Your best option is to create a new account with your desired username. I received an email that I created an account, but I never signed up for one. Someone may have registered your email by mistake. If you would like your email to be removed from the account please contact an admin of this instance. I can't create a new account because an account with this email already exists. You might have registered before, or someone may have used your email by mistake. Please contact an admin of this instance. About Help Terms Privacy Language © 2026 pix.webm.ink · Powered by Pixelfed · v0.12.6 | 2026-01-13T09:29:33 |
https://gitstar-ranking.com/freeCodeCamp | freeCodeCamp - Gitstar Ranking Gitstar Ranking Users Organizations Repositories Rankings Users Organizations Repositories Sign in with GitHub freeCodeCamp Star 504213 Rank 12 Go to GitHub Fetched on 2026/01/09 07:57 238 Repositories freeCodeCamp 435667 devdocs 38241 how-to-contribute-to-open-source 9242 mail-for-good 3827 guide 2152 chapter 1928 awesome-quincy-larson-emails 1176 LearnToCodeRPG 1099 boilerplate-npm 767 mobile 509 learn 488 pantry-for-good 396 boilerplate-infosec 381 meeting-for-good 338 CurriculumExpansion 336 Developer_Quiz_Site 291 100DaysOfCode-twitter-bot 289 wiki 282 boilerplate-express 260 chinese 228 boilerplate-mochachai 218 2016-new-coder-survey 200 python-coding-challenges 196 testable-projects-fcc 181 web3-curriculum 176 league-for-good 170 open-data 164 demo-projects 157 classroom 149 solana-curriculum 146 coderadio-client 144 boilerplate-project-timestamp 127 conference-for-good 118 contribute 112 assets 105 camper-gitter-bot 97 boilerplate-mongomongoose 92 open-api 87 cdn 83 curriculum 82 rdb-alpha 80 boilerplate-project-urlshortener 75 Rust-In-Replit 74 open-source-for-good-directory 74 infra 73 freeCodeCampOS 71 euler-rust 70 100DaysOfCode-discord-bot 70 news 64 boilerplate-project-exercisetracker 62 1 2 3 4 5 › Released by @k0kubun in December 2014. Fork me on GitHub . | 2026-01-13T09:29:33 |
https://issues.jenkins.io/secure/credits/AroundTheWorld!default.jspa#main | About Jira - 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 Jira Credits 🌍 ← Sydney Antoine Busch Senior Developer Alex Cooksey Service Enablement Engineer Customer Support Services Alex Courtis Senior Developer Diallo Abdoulaye Support Engineer Sydney Support Anton Ermolenko Senior Developer Engineering Ahmed Fouad Senior Developer Engineering Arik Friedman Principal Data Scientist Product Management Aidan Goldthorpe Developer Engineering Alex Hennecke Senior Developer Ashley Icamen Senior Technical Writer Content Design Albert Kavelar Senior Development Team Lead Engineering Abhi Kishore Junior Developer Engineering Alex Llewellyn Premier Support Engineer Support Andrew Lui Senior Technical Writer Content Design Andrea Malvetta Developer Engineering Andreas Marek Senior Developer Aliaksei Melnikau Senior Developer Engineering Anh Nguyen Senior Developer Engineering Andrea Olrich Developer Adam Petrovic Senior Development Team Lead Arslan Qamar Developer Engineering Alex Radu Senior Developer Alex Reardon Principal Developer Engineering Andres Sanz Rivas Engineering Manager Engineering Andrew Semple Senior Development Team Lead Engineering Artem Shubovych Developer Aimie Smith Product Marketing Team Lead Product Marketing Management Ashwin Srinivasan Principal Developer Anthony Starr Content Design Manager Content Design Andrew Swan Senior Developer Engineering Albert Wang Developer Alex Wei Senior Developer Artur Yapparov Developer Brenden Bain Principal Developer Engineering Brad Baker Architect Bejoy Jaison Support Engineer Sydney Support Ben Kelley Senior Developer Bing Liu Software Engineer Engineering Benjamin Magro Senior Product Manager Product Management Brian Nguyen Principal Developer Bartosz Ornatowski Senior Software Engineer Engineering Bradley Schoone Developer Bas Uytterhoeven-Spark Senior Developer Christine Burwinkle Head of Cops Content Design Clement Capiaux Senior Development Team Lead Chris Fuller Principal Developer Engineering Carlos Khatchikian Senior Development Team Lead Christopher Mann Senior Developer Charlie Marriott Senior Product Manager Product Management Chris Morgan Developer Chris Morgan Engineering Manager Engineering Christopher Nortje Senior Development Team Lead Engineering Craig Shannon Principal Engineer Engineering Chao Zeng Senior Developer Daniel Annesley Developer Delan Azabani Junior Developer David Black Senior Security Engineer Dominic Brodowski Senior Software Engineer Engineering David Currie Developer Djani Derviskadic Developer Daniel Franz Group Product Manager Product Management Daniel Kerris Senior Designer Design David Mason Developer Sydney Support Dave Norton Senior Support Engineer Standard Support Dean Pisani Developer Daniel Reissenberger Senior Software Engineer Engineering David Taylor Senior Developer David Ung Senior Application Support Engineer Standard Support Divyanshi Vashist Associate Product Manager Engineering Daniel Watania Support Engineer Sydney Support Erwan Alliaume Engineering Manager Engineering Eric Dalgliesh Senior Developer Engineering Etan Foo Software Engineer Intern Engineering Emiliano Sala Senior Developer Engineering Elton Santos Principal Engineer Engineering Eduardo Murai Soares Senior Developer Eric Sukmajaya Senior Full Stack Engineer Engineering Edward Zhang Senior Development Team Lead Frederik Happel Site Reliability Engineer Francis Rangel Senior Developer Felipe Reis Developer Graham Carrick Development Senior Manager Development Management Geoff Crain Senior Engineering Team Lead Gary Evesson Principal Developer Geoff Jacobs Operations Engineer Workplace Technology Gregory Joseph Senior Development Team Lead Garima Katyal Senior Engineering Manager Engineering Gatlee Kaw Software Engineer Engineering Guillaume Pitot Developer Engineering Guido Rota Principal Developer Graeme Smith Development Manager Gerry Tan Developer Giang Vo Senior Developer Gareth Williams Senior Developer Engineering Herman Chow Senior Developer Hamish Farrant Developer Hannes Obweger Development Manager Engineering Hanh Pho Senior Developer Henry Su Developer Dick Wiggers Developer Engineering Ivo Bosticky Senior Developer Engineering Ilia Sadykov Senior Developer James French Engineering Manager Engineering Josh Cameron Senior Developer Engineering Jonathon Creenaune Head of PaaS Jeroen De Raedt Senior Developer Johannes Els Senior Developer Engineering Jeremy Evans Senior Developer Xavi Ferró Senior Development Team Lead Engineering Jonathon Geeves Senior Developer Jamie Georgeson Senior Developer Engineering Joshua Hansen Senior Developer Jun Kim Software Engineer Engineering Justin Koke Development Manager Jimmy Kurniawan Senior Developer James Russell Senior Developer Engineering Jay Sethi Senior Engineering Manager Engineering Jason Sheehy Senior Developer Engineering Julia Simon Senior Developer Engineering Jason Thai Developer Joseph Walton Senior Development Team Lead James Winters Principal Developer Jason Wong Developer Product Management Sam Xu Developer Engineering Karen Bywater Senior Information Experience Writer Content Design Konrad Cichocki Senior Developer Keith Ford Senior Quality Engineer Kara Hatherly Senior Developer Kun Huang Engineering Manager Engineering Kunal Kanojia Principal Developer Engineering Kevin Ma Senior Software Engineer Engineering Kyle Nordbo Android Developer Klaus Paiva Senior Developer Engineering Khoa Pham Senior Developer Engineering Kiran Shekhar Developer Quality Engineering Leo Balan Senior Product Manager Lenard Bernardo Developer Engineering Luke Durkan Developer Engineering Luke Esther Senior Developer Engineering Lachlan Goodhew-Cook Senior Developer Leonard Osang Senior Developer Maciej Adamczak Senior Developer Michael Andreacchio Senior Service Enablement Engineer Sydney Support Michael Belton Developer Engineering Marc Senior Quality Engineer Engineering Matthew Dyer Developer Mauro Badii Site Reliability Engineer Sydney Support Marcio Ghiraldelli Senior Quality Engineer Quality Engineering Manish Goyal Senior Developer Matt Harrison Senior Developer Engineering Minh Ho Developer Engineering Matthew Hunter Service Enablement Manager Sydney Support Michael Drew Developer Michael Ruflin Architect Martin Jopson Senior Product Manager Product Management Michael Kemp Software Engineer Engineering Mendel Liang Intern Developer Engineering Martin Ma Principal Software Engineer Engineering Martin Meinhold Senior Developer Michelle Mortimer Lead Content Designer Content Design Mike Ni Senior Product Manager Product Management Melissa Paisley Developer Sydney Support Marek Pazik Senior Developer Engineering Matt Ponsford Senior Development Team Lead Engineering Matt Quail Engineering Lead Architect Architecture Matthew Robertson Senior Developer Engineering Martin Rubinsztein Senior Developer Mina Samy Developer Martin Suntinger Head of Product Strategy Product Management Monai Thangsuphanich Software Engineer Engineering Michael Tokar Senior Development Team Lead Development Management Mingyi Yang Senior Software Engineer Engineering Michelle Zeng Developer Engineering Michalina Ziemba Content Design Manager Content Design Norman Atashbar Senior Developer Nick Clarke Senior Development Team Lead Nafis Faramarzi Developer Engineering Nick Mason Senior Developer Sydney Support Ned Pummeroy Developer Nara So Developer Nhat Tran Senior Developer Engineering Nipuna Weerasinghe Software Engineer Engineering Olivier Dubois Developer Engineering Otto Ruettinger Head of Product Management Product Management Peter Gleeson Developer Peter Grasevski Developer Paul Greig Support Engineer Sydney Support Peggy Kuo Senior Developer Peter Leschev Development Manager Patrick Mafi Quality Engineer Quality Engineering Peter Obara Senior Quality Engineering Team Lead Quality Engineering Peter Plewa Principal Developer Peter Scobie R&D Program Manager Engineering Patrick Teen Senior Developer Engineering Penny Wyatt Senior Engineering Manager Quality Engineering Rob Chatfield Developer Engineering Rhys Christian Product Manager Special Ops Rutger Coolen Group Product Manager Product Management Richard Cordova Senior Developer Engineering Reuben D'Netto Senior Developer Richard Friend Senior Developer Robbie Gates Senior Architect Roger Lo Developer Robert Massaioli Senior Engineering Team Lead Ruvi Pitiyarachchi Designer Customer Experience Ruslan Prakapchuk Senior Developer Engineering Becc Roach Senior Designer Design Rachel Robins Lead Content Designer Content Design Renat Sabitov Senior Development Team Lead Rob Saunders Senior Product Manager Product Management Roman Tekhov Senior Development Team Lead Shova Acharya Software Engineer Engineering Sinan Aumarah Senior Software Engineer Engineering Shafqat Bhuiyan Senior Developer Engineering Sergio Cinos Rubio Principal Developer Engineering Sean Curtis Senior Developer Simone Houghton Program Management Manager Special Ops Sunny Kalsi Senior Developer Sanjay Kumar Senior Developer Engineering Sven Laanela Senior Team Lead Soney Mathew Senior Developer Sergey Meshkov Senior Developer Engineering Satej Mirpagar Senior Quality Engineer Engineering Sam Nazha Senior Developer Engineering Sam Omidi Support Engineer Sydney Support Sergey Oslopov Senior Support Engineer Standard Support Seam Mee Tan Support Engineer Sydney Support Symphony Wong Developer Thomas Barthelemy Senior Team Lead Engineering Thomas Bowes Intern Developer Engineering Timothy Cerexhe Senior Developer Engineering Thomas Davies Senior Developer Tripta Kaur Software Engineer Engineering Tim Sebastian Senior Javascript Developer Veenu Bharara Quality Principal Vicky Kharisma Principal Technical Support Kuala Lumpur Support Vedran Lunic Developer Engineering Vidhu Sharma Senior Product Manager Product Management Victoria Skalrud Senior Developer Vu Truong Developer Wolfgang Kritzinger Senior Developer Engineering Warren Thompson Content Design Manager Content Design Will Yasvoin Senior Developer Chandler Zhang Senior Developer Yann Kechichian Senior Software Engineer Engineering Yunyao Yao Developer Engineering Yufei Zuo Intern Developer Engineering Amsterdam Alex Conde Support Engineer Amsterdam Support Arbi Dridi Premier Support Engineer Premier Support Arnaud Errede Premier Support Manager Premier Support Adam Hynes Senior Developer Andrey Patyuchenko Premier Support Engineer Premier Support Andriy Yakovlev Principal Service Enablement Engineer SET Bastiaan Jansen Technical Support Manager Amsterdam Support David Di Blasio Premier Support Engineer Austin Support Dora Wierzbicka Support Engineer Amsterdam Support Julien Rey Senior Support Engineer Standard Support Kurt Eroglu Senior Developer Engineering Michael Heemskerk Architect Engineering Magnus Karlsson Premier Support Engineer Technical Support Enterprise - EMEA Matej Konecny Senior Developer Engineering Miranda Rawson Support Engineer Amsterdam Support Peter Koczan Solutions Engineer Amsterdam Support Ruchi Tandon Senior Support Engineer Amsterdam Support Shannon Spaniol Community Support Engineer Amsterdam Support Theodore Tzidamis Support Engineer Amsterdam Support Yilin Mo Premier Support Engineer Amsterdam Support Gdansk Adrian Bienias Developer Engineering Oleksiy Chystoprudov Senior Developer Engineering Adrianna Musialik Junior Developer Engineering Artur Falborski Developer Engineering Artur Faruga Developer Engineering Artur Gniadzik Senior Developer Engineering Adam Jakubowski Development Manager Engineering Anna Koronowicz-Makulec UX Designer Design Andrzej Kotas Product Manager Product Management Agata Kowal Developer Engineering Antoni Kowalski Developer Engineering Aleksander Mierzwicki Principal Site Reliability Engineer Engineering Aditya Parab Developer Engineering Artur Pawelczyk Developer Engineering Andrzej Poniatowski Senior Product Designer Design Ania Przybycień Developer Engineering Andrey Safonov Junior Developer Engineering Anna Scisłowska Product Manager Product Management Andrzej Swędrzyński Senior Engineering Manager Engineering Bartlomiej Lewandowski Senior Developer Engineering Bartosz Szulc Senior Quality Engineer Quality Engineering Barbara Żuk Senior Product Analyst Engineering Chris "Daz" Darroch Principal Developer Engineering Celebi Murat Junior Developer Engineering Dmytro Borshchov Developer Engineering Daniel Dudziak Junior Developer Engineering Dominik Kapusta Senior Developer Engineering Damian Kędzierski Senior Developer Engineering Daria Misiowiec Developer Engineering Dawid Pura Developer Engineering Daniel Ramotowski Senior Developer Engineering Daniel Rauf Senior Developer Engineering Dariusz Szuksztul Principal Developer Engineering Dawid Wlizło Junior Developer Engineering Ewelina Fiedorowicz Junior Software Engineer Engineering Filip Nowak Senior Developer Engineering Gaurav Agarwal Developer Engineering Grażyna Kaszkur Product Manager Product Management Grzegorz Rowiński Developer Engineering Grzegorz Tańczyk Development Team Lead Engineering Hossein Amiriparian Developer Engineering Hanna Sazonava Junior Designer Design Imran Abdul Lathif UX Designer Design Ignat Alexeyenko Senior Development Team Lead Engineering Imran Parvez Senior Product Designer Design Eve Stankiewicz Senior Product Manager Product Management Ilya Zinoviev Senior Developer Engineering Jakub Cegiel Quality Engineer Engineering Jakub Kurcek Senior Product Manager Product Management Jakub Łaziński Senior Product Manager Product Management Jakub Reczycki Developer Engineering Katarzyna Balcerzak Quality Engineer Engineering Kamil Cichy Senior Developer Engineering Katarzyna Derenda Product Manager Product Management Krzysztof Dubanowicz Software Engineer Engineering Kamil Kaczmarczyk Senior Developer Engineering Krzysztof Kępiński Quality Engineer Engineering Krzysztof Kercz Senior Developer Engineering Kamil Kolonko Engineering Manager Engineering Karol Łopaciński Senior Developer Engineering Konrad Marszałek Senior Quality Engineer Engineering Konrad Plasota Junior Software Engineer Engineering Karol Skwierawski Junior Software Engineer Engineering Liubou Boltach Junior Software Engineer Engineering Łukasz Gosiewski Developer Engineering Leonid Vysochyn Development Team Lead Engineering Łukasz Włodarczyk Development Team Lead Engineering Marcin Barzyk Developer Engineering Mateusz Beczek Software Engineer Engineering Michał Błajet Developer Engineering Michał Pastewski Junior Developer Engineering Michał Ciesielski Developer Engineering Michał Gozdera Development Team Lead Engineering Michał Dyro Senior Developer Engineering Małgorzata Gulgowska-Kowalska Principal Product Manager Product Management Marcin Kempa Development Team Lead Engineering Michał Kujałowicz Development and Quality Engineering Manager Engineering Maciej Kwidziński Senior Developer Engineering Milena Lech Service Enablement Engineer Special Ops Mateusz Makowski Junior Developer Engineering Mateusz Marzęcki Development Team Lead Engineering Marcin Mąsiorski Developer Engineering Mateusz Miara Senior Technical Writer Content Design Magdalena Michalak Senior Technical Writer Content Design Mykola Mykhalov DevOps Engineer Engineering Maciej Nowakowski Senior Development Team Lead Engineering Marcin Oles Development Team Lead Engineering Michał Orzechowski Senior Developer Engineering Mateusz Ostaszewski Developer Engineering Marek Piwnicki Quality Engineering Team Lead Engineering Maciej Przepiora Developer Engineering Marek Radochoński Senior Product Manager Product Management Mikołaj Rydzewski Senior Developer Engineering Maciej Rzymski Principal Developer Engineering Marcin Sasinowski Developer Engineering Michal Sierzputowski Quality Engineer Engineering Maria Sobińska Content Designer Customer Experience Maciej Swinarski Principal Developer Engineering Marek Szczepański Developer Engineering Mateusz Szerszyński Senior Developer Maciej Szpyra Developer Engineering Mateusz Walas Developer Engineering Marcin Waleriańczyk Senior Software Engineer Engineering Michał Warkocz Quality Engineer Engineering Mateusz Witkowski Senior Developer Engineering Michał Wyrzykowski Senior Developer Engineering Michał Zieliński UX Designer Design Mikołaj Żyromski Senior Developer Engineering Nikolay Loboda Developer Engineering Natalia Wróblewska Senior Software Engineer Engineering Octavian Genes Senior Developer Engineering Oleksandr Tkachenko Principal Quality Engineer Quality Engineering Olga Springer Product Manager Product Management Przemysław Bruski Architect Engineering Paweł Bugalski Principal Developer Engineering Paweł Cegła Developer Engineering Paweł Cieszko Engineering Manager Engineering Przemysław Czuj Developer Engineering Paweł Drygaś Junior Developer Engineering Piotr Juszczyński Senior Developer Engineering Patryk Latkowski Junior Software Engineer Engineering Paweł Lipiński Developer Engineering Piotr Masarczyk Junior Software Engineer Engineering Paweł Mikołajczuk Senior Developer Engineering Patryk Petrowski Senior Developer Engineering Paweł Przytarski Developer Engineering Pawel Skierczynski Development Team Lead Piotr Suwała Developer Engineering Piotr Święcicki Development Manager Engineering Paweł Wodkowski Senior Designer Design Rafał Hawrylak Principal Developer Engineering Rafał Jóźwiak Program Manager Engineering Roman Kolosovskiy Senior Product Manager Product Management Szymon Korytnicki Developer Engineering Syed Masood Senior Product Manager Product Management Sebastian Miałkowski Site Reliability Engineer Sylwia Mikołajczuk Program Manager Engineering Stanislav Natkovskyi Developer Engineering Sebastian Pawlak Senior Developer Engineering Simone Russo Developer Shushan Ulubabyan Senior Developer Engineering Seth Utecht Senior Developer Engineering Steve Watson Senior Developer Engineering Sławomir Zaraziński Developer Engineering Tomasz Bartyzel Senior Writer Content Design Tilwin Joy Developer Engineering Tomasz Kanafa Senior Developer Engineering Tomasz Majcher Quality Engineer Engineering Tomasz Pacuszka Developer Engineering Tomasz Zwierzchowski Senior Developer Engineering Wojciech Seliga Gdansk Office GM Development Management Zhenis Beisekov Product Manager Product Management San Francisco Ben Woskow Development Manager Turner Benard Support Engineer San Francisco Support Cameron Deatsch Head of Server Development Management Caspar Krieger Senior Development Team Lead David Chan Premier Support Engineer San Francisco Support Gary Sackett Technical Support Team Lead San Francisco Support Ian Dick Developer Engineering Ivan Tse Premier Support Engineer San Francisco Support Jake Brereton Group Product Marketing Manager Product Marketing Management Justin Burke Support Engineer San Francisco Support Jeff Curry Premier Support Engineer San Francisco Support Junie Dinda Head of Server PMM Product Marketing Management John Garcia Support Engineer San Francisco Support James Giles Support Engineer San Francisco Support Jordan Robison Support Engineer San Francisco Support Jason Worley Support Engineer San Francisco Support Kayne Barclay Engineering Lead Kyler Johnson Support Engineer San Francisco Support Kevin Liou Premier Support Engineer San Francisco Support Mary Avalos Support Engineer San Francisco Support Michael Thai Support Engineer San Francisco Support Michael Ventnor Senior Developer Osman Afridi Support Engineer San Francisco Support Pelle Kirkeby Support Engineer San Francisco Support Thomas Garske Support Engineer San Francisco Support Kuala Lumpur Ala Al-Shargabi Support Engineer Kuala Lumpur Support Amirul Bin Omar Application Support Engineer Standard Support Anna Monica Cardino Support Engineer Kuala Lumpur Support Ahmad Danial Mohammad Support Engineer Kuala Lumpur Support Ahmad Faisal Support Engineer Kuala Lumpur Support Azwandi Mohd Aris Support Engineer Kuala Lumpur Support Chung Park Chan Senior Support Engineer Sydney Support John Chin Kim Loong Support Engineer Kuala Lumpur Support Daryl Chuah Support Engineer Kuala Lumpur Support Daniel Leng Support Engineer Kuala Lumpur Support Immanuel Siagian Support Engineer Kuala Lumpur Support Janet Albion Senior Support Engineer Kuala Lumpur Support Julian Aidil Rahmadiputra Support Engineer Kuala Lumpur Support Joe Wai Tye Support Engineer Kuala Lumpur Support Kumar Ramajillu Support Engineer Kuala Lumpur Support Mohamed Hazwan Ariffin Support Engineer Sydney Support Muhammad Fahd Senior Cloud Support Engineer Kuala Lumpur Support Mogavenasan Muthusamy Support Engineer Standard Support Richie Gee Senior Support Engineer Kuala Lumpur Support Razaq Omar Support Engineer Kuala Lumpur Support Taiwo Akindele Senior Support Engineer Kuala Lumpur Support Tzu Hau Chai Application Support Engineer Standard Support Andy Nguyen Support Engineer Kuala Lumpur Support Gan Voon Kiat Support Team Lead Kuala Lumpur Support Vicknesh Shanmugam Application Support Engineer Standard Support Yew Teck En Technical Support Team Lead Kuala Lumpur Support Zulfadli Noor Sazali Premier Support Engineer Kuala Lumpur Support Remote Anna Pluskota Senior Quality Engineer Engineering Blake Haswell Senior Developer Ben Morgan Senior Developer Engineering Dominik Franke Senior Developer Daria Shatsylo Content Designer Content Design James Hazelwood Senior Developer Jacek Krawczyk Content Designer Content Design Jakub Rapsiewicz Software Engineer Intern Engineering Kamil Bar Developer Engineering Lukas Maczejka Developer Engineering Matt Cochrane Software Engineer Engineering Mikołaj Grząślewicz Senior Software Engineer Engineering Marty Henderson Senior Engineering Manager Development Management Maria Mikołajczak Software Engineer Engineering Michael Minns Senior Developer Engineering Martin Sturm Developer Engineering Nick Turskyi Software Engineer Engineering Oksana Levchuk Content Designer Content Design Paul Glantschnig Developer Engineering Piotr Kopecki Software Engineer Intern Engineering Patryk Oleksyk Senior Quality Engineer Engineering Robert Klimkiewicz Content Designer Content Design Raphael Riegger Design Manager Design Robert Smart Senior Developer Szymon Rachański Developer Engineering Tim Cinel Senior Developer Timur Omelchenko Developer Engineering Taj Palchaudhuri Senior Product Designer Design Tomasz Prus Experience Design Manager Design Valeryia Shymko Product Designer Design Elsewhere Anu Bharadwaj Head of Product Management Product Management Andrew Bui Software Engineer Engineering Anne Calantog Developer Aryan Chaubal Software Engineer Engineering Arkadiusz Glowacki Developer Engineering Arthur Goncalves Support Engineer Standard Support Anoop Ashok Goudar Software Engineer Engineering Amro Hassan Andrew Heinzer Community Support Engineer Austin Support Adam Horvath Askar Kalykov Andrew McKay Design Design Aleksey Miroshnik Developer Engineering Amisha Software Engineer Engineering Andreas Knecht Developer Engineering Anna Molly Design Design Alexey Petrushin Phan Thuc Anh Dev Manager Development Management Andre Quadros Petry Support Engineer Brazil Support Alex Rantos Developer Engineering Ashwini Rattihalli Principal Developer Arun S Software Engineer 2 Engineering Aleksei Verkholantcev Bradley Ayers Developer Engineering Brian Cruz Support Engineer Austin Support Bartek Gatz Product Manager Product Management Brandon Ibbotson Developer Engineering Bryce Johnson Bhargavi Kalari Support Manager Austin Support Brydie McCoy Developer Engineering Benito Picarelli Support Engineer Brazil Support Bryan Rollins General Manager Special Ops Bruno Rosa Support Engineer Brazil Support Balaji Srinivasan Senior Software Engineer Engineering Benjamin Suess Senior Software Engineer Engineering Ben Wirtz Product Manager Product Management Christopher Bowles Senior Software Engineer Engineering Chris Carter Quantitative User Researcher - Surveys Voice of the Customer Chris Doble Developer Engineering Cameron Fletcher Senior Developer Clarissa Gauterio Support Engineer Brazil Support Chau Huynh Chris Mountford Claudia Tu Chris Van Es Developer Engineering Clinton Volzke Danilo Conrad Premier Support Manager Brazil Support David Elkan Deeksha Singh Dean Hudson Design Design Dariusz Kordonski David Maye Premier Support Engineer San Francisco Support Darren McGarry Developer Engineering Dave Meyer Principal Product Manager Product Management Danielle Moore Quality Engineer Quality Engineering Duong Nguyen David Nicholson Site Reliability Engineer San Francisco Support David Piper Deyves Senger Support Engineer Standard Support David Tang Principal Developer Engineering Trinh Ngoc Diep Denise Unterwurzacher Senior Operations Engineer Eli Bishop Eric Franklin Support Engineer Austin Support Eric Kieling Regional Manager Brazil Support Earl McCutcheon Community Support Engineer San Francisco Support Edith Tom Engineering Manager Felix Haehnel Member of Technical Staff Felipe Prusch Support Engineer Standard Support Filip Rogaczewski Developer Engineering Felix Schmitz Felipe van Schaik Willig Support Engineer Brazil Support Geoffrey Wong Henrique Bittencourt Support Engineer Standard Support Henry Iguaro Hai Nguyen Developer Engineering Le Hoang Van Developer Engineering Phan Van Hoa Hoa Le Harshdeep Sinha Senior Software Engineer Engineering Nguyen Hung Developer Engineering Ivan Bruzgin Developer Engineering Ian Grunert Member of Technical Staff Ivan Lay Support Engineer Standard Support Ivan Maduro Site Reliability Engineer Bitbucket Cloud Ian Gil Ragudo Senior Developer Javier Aguilar Support Engineer Austin Support Jim Alexander Software Engineer Engineering Joshua Ali Jaiden Ashmore IT Senior Developer Engineering Ramiro Castro Support Engineer Austin Support Jerome Cordiez Design Design Jorge Dias Support Engineer Brazil Support James Hatherly Julius Hocman Jimmy Huang Jacek Jaroczynski Developer Engineering Jimmy Luong IT Senior Developer Justus Pendleton Jose Romero Senior Support Engineer Austin Support Jaime Sanchez Developer Engineering Jeremy Sanchez Support Engineer Standard Support Justin Vela Support Engineer Austin Support Krzysztof Barszcz Kellie Egan HR Business Partner Special Ops Kerrod Williams Product Manager Product Management Kathryn Grier Support Engineer Austin Support Keri Duthie Support Engineer Austin Support "Krzysztof Krysiak" "Software Engineer" "Engineering" Krzysztof Piwowar Design Design Laura Daly Product Marketing Product Marketing Management Luciano Fagundes Support Engineer Brazil Support Liam Flanagan Senior Software Engineer Engineering Liam Greig Design Manager Design Leonid Kyrpychenko Lucas Lima Support Engineer Brazil Support Lauren McHugh Luis Miranda Lukasz Pater Luiz Silva Senior Developer Marcus Silveira Senior Support Engineer Brazil Support Marek Broda Minh Do Michael Elias Developer Engineering Mathew Fenech Developer Engineering Matheus Fernandes Technical Support Team Lead Brazil Support Marco Garcia Support Engineer Austin Support Michael James Mauricio Karas Support Engineer Standard Support Morgan Knicely CSS Solutions Engineer Austin Support Mark Lassau Architecture Architecture Marty Lavender Support Engineer Austin Support Remus Mate Developer Engineering Matthew McMahon Mai Nakagawa Maggie Olsen Support Team Lead Standard Support Maciej Opala Developer Engineering Matthew Palmer Developer Engineering Mike Sharp Design Engineer Engineering Min'an Tan Michal Zeglarski Neha Bhayana Senior Product Manager Product Management Nguyen Nguyen Developer Engineering Nick Menere Head of Development Special Ops Nikolay Petrov Oswaldo Hernandez Developer Engineering Oleg Kovalov Developer Engineering Piotr Ackermann Paulo Hennig Senior Support Engineer Standard Support Przemyslaw Bielicki Przemyslaw Borkowski Developer Engineering Pedro Cora Premier Support Engineer Brazil Support Paulwyn Devasundaram Developer Engineering Pawel Farid Dev Manager Development Management Petterson Goncalves Community Support Engineer Community Support Priyanka Jiandani Software Engineer 2 Engineering Piotr Klimkowski Developer Engineering Paul McLoughlin Developer Engineering Paweł Niewiadomski Peter Runge Developer Engineering Puneet Saini Senior Software Engineer Engineering Pietro Schaff Support Engineer Brazil Support Petro Semeniuk Piyush Sonagara Senior Software Engineer Engineering Pedro Souza Support Engineer Brazil Support Piotr Stefaniak Developer Engineering Rory Armstrong Developer Engineering Rick Bal Premier Support Manager San Francisco Support Ricardo Carracedo Support Engineer Brazil Support Rodrigo Esteves Support Intern Standard Support Rachel Fuerst Support Engineer Austin Support Russ Gould Support Engineer Austin Support Rosie Jameson Technical Writer Content Design Roy Krishna Operations Manager Special Ops Rafael Parmigiani Senior Support Engineer Standard Support Rostislav Pasechnikov Software Engineer Engineering Rajshri Pendekar Senior Software Engineer Engineering Raghavendren Ramakrishnan Quality Engineer Quality Engineering Rodrigo Rosa Support Engineer Standard Support Rupert Shuttleworth Samuel Le Berrigaud Sheri Atienza Product Marketing Product Marketing Management Stuart Bargon Scott Christopher Senior Support Engineer Austin Support Shawn Cranford Support Engineer Austin Support Stanislav Dvorscak Slawek Ginter Architecture Architecture Slawomir Ginter Developer Engineering Steve Haffenden Developer Engineering Scott Harwood Scott Hughes Shreyans Jain Software Engineer Engineering Simeon Malchev Sarah Moloney Design Design Sripathi Pai Quality Engineer Quality Engineering Swaraj Pal Senior Software Engineer Engineering Sidney Shek Architect Tang Son Hai Ngoc Developer Engineering Sergey Zaporozhtsev Trevor Campbell Developer Engineering Tiago Kolling Comasseto Support Engineer Brazil Support Tim Evans Premier Support Engineer Austin Support Tanu Garg Senior Software Engineer Engineering Nguyen Thanh Dinh Developer Engineering Bui Duy Thanh Developer Engineering Tapan Pareek Software Engineer 2 Engineering Tian Pu Developer Engineering Tomek Sroka Principal Developer Engineering Justin Nguyen Developer Engineering Vladimir Vinogradov William Mock Head of CSS Enterprise Austin Support Wojciech Urbanski Developer Engineering Wesley Walser Zehua Liu → 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://www.tumblr.com/support?language=ru_RU | Центр справки | Tumblr Войти Зарегистрироваться © Tumblr, Inc. Справка О Tumblr Приложения Разработчикам Темы Вакансии Юридические сведения Условия Авторское право Конфиденциальность 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:33 |
https://www.atlassian.com/ja/software/jira/templates/marketing | マーケティング・テンプレート | Jira テンプレート・ライブラリ | Atlassian Close あなたの言語 でこのページを表示しますか？ すべての言語 言語を選択する 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 無料で入手する 機能 すべての機能 Jira の Rovo Back ソリューション チーム ユースケース 企業規模 チーム マーケティング エンジニアリング デザイン オペレーション IT ユースケース はじめに 計画 キャンペーン管理 アジャイルプロジェクト管理 プログラム管理 企業規模 Enterprise Back 製品ガイド テンプレート テンプレート すべてのテンプレート ソフトウェア開発 マーケティング デザイン 営業 オペレーション サービス管理 人事 法務 IT オペレーション ファイナンス Jira Service Management のテンプレート Back 価格 その他 + 表示を減らす - 無料で入手する Back 無料で入手する Jira テンプレート Open and close the navigation menu カテゴリー ソフトウェア開発 マーケティング デザイン 営業 オペレーション サービス管理 人事 法務 IT オペレーション ファイナンス プロジェクト管理テンプレート 無料で入手する カテゴリー ソフトウェア開発 マーケティング デザイン 営業 オペレーション サービス管理 人事 法務 IT オペレーション ファイナンス プロジェクト管理テンプレート マーケティング テンプレート Jira でインパクトのあるマーケティングを実現します。事前構築済みのカスタマイズ可能なマーケティング チーム向けテンプレートがあれば、簡単に始められます。 プロジェクト管理 ビジネス プロジェクトを完了するアクティビティを管理します。 コンテンツ管理 優先順位付けから配信までのコンテンツ ライフサイクルを管理します。 キャンペーン管理 発案から実行まで、マーケティング キャンペーンの進行を促進します。 市場開拓 市場投入を調整します。 マーケティング サービス管理 すべてのマーケティング リクエストの管理と追跡 メール キャンペーン 下書きからローンチまで、メール キャンペーンを計画して実行します マーケティング・リソース マーケティング・チーム向け Jira マーケティング チームのアジリティを高めます。Jira がどのように作業を効率化するか、さらに詳しくご覧ください。 詳細を見る プロジェクトを自動化する 重要な業務に集中して、他は自動化に任せましょう。チームのカスタム・ルールを作成したり、事前作成済みの自動化を使用してすぐに開始したりできます。 自動化について詳しく見る お気に入りのツールに接続 500 以上の統合を活用してシームレスに作業を進め、3000 以上の他の拡張機能を活用してチームの最適なプロセスを作成しましょう。 アプリ・マーケットプレイスを詳しく見る 会社名 アトラシアンで働く イベント ブログ 投資家向け アトラシアン基金 プレスキット お問い合わせ 製品 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket すべての製品を見る リソース 技術サポート 購入とライセンス アトラシアン コミュニティ ナレッジ ベース Marketplace アカウント管理 サポートを依頼する 学ぶ パートナー トレーニングと認定 ドキュメント 開発者向けリソース エンタープライズ サービス 全リソースを見る Copyright © 2025 Atlassian プライバシーポリシー 利用規約 サイト管理者情報 言語の選択 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:33 |
https://www.atlassian.com/es/software/jira/guides/issues/tutorials | Tutoriales sobre incidencias 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 de actividades de Jira Crear una actividad Selecciona "Crear" en la barra de navegación superior. Tu actividad se mostrará en el backlog o en el tablero del proyecto. Encontrar una actividad Realiza una búsqueda global y encuentra una actividad en todo el sitio La barra de búsqueda en la barra de navegación superior te permite buscar rápidamente actividades en toda la instancia mediante el ID de la actividad o palabras clave. Puedes delimitar la búsqueda por proyecto, persona asignada o estado. Realiza una búsqueda contextual y encuentra una actividad en la vista del tablero, la hoja de ruta o el backlog del proyecto Las barras de búsqueda se encuentran en la vista de la hoja de ruta, el backlog y el tablero. Las actividades aparecerán en los resultados de búsqueda si se encuentran en esa vista en particular. Encuentra una actividad en un proyecto determinado a través del navegador de actividades Ve a "Actividades" en la barra lateral de navegación. Alterna entre los modos "Básico" o "JQL" en la parte superior derecha de la pantalla. En el modo básico, puedes escribir palabras clave en la barra de búsqueda o utilizar los menús desplegables para filtrar las actividades por proyecto, tipo de actividad, estado, persona asignada y cualquier campo que pueda tener una actividad. En el modo JQL, puedes generar consultas estructuradas con Jira Query Language (JQL) para buscar actividades. Ten en cuenta que el navegador de actividades no está disponible de forma predeterminada en los proyectos gestionados por el equipo. Habilita esta función en Configuración del proyecto > Funciones > Navegador de actividades . Añadir un tipo de actividad a un proyecto En proyectos gestionados por el equipo: Selecciona "Configuración del proyecto" en la barra de navegación lateral de la izquierda, luego selecciona "Tipos de actividad" y, a continuación, pulsa "+ Añadir tipo de actividad". Arrastra y suelta los tipos de campos que te gustaría tener en el tipo de actividad y ponle un nombre a cada uno. Si quieres, también puedes establecer los valores predeterminados en cada campo. En proyectos gestionados por la empresa: Cómo vincular actividades Abre una actividad. Selecciona Vincular actividad en la parte superior de la ventana de la actividad. Elige el tipo de enlace de elemento de actividad (por ejemplo: "esta actividad está bloqueada por..."). Especifica las actividades que quieras vincular escribiendo la clave de actividad completa (por ejemplo: ABC-123). Selecciona Link (Vincular). Configurar el diseño de una actividad Selecciona cualquier actividad de tu tablero. En la parte inferior derecha de la vista de la actividad, selecciona Configurar . Arrastra y suelta los campos de la actividad en las regiones correspondientes. 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:33 |
https://www.ecns.cn/video/2026-01-07/detail-iheyrzrv3836956.shtml | Insights | Sanae Takaichi's erroneous remarks a grave 'diplomatic failure': Japanese scholar --> 中文 Home News Ecns Wire Business Travel Photo Video Voices RIGHT BG LINE Text: A A A Print Video Insights | Sanae Takaichi's erroneous remarks a grave 'diplomatic failure': Japanese scholar 2026-01-07 10:13:35 Ecns.cn Editor : Meng Xiangjun ECNS App Download Japanese Prime Minister Sanae Takaichi’s remarks on Taiwan violate both international protocol and diplomatic norms, said Atsushi Koketsu, professor emeritus at Yamaguchi University, recently. Koketsu called it a grave “diplomatic failure.” He noted that Takaichi’s statements fundamentally contradict Japan’s identity as a peace-loving nation governed by its pacifist constitution. The professor expressed deep disappointment, emphasizing that Takaichi’s stance is undermining the Sino-Japanese relationship. More Photo 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 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 Most popular in 24h More Top news No country should act as the world's police or judge: Chinese FM Insights | Sanae Takaichi's erroneous remarks a grave 'diplomatic failure': Japanese scholar Chinese researchers achieve storm forecasting 4 hours in advance China achieves breakthrough in hydrogen sulfide treatment UN members denounce U.S. attack More Video 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 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://gitstar-ranking.com/github | github - Gitstar Ranking Gitstar Ranking Users Organizations Repositories Rankings Users Organizations Repositories Sign in with GitHub github Star 592305 Rank 10 Go to GitHub Fetched on 2026/01/09 03:07 530 Repositories gitignore 171678 spec-kit 61050 github-mcp-server 25738 copilot-docs 23264 docs 18687 awesome-copilot 16551 opensource.guide 15127 gh-ost 13134 copilot.vim 11196 codeql 9109 semantic 9057 roadmap 8541 scientist 7647 personal-website 7586 copilot-cli 6402 markup 6004 dmca 5893 CopilotForXcode 5490 training-kit 4802 swift-style-guide 4779 explore 4637 gemoji 4496 choosealicense.com 4016 mona-sans 3966 git-sizer 3952 relative-time-element 3922 hubot-scripts 3603 hotkey 3293 secure_headers 3277 scripts-to-rule-them-all 3259 gov-takedowns 3151 archive-program 3095 github-elements 2890 janky 2745 haikus-for-codespaces 2513 VisualStudio 2467 renaming 2451 glb-director 2420 CodeSearchNet 2404 SoftU2F 2236 balanced-employee-ip-agreement 2196 accessibilityjs 2171 advisory-database 2095 platform-samples 2090 site-policy 2004 hubot-sans 1926 government.github.com 1901 github-services 1892 pages-gem 1870 india 1805 1 2 3 4 5 … › Released by @k0kubun in December 2014. Fork me on GitHub . | 2026-01-13T09:29:33 |
https://www.chinadaily.com.cn/world/special_coverage/68f1f858a310f735438b59d3 | Beijing in Eyes of Foreign Reporters - Chinadaily.com.cn Search HOME CHINA WORLD BUSINESS LIFESTYLE CULTURE TRAVEL VIDEO SPORTS OPINION REGIONAL NEWSPAPER MOBILE Global Edition ASIA 中文 双语 Français HOME CHINA WORLD BUSINESS LIFESTYLE CULTURE TRAVEL VIDEO SPORTS OPINION REGIONAL NEWSPAPER China Daily PDF China Daily E-paper MOBILE World Asia-Pacific Americas Europe Middle East Africa China-US China-Europe China-Japan China-Africa Home World / Beijing in Eyes of Foreign Reporters Home / World / Beijing in Eyes of Foreign Reporters 'Charming Beijing' TV Series overseas promotion event held in Oct 2025-10-31 17:47 1 1/1 Most Viewed in 24 Hours World in Focus Clean energy push Across Asia + Match online Himalayas warming 50 percent faster than global average: Study Special Coverage + 2025 A Date with China GMD SCO Summit Cities Tianjin Reporter's Journal + Shandong puts ancient philosophers into tourism draw A divergence of fates for two illustrious American newspapers Friends Afar + Blogger aims to bridge France, China links Ties That Bind + Vital pass to boost China-Pakistan trade Top BACK TO THE TOP English 中文 HOME CHINA WORLD BUSINESS LIFESTYLE CULTURE TRAVEL VIDEO SPORTS OPINION REGIONAL NEWSPAPER China Daily PDF China Daily E-paper MOBILE Copyright 1994 - . All rights reserved. The content (including but not limited to text, photo, multimedia information, etc) published in this site belongs to China Daily Information Co (CDIC). Without written authorization from CDIC, such content shall not be republished or used in any form. Note: Browsers with 1024*768 or higher resolution are suggested for this site. License for publishing multimedia online 0108263 Registration Number: 130349 About China Daily Advertise on Site Contact Us Job Offer Expat Employment FOLLOW US Copyright 1994 - . All rights reserved. The content (including but not limited to text, photo, multimedia information, etc) published in this site belongs to China Daily Information Co (CDIC). Without written authorization from CDIC, such content shall not be republished or used in any form. --> | 2026-01-13T09:29:33 |
http://shandong.chinadaily.com.cn/weifang/ | Weifang Advertorial Advertorial Home This is Weifang Overview Regions Media Center News In Focus Videos Photo Gallery Investment Biz Updates Why Weifang Industries Industrial Parks Enterprises Culture East Asian Cultural Hub Global Kite Capital Heritages Celebrities Travel Attractions Hotels Dining Intl Exchanges What’s On Friendship Cities Living Visas Education Healthcare Work Marriage Happy New Year Festive demand fuels boom for Weifang's traditional clay sculptures Weifang's sky dazzles as kite extravaganza unfurls China Opportunities Dynamic Weifang News December 12, 2025 Weifang targets trillion-yuan economy by 2028 Weifang city in Shandong province has set its sights on becoming a trillion-yuan ($141.6 billion) economy by 2028. January 06, 2026 Weifang crowns champion of Shandong's cuisine competition Read more December 29, 2025 Weifang Port breaks ground on 50,000-metric-ton deep-water channel Read more December 22, 2025 Weifang heats up winter economy with seasonal promotions Read more Videos An invitation to winter magic in Weifang Weifang: A rising magnet for inbound travel Weifang debuts smart-agriculture hub at Osaka Expo Weifang kite festival forges global bonds Weifang kite festival soars with global spirit In Focus Investment Biz Updates Weifang Port breaks ground on 50,000-metric-ton deep-water channel Weifang heats up winter economy with seasonal promotions Weifang targets trillion-yuan economy by 2028 Why Weifang Industries Weifang, a famous industrial city, has four industrial clusters each with output value of over 100 billion yuan, including power equipment, high-end chemicals, food processing and new-generation information technology. Enterprises Industrial Parks Weifang is home to dozens of national and provincial development zones, pilot areas and high-tech industrial development zones. Culture 2nd World Indoor Kite Championships takes flight in Weifang The 2nd World Indoor Kite Championship soared into action on Oct 18 at the gymnasium of Weifang University. --> --> Weifang kites soar at Las Vegas World Kite Festival December 15, 2025 Weifang showcases traditional handicrafts at Saudi Intl Handicrafts Week December 08, 2025 Stamped in history, alive in Weifang November 04, 2025 Travel Attractions Explore Weifang's breathtaking fall foliage As autumn deepens, Weifang transforms into a vibrant tapestry of reds and golds, making it the ideal time to explore the city's best spots for fall foliage. Hotels The Farrington Weifang The Farrington Weifang is a hotel furnished with 229 rooms and suites and more than 10 restaurants and lounges. Dining Weifang crowns champion of Shandong's cuisine competition Following a five-month journey across 16 cities, Weifang emerged as the winner in the "Shandong Cuisine Championship". Living Visas Education Healthcare Work Marriage BACK TO THE TOP Link Shandong, China This is Weifang Overview Regions Media Center News In Focus Videos Photo Gallery Investment Biz Updates Why Weifang Industries Industrial Parks Enterprises Culture East Asian Cultural Hub Global Kite Capital Heritages Celebrities Travel Attractions Hotels Dining Intl Exchanges What’s On Friendship Cities Living Visas Education Healthcare Work Marriage Copyright© The Information Office of Weifang Municipal People's Government. All rights reserved. Presented by China Daily. | 2026-01-13T09:29:33 |
https://cn.chinadaily.com.cn/a/202505/28/WS6836a7c5a310205377035619.html | 海外手记 - 中国日报网 China Daily Homepage 中文网首页 时评 资讯 C财经 生活 视频 专栏 双语 --> 原创 观天下 地方 --> 登录 注册 观天下 移动新媒体 站内搜索 站内搜索 观天下 China Daily Homepage 中文网首页 时评 资讯 C财经 生活 视频 专栏 双语 --> 漫画 原创 观天下 地方 海外手记 海外手记 海外手记 | 虞美人花，也为他们开 2 个月 前 海外手记 | 英语的burger是汉堡，德语的Bürger是什么？ 2 个月 前 海外手记丨以音乐架桥沟通中俄：从冼星海到左贞观 3 个月 前 海外手记丨莫斯科机场的中文标识缓解了我的“语言恐慌” 3 个月 前 海外手记丨探寻列宁在喀山的“青葱岁月” 4 个月 前 海外手记丨黄河之声回荡莫斯科——一场跨越时空的音乐缅怀 4 个月 前 海外手记丨舌尖上的榴莲，让中泰友谊常鲜 4 个月 前 海外手记 | 到现场去，到人民中去 ——英国记者乔治·何克给我的启示 4 个月 前 海外手记 | 钱秀玲这个名字，你听说过吗？ 4 个月 前 海外手记 | 英国国旗争夺战 4 个月 前 海外手记 | 黑比利时的诗人，成了比利时的宝 5 个月 前 海外手记 | 七姐妹岩：微信朋友圈里新兴的英伦打卡地 5 个月 前 海外手记 | 讲述，是最深的铭记 ——“里斯本丸”号纪念碑背后的故事 5 个月 前 海外手记 | 等了一百年，塞纳河开泳池了！ 5 个月 前 海外手记 | 论欧洲人为什么热死也不装空调 5 个月 前 1 2 3 4 5 6 7 8 9 10 Next >>| 1/13 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://www.offsec.com/events/the-gauntlet/ | The Gauntlet: Capture Flags, Climb Leaderboards, Win Big | OffSec Home Learn Individuals Teams Kali & Community Resources Pricing Please enable JavaScript. Toggle menu Enroll now Sign in Search Contact us Stay tuned for Season 2 The Gauntlet: Season 1, Echo Response has come to and end. OffSec will verify and finalize winners after the final challenge closes. Only valid submissions are eligible. Any attempts to cheat, manipulate results, or break the Event rules will result in immediate elimination from The Gauntlet and disqualification from prize eligibility. The Gauntlet Season 1 Echo Response Prize announcements Winners will be drawn on December 16, 2025 , and contacted via the email registered with OffSec within 7 days of being drawn. Prizes are non-transferable, non-exchangeable, and cannot be redeemed for cash, credit, or any other alternatives. $100,000 in exclusive prizes Anyone with a free OffSec account can register and take part. You do not need a subscription, prior certification, or purchase to participate or be eligible for prizes. "]}],[0,{"q":[0,"How does it work?"],"a":[0," Each week, a new scenario is released inside Proving Grounds, featuring a task-based machine with objectives to complete and flags to capture. You'll earn points for progress, with extra credit for speed and first PWN. All scores feed into a live leaderboard. The more scenarios you complete, the higher you climb. At the end of the event, top participants will win part of the $100,000 USD prize pool, while everyone earns bragging rights, digital badges, and a chance to make their mark. "]}],[0,{"q":[0,"What kind of prizes can I win?"],"a":[0,"\n\t\t\t Finish in the top 100 leaderboard? Great news, you'll win a prize! Here's a breakdown of exactly what you can win: \n\t\t\t OffSec Subscriptions \n\t\t\t \n\t\t\t\t \n\t\t\t\t\t Learn One : available for leaderboard positions 1-5.\n\t\t\t\t \n\t\t\t\t \n\t\t\t\t\t Course + Cert Exam Bundle : available for leaderboard positions 6-27.\n\t\t\t\t \n\t\t\t\t \n\t\t\t\t\t Proving Grounds Practice Annual Subscription : available for leaderboard positions 28-100.\n\t\t\t\t \n\t\t\t \n\t\t\t Limited-Edition Merch Boxes \n\t\t\t \n\t\t\t\t \n\t\t\t\t\t Tier 1: Ultimate Champion Pack, available for leaderboard positions 1-5.\n\t\t\t\t \n\t\t\t\t \n\t\t\t\t\t Tier 2: Legends Premium Pack, available for leaderboard positions 6-10.\n\t\t\t\t \n\t\t\t\t \n\t\t\t\t\t Tier 3: The Gauntlet Crate, available for leaderboard positions 11-50.\n\t\t\t\t \n\t\t\t \n\t\t\t OffSec Legends T-Shirts \n\t\t\t A limited-edition t-shirt branded with our exclusive OffSec Legends character(s). Available for leaderboard positions 51-100. \n\t\t"]}],[0,{"q":[0,"Do I need to complete each scenario on the day it drops?"],"a":[0," No, you can complete scenarios at your own pace. However, completing them sooner gives you a better shot at first PWN bonuses and leaderboard positioning. "]}],[0,{"q":[0,"How long will each scenario be available for?"],"a":[0," Each scenario stays open through the duration of the 8-week event. You'll have access to all unlocked scenarios once they drop, so you can catch up if needed. "]}],[0,{"q":[0,"Will I earn a certificate or credential?"],"a":[0," All participants who complete scenarios will receive a digital badge. Top performers may receive additional recognition, merch, or cert attempts. "]}],[0,{"q":[0,"I have more questions."],"a":[0," Please see the Proving Grounds: The Gauntlet article in our Help Center. "]}]]],"wide":[0,true],"class":[0,"astro-mvywp6gt"]}' ssr client="load" opts='{"name":"FAQList","value":true}' await-children> The Gauntlet FAQ Can anyone participate? How does it work? What kind of prizes can I win? Do I need to complete each scenario on the day it drops? How long will each scenario be available for? Will I earn a certificate or credential? I have more questions. The OffSec Legends The OffSec Legends, inspired by OffSec's world-renowned certifications, are powerful guides who lead you through The Gauntlet. They assign missions, share wisdom, and call on you to rise beside them to secure victory. Penetration Testing with Kali Linux The stealthiest can slip past the fiercest defenses, leaving no sign behind. Kali Evasion Techniques and Breaching Defenses The most cunning twist security, slipping through barriers and leaving chaos behind. ShadowGlyph Web Attacks with Kali Linux The most perceptive can slip through any defense, unnoticed and untouchable. NightHorn Advanced Web Attacks and Exploitation The cunning unravel webs, slipping through barriers with lethal grace. Widow Windows User Mode Exploit Development The slyest can bypass any barrier in this realm or others. Cipherflare Advanced Windows Exploitation The most relentless can sever any connection, striking without warning and leaving no trace behind. Nullgrim Security Operations and Defensive Analysis The most steadfast defend any stronghold with unwavering resolve. KnightWarden Foundational Threat Hunting The fastest can pierce through any defense, striking with lethal speed and leaving no trace behind. Hornet Tracer Foundational Incident Response The most commanding control the storm, eliminating threats with unmatched force. AnchorHelm The Gauntlet: Terms & Conditions Every great quest has fine print. Check out the rules before you storm The Gauntlet. Read Terms & Conditions Share Get the latest updates around resources, events & promotions from OffSec Submit By submitting this form, I agree to the processing of my personal data by OffSec as described in the Privacy Policy . Learn Products Courses + Certifications Proving Grounds Learning Paths Pricing For Organizations Cyber Ranges Industry Frameworks Pentesting Services Use Cases Industries OffSec About OffSec Careers Press Room Product Updates Help Center Community User Generated Content Bug Bounty Program Learner Stories Resources Blog Cyberversity Cybersecurity Job Roles Partners Public Sector Find a Partner Become a partner Partner Portal Login Feedback Legal Trust & Compliance RSS Feed © OffSec Services, LLC 2026 All rights reserved | 2026-01-13T09:29:33 |
https://www.atlassian.com/pl/software/jira/guides/issues/tutorials | Samouczki dotyczące zgłoszeń w Jira Software | Atlassian Close Czy wyświetlić tę stronę w Twoim języku ? Wszystkie języki Wybierz swój język 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Zacznij korzystać za darmo Funkcje Wszystkie funkcje Rovo w Jirze Back Rozwiązania Zespoły Przypadki użycia Rozmiar firmy Zespoły Marketing Inżynieria Projekt Eksploatacja IT Przypadki użycia Wprowadzenie Planowanie Zarządzanie kampanią Zwinne zarządzanie projektami Zarządzanie programem Rozmiar firmy Enterprise Back Przewodnik po produktach Szablony Szablony Wszystkie szablony Tworzenie oprogramowania Marketing Projekt Sprzedaż Eksploatacja Zarządzanie usługami HR Prawo Operacje IT Finanse Szablony w Jira Service Management Back Ceny Więcej + Mniej - Zacznij korzystać za darmo Back Zacznij korzystać za darmo Wprowadzenie Wprowadzenie do Jira System Jira dla zespołów 7 kroków, aby rozpocząć pracę w Jira Projekty Informacje ogólne Samouczki Zasoby Tablice Informacje ogólne Samouczki Zasoby Zgłoszenia Informacje ogólne Samouczki Zasoby Przepływy pracy Informacje ogólne Samouczki Zasoby Narzędzia Integracji Informacje ogólne Samouczki Zasoby Raporty i pulpity nawigacyjne Informacje ogólne Samouczki Zasoby Analizy Informacje ogólne Samouczki Zasoby Uprawnienia Informacje ogólne Samouczki Zasoby JQL Informacje ogólne Samouczki Ściągawka Zasoby Nawigacja Overview Tutorials Resources Automatyzacja Informacje ogólne Samouczki Zasoby Oś czasu Informacje ogólne Samouczki Zasoby Advanced Roadmaps Informacje ogólne Samouczki Zasoby Jira mobile Informacje ogólne Samouczki Zasoby Więcej informacji o systemie Jira Wersje systemu Jira Opcje hostingu Samouczki dotyczące zgłoszeń w Jirze Tworzenie zgłoszenia Wybierz „Utwórz” w górnym obszarze nawigacji. Twoje zgłoszenie pojawi się w backlogu lub na tablicy projektu. Znajdowanie zgłoszenia Wyszukiwanie globalne zgłoszenia w całej witrynie Pasek wyszukiwania w górnym obszarze nawigacyjnym umożliwia szybkie wyszukiwanie zgłoszeń w całej instancji za pomocą identyfikatora zgłoszenia lub słów kluczowych. Możesz zawęzić zakres wyszukiwania do konkretnego projektu, statusu i/lub konkretnej osoby przypisanej. Wyszukiwanie kontekstowe zgłoszenia w widoku tablicy, harmonogramu lub backlogu projektu Paski wyszukiwania można znaleźć w widoku harmonogramu, backlogu i tablicy. Zgłoszenia pojawią się w wynikach wyszukiwania, jeśli występują w konkretnym widoku. Znajdowanie zgłoszenia w danym projekcie za pomocą nawigatora zgłoszeń Przejdź do opcji „Zgłoszenia” na bocznym pasku nawigacji. Przełączaj się między trybami „Podstawowy” i „JQL” w prawym górnym rogu ekranu. W trybie podstawowym można wpisywać słowa kluczowe na pasku wyszukiwania i/lub korzystać z rozwijanych menu, aby filtrować zgłoszenia według projektu, typu zgłoszenia, statusu, osoby przypisanej i wszelkich pól, które mogą występować w zgłoszeniu. W trybie JQL można tworzyć uporządkowane zapytania w języku Jira Query Language (JQL) w celu wyszukiwania zgłoszeń. Uwaga: nawigator zgłoszeń jest domyślnie niedostępny w projektach zarządzanych przez zespół. Aby włączyć tę funkcję, wybierz kolejno opcje Ustawienia projektu > Funkcje > Nawigator zgłoszeń . Dodawanie typu zgłoszenia do projektu W projektach zarządzanych przez zespół: Wybierz opcję „Ustawienia projektu” na bocznym pasku nawigacji po lewej stronie, a następnie „Typy zgłoszeń” i naciśnij przycisk „+ Dodaj typ zgłoszenia”. Przeciągnij i upuść rodzaje pól, które chcesz uwzględnić w typie zgłoszenia, i nadaj nazwę każdemu rodzajowi pola. W razie potrzeby możesz także ustawić wartość domyślną dla każdego pola. W projektach zarządzanych przez firmę: Jak połączyć zgłoszenia Otwórz zgłoszenie. Wybierz opcję Połącz zgłoszenie u góry modalu zgłoszenia. Wybierz typ łącza do zgłoszenia (na przykład „to zgłoszenie jest zablokowane przez…”). Określ co najmniej jedno zgłoszenie, z którym chcesz utworzyć połączenie, wpisując pełny klucz zgłoszenia (na przykład ABC-123). Wybierz opcję Połącz . Konfiguracja układu zgłoszenia Wybierz z tablicy dowolne zgłoszenie. W prawym dolnym rogu widoku zgłoszenia wybierz opcję Konfiguruj . Przeciągnij i upuść pola zgłoszenia w odpowiednich miejscach. Firma Kariera Wydarzenia Blogi Relacje z inwestorami Fundacja Atlassian Materiały prasowe Skontaktuj się z nami produkty Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Zobacz wszystkie produkty Zasoby Pomoc techniczna Zakup licencji Atlassian Community Baza wiedzy Marketplace Moje konto Utwórz zgłoszenie do pomocy technicznej Poznawanie Partnerzy Szkolenia i certyfikaty Dokumentacja Zasoby dla programistów Usługi Enterprise Zobacz wszystkie zasoby Copyright © 2025 Atlassian Polityka prywatności Warunki Nota prawna Wybierz język Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:33 |
http://groovy-lang.org/syntax.html#_binary_literal | 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 |
http://shandong.chinadaily.com.cn/ | Shandong, China HOME ABOUT Overview Cities Photo Gallery Videos NEWS Latest Features Reports in PDF DEVELOPMENTS Transformed Development Drivers Rural Vitalization Marine Economy CULTURE What’s On Heritage Traditional Culture Celebrities INTL EXCHANGE Why Shandong Industrial parks Belt and Road Sister Cities BRANDS Strategies Companies TRAVEL Attractions Dining LIVING Visas Healthcare Transportation Education Marriage Useful Info 中文 btn-search btn-facebook btn-twitter Search Mask Embark on cozy winter tour in Shandong Mask This is Shandong Mask Traditions revive in Shandong Mask Shandong sees strong rise in foreign trade 1 2 3 4 prev next Visas Healthcare Transportation Marriage Education Useful Info NEWS Jinan charts course for 15th Five-Year Plan period 2026-01-13 The Ninth Plenary Session of the 12th Jinan Municipal Committee of the Communist Party of China was held from Dec 25 to 26. High-temperature geothermal resource discovered in Shandong 2026-01-13 A landmark high-temperature geothermal resource has been confirmed at a depth of 4,000 meters in Dongying. Shandong's first satellite launch of 2026 scheduled in Rizhao 2026-01-12 A Ceres-1S Y7 carrier rocket is scheduled to launch off the coast of Rizhao, Shandong, around Jan 16, and will be the city's first launch of 2026. Qingdao targets Southeast Asian tourists with direct flights 2026-01-12 Qingdao has stepped up efforts to attract inbound tourists from Southeast Asia and the Republic of Korea, as Chinese cities compete to capture the "Travel China" trend at the start of the year. FEATURES Mask Xi's Moments Mask Voice your opinions on China's 2026 Government Work Report DEVELOPMENTS Transformed Development Drivers Haiyang emerges as green energy powerhouse in northern China 2026-01-05 Rural Vitalization Shandong apple pickers find new fame as influencers 2026-01-04 Marine Economy Qingdao Port pushes intelligence deployment 2026-01-08 CULTURE What's on 'Drama bus' in Jinan transforms city into immersive stage 2026-01-07 Heritage Shandong Museum unveils exhibition on Dongyi culture 2026-01-09 Traditional Culture Caoxian hanfu blends ancient craft with modern tech 2026-01-09 Celebrities Jinan athlete claims tai chi all-round gold at 15th National Games 2025-11-11 ABOUT SHANDONG China advancing opening-up to oppose unilateralism Dongying Binzhou Dezhou Yantai Weihai Liaocheng Jinan Zibo Weifang Taian Qingdao Rizhao Heze Jining Zaozhuang Linyi INTL EXCHANGE Why Shandong Industrial Parks Belt & Road Sister Cities ATTRACTIONS Mack Winter wonders await in Shandong Mack Shandong shows potential for winter tourism Mack Cozy winter outings begin in Shandong Mack Snow blankets Daming Lake in winter calm Mack Four recommended ski resorts in Jinan COMPANIES prev 1 2 3 next About Overview Cities Photo Gallery Videos News Latest Features Reports in PDF Developments Transformed Development Drivers Rural Vitalization Marine Economy Culture What's on Heritage Traditional Culture Celebrities Intl Exchange Why Shandong Industrial Parks Belt & Road Sister Cities Brands Strategies Companies Travel Attractions Dining Living Visas Healthcare Transportation Education Marriage Useful Info Fackbook Twitter Links > Beijing Shanghai China (Shandong) Pilot Free Trade Zone Qingdao Area Qingdao West Coast New Area Shandong Provincial People's Government Cultural Jining Charming Qingdao Jinan, A City of Springs Tai'an Wonderland Yantai Copyright . The Information Office of Shandong Provincial People’s Government. All rights reserved. Presented by China Daily. 京ICP备13028878号-6 goTop | 2026-01-13T09:29:33 |
https://wiki.documentfoundation.org/Special:MyLanguage/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:33 |
https://www.atlassian.com/br/jira/solutions/planning | Software de gerenciamento para planejamento de projetos | Atlassian Close Quer visualizar esta página no seu idioma ? Todos os idiomas Escolha seu idioma 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Obtenha grátis Funções Todas as funções Rovo no Jira Back Soluções Equipes Casos de uso Tamanho da empresa Equipes Marketing Desenvolvimento Design Operações TI Casos de uso Introdução Planejamento Gerenciamento de campanha Gerenciamento de projetos no Agile Gerenciamento de programas Tamanho da empresa Empresas Back Guia do produto Modelos Templates Título da coluna Todos os templates Desenvolvimento de software Marketing Design Vendas Operações Gestão de serviços RH Jurídico Operações de TI Finanças Templates do Jira Service Management Back Preços E mais + Menos - Obtenha grátis Back Obtenha grátis A Atlassian foi reconhecida como líder no Magic Quadrant™ da Gartner de 2025 pelo gerenciamento de trabalho colaborativo! Saiba mais PLANEJAMENTO NO JIRA Planejamento flexível para cada equipe Mantenha as equipes e as partes interessadas sincronizadas, independentes e alinhadas às suas metas. Baixe o Jira grátis Faça como os mais de 300 mil clientes que impulsionam a colaboração da equipe com a Atlassian Por que planejar com o Jira? Visualize seu trabalho Divida projetos complexos em partes menores e gerenciáveis. Adicione e ajuste os trabalhos de forma simples para visualizar o tempo e a sequência de diferentes tarefas. Compartilhamento fácil Os cronogramas são atualizados em tempo real à medida que o trabalho avança. Dessa forma, você tem tudo pronto para um compartilhamento imediato com equipes, líderes e partes interessadas. Seu plano, seu estilo Começando do zero ou com um template, você tem a liberdade de personalizar seu plano de acordo com suas necessidades. Veja como o seu trabalho impulsiona as metas da empresa Compare os recursos de planejamento Advanced Basic O Planos , uma função de planejamento avançado do Jira Premium, possibilita a colaboração de várias equipes em programas ou metas compartilhadas. O cronograma , uma visualização do projeto disponível em todas as edições do Jira, permite que você planeje e acompanhe o trabalho em uma única equipe. Promova o trabalho multidisciplinar com o Jira Acompanhe o panorama geral Compare os recursos de planejamento Advanced Basic Com o Planos, você monitora o trabalho em várias equipes e projetos . Na tela de resumo de um plano, você tem uma visualização holística do progresso do trabalho, das dependências e da capacidade da equipe. A visualização do cronograma permite que você planeje o trabalho e acompanhe as dependências de uma única equipe . Antecipe-se às dependências Compare os recursos de planejamento Advanced Basic Mapeie as dependências entre equipes, projetos e muito mais para evitar possíveis conflitos de recursos ou cronograma. Relate dependências às partes interessadas integrando o plano a uma página do Confluence. Mapeie as dependências entre itens de trabalho no projeto para identificar e contabilizar possíveis bloqueadores. Align delivery across multiple teams Advanced only Use program boards to bring teams of teams onto a single plan. Align delivery across multiple sprints and keep complex projects progressing smoothly and on schedule. Planeje pensando na capacidade da equipe Somente Advanced Mantenha as metas sob controle garantindo que as equipes tenham tudo para concluir o trabalho definido no escopo. Visualize a capacidade de várias equipes a cada sprint. Pense em situações diferentes Somente Advanced Tenha acesso a mais informações sobre possíveis resultados criando várias versões do plano com base em diferentes opções ou nos melhores e piores cenários. Release with confidence Advanced only Use releases to track progress, manage timelines, and keep every launch focused. Achieve smoother, more predictable releases that move the business forward. Templates para planejamento Explore os templates personalizáveis do Jira para todo tipo de plano. Planejamento de alto nível Planeje, acompanhe e relate os esforços de toda a empresa, como um programa ou uma iniciativa. Planejamento entre equipes Agende e atribua trabalhos, gerencie a capacidade e monitore o progresso em várias equipes de Scrum. Gerenciamento de projeto Da organização de tarefas à visualização de cronogramas, as equipes têm visão total do progresso do projeto. Explorar mais templates Planejamento de recursos Confira nossos tutoriais, artigos e guias gratuitos para saber mais. Como planejar com o Jira Tutoriais sobre como planejar o trabalho, acompanhar o progresso e mapear dependências. Veja o guia Planejamento estratégico com o Jira Aprenda a estrutura de planejamento estratégico e como ela pode ajudar você a atingir grandes metas. Saiba mais Fundamentos do planejamento de sprint O essencial para aplicar a metodologia Scrum nos fluxos de trabalho da equipe. Explorar agora Transforme a maneira como você trabalha Organizações e equipes trabalhando juntas em um só lugar. Obtenha grátis Empresa Carreiras Eventos Blogs Relações com investidores Fundação Atlassian Kit de imprensa Fale conosco produtos Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Ver todos os produtos Recursos Suporte técnico Compras e licenciamento Comunidade da Atlassian Base de conhecimento Marketplace Minha conta Criar chamado de suporte Saiba mais Parceiros Treinamento e certificação Documentação Recursos de desenvolvedores Serviços corporativos Ver todos os recursos Copyright © 2025 Atlassian Política de privacidade Termos Aviso legal Escolha o Idioma Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:33 |
https://wiki.documentfoundation.org/Special:MyLanguage/Visual_Elements | Design/VisualElements - 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 Design/VisualElements 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 < Design 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 Design Home Whiteboards Development Blueprints UX Principles UX Guidelines Artwork Resources Branding Guidelines Meetings With a consistent ' look and feel' LibreOffice increases its public recognition. People remember graphical elements once they have associated them with our product and community. That's what branding is for! By using the material presented in the galleries linked from this overview you support LibreOffice to be recognized as self-constained and self-confident professional part of the office suite market. The resources linked from here are created in a way that makes it easy to comply with the LibreOffice trademark policy , our logo usage policy and the branding guidelines . In any doubt please have a look at these links. For Artists: If you want to share your own artwork with LibreOffice, feel free to contact the Design Team . You can use your user page to host your graphical ideas. Have a look at Existing Designs too. Categories of Artwork - please click on the titles or thumbnails   Official Main Visuals LibreOffice Logos LibreOffice Icons LibreOffice Product Graphics LibreOffice Motif   Artist Resources Graphical Branding Elements Branding Guidelines and Hints Mockup Kits Ideas for Collaborative Artwork   Marketing Resources ready to use LibreOffice Presentations LibreOffice Videos LibreOffice Flyers Reference Cards Brochuretypes   Electronic Artwork Web Buttons Web Banners Wallpapers   Physical Artwork DVD Labels and Covers Posters and Printed Banners Business Card Stickers and Merchandising   Templates and Documentation Clipart Galleries Impress Templates Writer Templates Screenshots Documentation Fronts Retrieved from " https://wiki.documentfoundation.org/index.php?title=Design/VisualElements&oldid=791566 " Categories : Design Gallery EN This page was last edited 18:01, 9 April 2025 by Krasnaya Ploshchad . Based on work by Adolfo Jayme Barrientos and Klaus-Jürgen Weghorn 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:33 |
https://www.atlassian.com/br/software/jira/templates/marketing | Templates de marketing | Biblioteca de templates do Jira | Atlassian Close Quer visualizar esta página no seu idioma ? Todos os idiomas Escolha seu idioma 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Obtenha grátis Funções Todas as funções Rovo no Jira Back Soluções Equipes Casos de uso Tamanho da empresa Equipes Marketing Desenvolvimento Design Operações TI Casos de uso Introdução Planejamento Gerenciamento de campanha Gerenciamento de projetos no Agile Gerenciamento de programas Tamanho da empresa Empresas Back Guia do produto Modelos Templates Título da coluna Todos os templates Desenvolvimento de software Marketing Design Vendas Operações Gestão de serviços RH Jurídico Operações de TI Finanças Templates do Jira Service Management Back Preços E mais + Menos - Obtenha grátis Back Obtenha grátis Templates do Jira Open and close the navigation menu Categorias Desenvolvimento de software Marketing Design Vendas Operações Gestão de serviços RH Jurídico alimentadas por IA Finanças Templates de gerenciamento de projeto Obtenha grátis Categorias Desenvolvimento de software Marketing Design Vendas Operações Gestão de serviços RH Jurídico alimentadas por IA Finanças Templates de gerenciamento de projeto Templates de marketing Entregue campanhas de marketing relevantes com o Jira. Com templates pré-criados e personalizáveis para equipes de marketing, é fácil começar. Gerenciamento de projeto Gerencie atividades para concluir um projeto de negócios. Gestão de conteúdos Faça a gestão do ciclo de vida do conteúdo, da priorização à entrega. Gerenciamento de campanha Oriente a campanha de marketing desde a ideia até a execução. Entrada no mercado Coordene lançamentos de entrada no mercado. Gerenciamento de serviços de marketing Gerencie e acompanhe todas as solicitações de marketing. Campanha de e-mail Planeje e execute campanhas por e-mail, desde o rascunho até o lançamento Recursos de marketing Jira para equipes de marketing Agilize a equipe de marketing. Saiba mais sobre como o Jira Work Management ajuda a otimizar o trabalho. Saiba mais Coloque os projetos no piloto automático Se concentre no que importa e automatize o resto. Crie as regras personalizadas para a equipe ou comece a trabalhar com rapidez com as automações predefinidas. Descubra automações Conexão com as ferramentas que você prefere Aproveite mais de 500 integrações para trabalhar sem problemas e mais de 3 mil extensões para deixar o processo da equipe perfeito. Conheça o marketplace de aplicativos Empresa Carreiras Eventos Blogs Relações com investidores Fundação Atlassian Kit de imprensa Fale conosco produtos Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Ver todos os produtos Recursos Suporte técnico Compras e licenciamento Comunidade da Atlassian Base de conhecimento Marketplace Minha conta Criar chamado de suporte Saiba mais Parceiros Treinamento e certificação Documentação Recursos de desenvolvedores Serviços corporativos Ver todos os recursos Copyright © 2025 Atlassian Política de privacidade Termos Aviso legal Escolha o Idioma Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:33 |
http://groovy-lang.org/syntax.html#_shebang_line | 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://cn.chinadaily.com.cn/a/202505/28/WS6836a7c5a310205377035619.html | 海外手记 - 中国日报网 China Daily Homepage 中文网首页 时评 资讯 C财经 生活 视频 专栏 双语 --> 原创 观天下 地方 --> 登录 注册 观天下 移动新媒体 站内搜索 站内搜索 观天下 China Daily Homepage 中文网首页 时评 资讯 C财经 生活 视频 专栏 双语 --> 漫画 原创 观天下 地方 海外手记 海外手记 海外手记 | 虞美人花，也为他们开 2 个月 前 海外手记 | 英语的burger是汉堡，德语的Bürger是什么？ 2 个月 前 海外手记丨以音乐架桥沟通中俄：从冼星海到左贞观 3 个月 前 海外手记丨莫斯科机场的中文标识缓解了我的“语言恐慌” 3 个月 前 海外手记丨探寻列宁在喀山的“青葱岁月” 4 个月 前 海外手记丨黄河之声回荡莫斯科——一场跨越时空的音乐缅怀 4 个月 前 海外手记丨舌尖上的榴莲，让中泰友谊常鲜 4 个月 前 海外手记 | 到现场去，到人民中去 ——英国记者乔治·何克给我的启示 4 个月 前 海外手记 | 钱秀玲这个名字，你听说过吗？ 4 个月 前 海外手记 | 英国国旗争夺战 4 个月 前 海外手记 | 黑比利时的诗人，成了比利时的宝 5 个月 前 海外手记 | 七姐妹岩：微信朋友圈里新兴的英伦打卡地 5 个月 前 海外手记 | 讲述，是最深的铭记 ——“里斯本丸”号纪念碑背后的故事 5 个月 前 海外手记 | 等了一百年，塞纳河开泳池了！ 5 个月 前 海外手记 | 论欧洲人为什么热死也不装空调 5 个月 前 1 2 3 4 5 6 7 8 9 10 Next >>| 1/13 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://www.atlassian.com/ko/work-management/strategic-planning | 전략적 계획 설명 [+목표 달성 방법] | The Workstream Close 선택한 언어 로 이 페이지를 보고 계십니까? 모든 언어 언어를 선택합니다. 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 무료로 시작 제품 추천 개발자 제품 매니저 IT 전문가 비즈니스 팀 리더십 팀 추천 개발자 제품 매니저 IT 전문가 비즈니스 팀 리더십 팀 모든 앱 보기 추천 추천 앱 Jira 유연한 프로젝트 관리 Confluence 공동 작업 중심의 지식 작업 영역 Jira Service Management 빠른 속도의 서비스 제공 Atlassian Collection 원활하게 팀워크 강화 Jira • Confluence • Loom • Rovo 전략 및 결과를 자신 있게 최적화 Focus • Talent • Align 신속한 서비스 제공 Jira Service Management • Customer Service Management • 자산 • Rovo 고품질 소프트웨어를 신속하게 제공 Rovo Dev • DX • Pipelines • Bitbucket • Compass 제공: Rovo 팀의 지식으로 구동되는 AI 기반 앱. 개발자 Jira 유연한 프로젝트 관리 Compass 팀을 위한 소프트웨어 카탈로그 파이프라인 확장 가능한 CI/CD 자동화 Bitbucket 소스 코드 및 CI/CD DX (인수 보류 중) 생산성 및 AI 영향 측정 Rovo Dev 개발자를 위한 에이전틱 AI 고품질 소프트웨어를 신속하게 제공 Rovo Dev • DX • Pipelines • Bitbucket • Compass Rovo 팀의 지식으로 구동되는 AI 기반 앱. 제품 매니저 Jira 유연한 프로젝트 관리 Confluence 모두 한곳에 있는 지식 Jira Product Discovery 신규 아이디어 캡처 및 우선 순위 지정 원활하게 팀워크 강화 Jira • Confluence • Loom • Rovo Rovo 팀의 지식으로 구동되는 AI 기반 앱. IT 전문가 Jira Service Management 빠른 속도의 서비스 제공 Guard 신규 향상된 클라우드 보안 Rovo 팀의 지식으로 구동되는 AI 기반 앱. 비즈니스 팀 Jira 유연한 프로젝트 관리 Confluence 모두 한곳에 있는 지식 Trello 체계적이고 시각화된 작업 Loom 신규 빠른 비동기식 동영상 업데이트 Jira Service Management 빠른 속도의 서비스 제공 Customer Service Management Customer experiences reimagined 원활하게 팀워크 강화 Jira • Confluence • Loom • Rovo Rovo 팀의 지식으로 구동되는 AI 기반 앱. 리더십 팀 Focus 신규 엔터프라이즈급 전략 계획 Talent 신규 지식 인력 계획 Jira Align 엔터프라이즈 전체에 걸친 작업 계획 및 가치 전략 및 결과를 자신 있게 최적화 Focus • Talent • Align Rovo 팀의 지식으로 구동되는 AI 기반 앱. Back 솔루션 솔루션 사용 사례별 팀 협업 전략 및 계획 서비스 매니지먼트 소프트웨어 개발 팀별 소프트웨어 마케팅 IT 크기별 Enterprise 소규모 비즈니스 Startup 비영리 기관 업계별 리테일 통신 프로페셔널 서비스 정부 Rovo 팀의 지식으로 구동되는 AI 기반 앱. Back Atlassian을 선택하는 이유 Atlassian을 선택하는 이유 업무 시스템 신규 팀 협업 방식에 대한 Atlassian의 블루프린트 통합 수천 개의 앱을 Atlassian 제품에 연결 고객 팀워크 기반의 사례 연구 및 스토리 FedRAMP 공공 부문을 위한 규정 준수 솔루션 복원력 엔터프라이즈급 및 고성능 인프라 플랫폼 고도로 통합되고 신뢰할 수 있는 안전한 플랫폼 Trust Center 데이터의 보안, 컴플라이언스 및 가용성 보장 Back 리소스 리소스 고객 지원 질문하고 버그를 신고하고 피드백을 제공 파트너 찾기 컨설팅, 교육 및 제품 사용자 지정 지원 Atlassian Ascend 전환을 위한 리소스 및 지원 커뮤니티 Atlassian 커뮤니티와 함께 배우고 소통하며 성장하세요 지원 일반적인 질문 제품 조언 파트너 지원 Enterprise 지원 기술 지원 가격 및 청구 개발자 지원 구매 및 라이선싱 리소스 프로젝트 관리 애자일 Atlassian Learning 시작하기 프로젝트 협업 팀 플레이북 제품 문서 Back Enterprise 자세한 내용 + 간략히 보기 - 무료로 시작 Jira 유연한 프로젝트 관리 Jira Service Management 빠른 속도의 서비스 제공 Confluence 모두 한곳에 있는 지식 제품 모두 보기 무료로 시작 Back 무료로 시작 Confluence로 팀워크를 혁신하세요. Confluence가 모든 팀의 콘텐츠 공동 작업 허브인 이유를 확인하세요. 무료로 시작 The Workstream Strategic planning 전략적 계획이 큰 목표를 흔들어 놓을 수 있는 방식 한 발 물러서서 주력할 곳 찾기 주제 찾아보기 전략적 계획 Back 개요 프레임워크 비전 및 미션 만들기 목표 설정 Back 개요 목표 유형 목표 설정 이론 OKR 예시 Cost benefit analysis 구현 계획 예제 PESTLE analysis PEST analysis SWOT 분석 연간 계획 Business process reengineering 목표 정렬 Quarterly planning 프로젝트 관리 Back 개요 프로젝트 관리 단계 프로젝트 범위 프로젝트 계획 Back 개요 타임라인 프로젝트 계획 개발 작업 계획 제안서 개요 프로젝트 헌장 및 프로젝트 포스터 비교 마일스톤 차트 KPI 비전 보드 스윔레인 다이어그램 마케팅 계획 Operational planning 리소스 계획 Back 개요 작업 수용량 계획 프로젝트 킥오프 회의 프로젝트 실행 Back 개요 템플릿을 통해 올바른 작업을 더 빠르게 완료하세요 프로젝트 추적관리 RACI 차트 프로세스 순서도 의사 결정 프로세스 작업 분류 구조 Confluence 데이터베이스로 콘텐츠 관리 단순화 Confluence 데이터베이스로 할 수 있는지 몰랐던 7가지 멋진 기능 자동화를 사용하여 Confluence 전반의 워크플로 강화 개념 증명 프로젝트 수명 주기 브랜드 런칭 프로젝트 설계 솔루션 순서도 온라인 화이트보드 화이트보드 전략 마인드 매핑 콘셉트 매핑 원칙 반복 프로세스 프로젝트 관리자 프로젝트 목표 프로젝트 목표 예시 대시보드 보고 Enterprise risk management 시간 관리 시간 관리 도구 위험 기록부 PERT 차트 프로젝트 산출물 Acceptance criteria 리드 타임 IT 프로젝트 관리 비즈니스 케이스 프로젝트 포트폴리오 관리 프로세스 매핑 위험 완화 위험 관리 중요 경로 방법 AI 프로젝트 관리 엔터프라이즈 프로젝트 관리 프로젝트 추정 승인 프로세스 최적화 통합 마스터 일정이란 무엇입니까? 세 가지 제약 조건 리소스 관리 Back 개요 추적 8d problem solving 시간 추적 리소스 일정 관리 Enterprise resource management Business Process Automation 마인드맵 예시 리소스 분류 구조 Cost performance index 변경 관리 계획 구현 후 검토 PDCA 주기 Construction project management 건설 프로젝트 관리 소프트웨어 종합적 품질 관리 공감 맵 엔터프라이즈 계획 프로젝트 위험 관리 프로젝트 위험 관리 비즈니스 모델 캔버스 스파게티 다이어그램 지각 매핑의 이해 지연 시간이 프로젝트 관리에 미치는 영향 아키텍처 다이어그램: 정의, 유형 및 모범 사례 이벤트 프로젝트 관리 가이드[2025] 이벤트 마케팅 UML 다이어그램 블록 다이어그램 브랜드 새단장 방법: 핵심 요소 및 주요 단계 데이터 흐름 다이어그램(DFD): 정의 및 주요 구성 요소 Entity relationship diagram 위험 행렬 의사 결정 트리 벤 다이어그램 조직도 친화도 다이어그램 Design sprints Context switching 프로젝트 협업 Back 개요 협업 중심의 문화 Back 개요 협업 중심의 커뮤니케이션 팀 협업 고급 사용자가 제공하는 내부적인 협업 팁 공동 작업을 통한 콘텐츠 만들기 팀 프로젝트 관리 교차 기능 팀 Back 개요 교차 기능 협업 Approvals process 팀 및 이해 관계자 커뮤니케이션 브레인스토밍 모범 사례 Back 개요 브레인스토밍 기법 브레인스토밍 세션 Confluence 화이트보드를 사용한 브레인스토밍(제공 예정) 효과적인 팀 회의 Back 개요 협업 중심의 회의 회의를 줄이는 방법 미팅 메모 및 안건 미팅 케이던스 미팅 회고 프로젝트 설명서 Project retros 이해 관계자 이론 팀 헌장 이해 관계자 매핑: 정의, 이점 및 예시 커뮤니케이션 계획 팀 관리 및 리더십 Back 개요 팀 관리(전략) Back 개요 직원 참여 활동 직원 인정 직장 생산성 원활하지 못한 커뮤니케이션 극복 기능적 조직 구조[정의, 이점 + 예시] 리더십 및 의사 결정 Back 개요 모델 공동 리더십 지식 공유 Back 개요 지식 공유 문화 지식 공유 모범 사례 Back 개요 더 나은 지식 공유를 위해 페이지에 동영상을 게시하세요 알림 관리 및 경고 관리 설명서 Back 개요 설명서의 중요성 설명서 표준 프로세스 설명서 팀을 위한 단일 정보 출처 만들기 Document storage and tracking 제품 문서 소프트웨어 설계 문서 작업 명세서 지식 공유 문화 문서 관리 프로세스 Social intranet Back 개요 엔터프라이즈 소셜 네트워크 여러분과 팀이 새 분기 또는 완전히 새로운 한 해를 시작한다고 상상해 보세요. 제대로 준비해서 함께 큰 성과를 내고 싶은 열의가 가득한 상태입니다. 우선 무엇부터 시작해야 할지 결정해야 합니다. 이론적으로는 기회가 즐거워 보이지만 머지 않아 상황이 악화됩니다. 각자 무엇에 주력해야 하는지에 대한 의견이 다르고 각자의 중대한 우선 순위를 제일 앞세워야 하는 이유를 모두 주장하고 있습니다. 오랜 시간이 지나도록 결정하지 못해서 팀이 실제로 해야 하는 업무가 미뤄지고 있습니다. 회사에서 전략적 계획을 세우지 않을 경우 일어나는 일입니다. 무료 전략적 계획 템플릿 사용 전략적 계획이란? 전략적 계획은 일반적으로 회사의 리더가 수행하며 회사가 방향을 정의하기 위해 거치는 프로세스입니다. 여기에는 전반적인 비전을 지원하기 위해 우선 순위를 설정하고 리소스를 할당하는 방법을 결정하는 단계가 포함됩니다. 전략적 계획과 프로젝트 계획을 혼동하기 쉽지만 둘은 현저히 다릅니다. 프로젝트 계획은 팀이 완료해야 하는 단일 작업 또는 담당 업무에 중요합니다(프로젝트의 시작부터 완료까지 진행하는 방법). 전략적 계획은 더 광범위합니다. 모든 개별 프로젝트를 회사의 중대한 목표를 지원하는 응집력 있는 전략으로 끌어옵니다. 따라서 전략 계획에 회사가 "HR 관리 분야에서 가장 신뢰할 수 있는 전문가로 알려지는 것"을 목표로 삼는다는 비전 선언문 이 있다면 회사가 완료하는 모든 단일 프로젝트는 어떻게든 그 비전과 관련이 있어야 합니다. 기본적으로 전략적 계획은 기업과 리더가 내리는 모든 결정의 나침반이라고 생각하세요. 전체적인 맥락을 설정하므로 일상적인 세부 사항에서 길을 잃지 않습니다. 전략적 계획에 시간을 들일 가치가 있는 이유 1. 노력에 집중(+스트레스 감소) 팀을 위해 결정을 내리는 것이 종종 다트를 던지는 것처럼 느껴집니까? 여러분만 느끼는 기분은 아닙니다. McKinsey에서 실시한 설문 조사에 따르면 응답자 중 20% 만 현재 조직이 의사 결정 에 탁월하다고 답했습니다. 전략적 계획을 세우면 도움이 됩니다. 회사 전체가 어디로 향하고 있는지 파악하면 더 신중하게 최종 목표를 지지하는 결정을 내릴 수 있습니다. 또한 전략적 계획은 특정 프로젝트가 전체 계획에 어떻게 기여하는지 보여줄 수 있는 명확하고 측정 가능한 결과를 모든 프로젝트에 제공합니다. 2. 커뮤니케이션 개선 다음 시나리오에서 벌어질 모든 오해와 혼란을 상상해 보세요. 여러분은 동료에게 분기 재무제표 작성에 유용한 지침을 알려주었습니다. 그런데 그 동료는 당월의 수표 번호를 기록하는 법을 배우고 있다고 생각했습니다. 혼란스럽네요. 시간이 낭비되었습니다. 하지만 직장에서 이런 일이 빈번하게 발생합니다. '매우 자주', '자주' 또는 '가끔' 커뮤니케이션 착오가 일어난다고 답한 직원이 80% 이상입니다. 다행히도 직원이 (전략 계획을 검토하면 알게 되는) 더 큰 그림을 잘 이해하면 메시지가 더 명확해집니다. 직원은 방향을 이해하고 지침을 제공하며 자신 있게 프로젝트를 추진하는 데 필요한 상황과 배경 정보를 이미 갖추고 있습니다. 회사 전체가 어디로 향하고 있는지 파악하면 더욱 신중하게 최종 목표를 지지하는 결정을 내릴 수 있습니다. 3. 일관성 향상 놀라운 통계가 여기 있습니다. 회사 직원 중 최대 95% 가 회사 전략을 잘 모르거나 이해하지 못한다고 답했습니다. 매우 높은 비율입니다. 직원은 자신의 일상이 회사 성장에 어떤 영향을 미치는지 아무것도 모르거나 잘 이해하지 못하는 것을 좋아하지 않습니다. 전략적 계획이 있으면 최고 경영진부터 신규 직원까지 팀원 모두가 자신이 무엇을 향해 일해야 하는지 알 수 있습니다. 전략적 계획을 문서화하고 쉽게 확인할 수 있게 만들어서 누구든지 다시 참조하여 명확하게 이해할 수 있도록 하세요. 일반적으로 전략적 계획이 성공하는 또 다른 이유는 공동 작업 중심의 프로세스이기 때문입니다. 공개적으로 논의한다는 것은 처음부터 모든 당사자가 같은 정보를 공유한다는 의미입니다. 세 가지 활동을 통한 최고의 전략적 계획 프로젝트 계획 방면에서 이미 전문가라면 회사 중심의 더 큰 규모라는 점에서 전략적 계획과 유사한 점이 많으므로 안심하세요. 하지만 전략적 계획에는 고유한 몇 가지 활동이 있습니다. 이 활동은 리더십 팀이 여러분의 비전을 지원하는 계획을 세우는 데 활용할 수 있습니다. 1. SWOT 분석 SWOT 분석은 회사의 강점, 약점, 기회뿐만 아니라 비즈니스를 위협하는 요소도 파악해야 합니다. 여기에 접근하는 가장 간단한 방법은 각 요소를 2x2 행렬로 나타내는 것입니다( 여기에서 유용한 템플릿 가져오기 ). SWOT Analysis Strengths Opportunities • • Weaknesses Threats • • SWOT Analysis Strengths • Opportunities • Weaknesses • Threats • 위 표에 제품이나 회사의 강점, 약점, 기회, 위협 요소를 나열합니다. 예를 들어 여러분의 강점 은 경쟁사에는 없는 기술을 보유하고 있다는 것이고 기회 는 더 넓은 시장에 진출할 수 있다는 것입니다. 반면에 약점 은 재원이 부족하다는 것이고 위협 은 비슷한 회사가 점점 더 많이 시장에 진출하고 있다는 것입니다. 이 정보를 통해 각 요소를 고려하는 전략을 세울 수 있으므로 계획을 세울 때 중요하게 활용됩니다. SWOT 분석은 전략적 계획 뿐 아니라 새 프로젝트, 기능 등에도 언제든지 수행할 수 있습니다. 유연한 프레임워크입니다. SWOT 분석에는 누가 참여해야 합니까? 무엇을 계획하는지에 따라 대답이 달라집니다. 하지만 명확하게 전략적 계획에 사용할 때는 리더십 팀이 반드시 참여해야 합니다. 2. Start-Stop-Continue(시작-중지-계속) 역사는 훌륭한 스승입니다. 과거의 성공과 실패를 통해 많은 것을 배울 수 있습니다. Start-Stop-Continue(시작-중지-계속)는 회사에서 최근 경험을 돌아보고 앞으로 무엇을 바꿔야 하는지 결정하는 회고적 기법입니다. 팀을 모으고 다음 세 가지 범주의 활동을 브레인스토밍하게 됩니다. Start(시작) : 아직 행하지 않았지만 조직에 긍정적 영향을 미칠 만한 활동입니다. Stop(중지) : 현재 수행하고 있지만 조직에 부정적 영향을 미치는 활동입니다. Continue(계속) : 시도해서 성공했지만 아직 일상적이지 않은 활동입니다. 모든 팀원에게 각 범주에 대해 최대한 많은 아이디어를 떠올릴 시간을 주세요. 그런 다음 팀과 함께 토론하고 비슷한 아이디어를 그룹화하여 어떤 그룹을 가장 먼저 다룰지 정합니다. 이 프레임워크는 맹목적인 낙관주의로 또는 지금까지의 상황이 어떠한지 충분히 알지 못하는 상태로 진행하지 않고 전략적 계획을 세워 진행할 수 있는 귀중한 인사이트를 제공합니다. 전략적 계획은 모든 개별 프로젝트를 회사의 중대한 목표를 지원하는 응집력 있는 전략으로 끌어옵니다. 3. 계획 업데이트 전략적 계획은 회사의 전체 수명 기간 동안 회사가 따라야 할 리소스입니다. 그렇다고 해서 처음에 세운 계획을 그대로 지켜야 한다는 뜻은 아닙니다. 회사와 함께 점차 발전해야 합니다. 따라서 계획을 세우기만 하고 잊어버리지 마세요. 정기적으로(이상적으로는 분기별로) 시간을 내서 계획 진행률을 검토하고 필요한 경우 변경 및 업데이트해야 합니다. 전략적 계획을 계속 개선하면 디지털 먼지만 모아 놓은 구식의 관련 없는 문서가 아니라 꾸준히 활용할 수 있는 리소스가 됩니다. 소프트웨어가 도움이 될 수 있는 방법 정적 문서를 열고 회사 전략적 계획에 대해 생각나는 대로 적어볼까 고민하고 있습니까? 아직은 아닙니다. 공동 작업 문서 소프트웨어를 통해 다음 기능을 활용하면 전체 전략적 계획 프로세스가 더 간편해집니다. 구체적 로드맵 만들기 팀원에게 작업 할당 한곳에서 정보 수집 및 추적 프로세스에 다른 팀원 추가 원활한 업데이트 이제 유연하지 않은 문서는 버리고 기술을 활용하여 큰 스트레스 없이 전략적 계획을 수립할 수 있습니다. 지금 바로 Confluence를 확인하세요 . 전략적 계획을 하나로 모으기 전략적 계획은 간단할 수도 있고 복잡할 수도 있습니다. 한 페이지로 끝나는 계획도 있고 장황하게 긴 계획도 있습니다. 즉, 회사에 맞도록 유연하게 원하는 대로 조합할 수 있습니다. 전략적 계획을 세울 때는 다음이 포함되어야 합니다. 회사에 대한 간략한 설명 : 회사 이력과 주요 제품 및/또는 서비스의 하이라이트를 간략하게 요약합니다. 미션 선언문 : 회사의 존재 목적을 설명합니다. 비전 선언문 : 앞으로의 회사 비전을 설명합니다. 현재 위치를 설명하는 대신 목표로 삼는 위치를 설명합니다. 이미 아시다시피 전략적 계획의 나머지 부분은 회사 전략으로만 채울 것입니다. 더 관리하기 쉽도록 다음과 같은 세 가지 범주로 분류하는 것이 좋습니다. 목표 : 회사가 달성하고자 하는 크고 측정 가능한 목표. 전략 : 목표 달성을 위해 따라야 할 한층 세부적인 단계. 전술 : 회사가 결정하는 전략 범위에 있는 개별 조치 항목. 명확한 설명을 위해 예를 들겠습니다. 다음은 전략적 계획에 포함될 수 있는 내용입니다. 목표 1 : 1분기 말까지 총 매출을 $850,000에서 $1,000,000로 올린다. 전략 1.1 : 이메일 캠페인을 만들어 무료 평가판 사용자를 유료 사용자로 전환한다. 전술 1.1.1 : 이메일 목록을 유료 구독자와 무료 사용자로 세분화한다. 전술 1.1.2 : 유료 티어로 전환하는 사용자를 위한 특별 혜택을 생성한다. 전술 1.1.3 : 전환할 마음이 생기도록 3개의 이메일 시리즈를 작성한다. 큰 목표에서 실행 가능성이 더 높은 부분으로 이어지는 과정을 확인하셨습니까? 전략적 계획을 세울 때마다 이 과정을 반복할 것입니다. 각 목표에는 그것을 지원하는 몇 가지 전략이 있어야 하고 각 전략에는 수많은 전술이 포함됩니다. 이제 회사 전략에 대해 막연한 아이디어가 아니라 따라갈 수 있는 상세한 로드맵이 생겼습니다. 전략적 계획으로 성공에 한걸음 더 다가가기 전략적 계획이 없으면 팀 또는 회사 전체가 갈 곳을 잃은 기분이 들기 쉽습니다. 혼란이 확산되고 불만이 쌓이면서 중요한 업무는 끝내지 못하고 무의미한 곳에 시간을 낭비할 것입니다. 이 경우 전략적 계획을 통해 시간을 절약할 수 있습니다. 전략적 계획에 힘써 투자하면 더 집중해서 노력하고 정보를 토대로 선택하고 커뮤니케이션을 간소화하며 가장 중요한 일을 진행할 수 있습니다. 시간과 에너지를 투자할 만한 가치가 있다고 여겨집니까? Atlassian도 그렇게 생각합니다. 이제 시작할 일만 남았습니다. 전략을 막상 실행에 옮기면 생각보다 어렵지 않다는 것을 Atlassian이 약속합니다. 관련 자료 OKR 템플릿 큰 목표와 그 목표에 도달하는 전략 세우기 사용해 보기 사용해 보세요 Confluence는 팀워크를 통합하기 위해 조직이 비전, 계획, 목표를 문서화하고 공유하는 팀 작업 영역입니다. 자세히 알아보기 Confluence로 모든 팀이 더 빠르게 콘텐츠 공동 작업 가능 무료로 시작 자세히 알아보기 Choose your language Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 개인정보보호 이용 약관 Copyright © 2026 Atlassian 다음 단계 프레임워크 | 2026-01-13T09:29:33 |
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:33 |
https://reports.jenkins.io/jelly-taglib-ref.html#test | 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://cn.chinadaily.com.cn/a/202302/09/WS621c9440a3107be497a08404.html | 世界说 - 中国日报网 China Daily Homepage 中文网首页 时评 资讯 C财经 生活 视频 专栏 双语 --> 原创 观天下 地方 --> 登录 注册 观天下 移动新媒体 站内搜索 站内搜索 观天下 China Daily Homepage 中文网首页 时评 资讯 C财经 生活 视频 专栏 双语 --> 漫画 原创 观天下 地方 世界说 世界说 【世界说】国际法专家密集发声：美对委行动是于法无据的“强权即公理”行径 损害国际秩序根基 5 天 前 【世界说】对委军事行动遭美国国内声讨 议员警告：终将给美民众带来灾难性后果 6 天 前 【世界说】美国媒体2025年终回顾：贸易战最大教训——消费者被迫承受更高生活成本 2 周 前 【世界说】外媒：美对台军售只为敲骨吸髓满足自身利益 2 周 前 【世界说】美媒：必需品通胀吞噬购买力，美国消费者感受到寒意 2 周 前 【世界说・年终观察】2025年美国枪暴“多棱镜”：被压制的研究，被贩卖的恐惧，被撕裂的校园 2 周 前 【世界说】日本官员“拥核言论”暴露危险野心 多方警告勿蹈覆辙 3 周 前 【世界说】“我们亲历过核事故风险，不能轻视它” 外媒：日本将重启其最大核电站，当地民众谨慎存疑 3 周 前 【世界说】日本防卫费“野蛮生长”引国际担忧，专家警告威胁地区安全且民生在“防卫优先”下承压 4 周 前 【世界说】日本网络平台“嫌中”视频招聘暴露右翼水军产业化链条 4 周 前 【世界说】当美国假日季遭遇通胀 美最新民调：近七成民众坦言财务焦虑让节日计划“缩水” 4 周 前 【世界说】菲学者：高市早苗涉台错误言论犹如打开亚太地缘安全“潘多拉魔盒” 1 个月 前 【世界说】“存亡危机”言论成自困预言 日本经济恐因高市挑衅言论承受沉重代价 1 个月 前 【世界说】外媒：日本“和平假面”下防卫预算13连增 应警惕军国主义幽灵复现 1 个月 前 【世界说】日学者及国际政界人士批高市涉台错误言论：触碰多重红线 违背历史正义与外交共识 2 个月 前 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://wiki.documentfoundation.org/Special:MyLanguage/QA | QA - 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 QA 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 Bug Report Bug Triage Projects Regression Test Automated Tests Bibisect QA Meetings QA FAQs Other languages: Bahasa Indonesia Deutsch English Nederlands dansk español français galego italiano português do Brasil čeština монгол русский українська العربية فارسی नेपाली བོད་ཡིག 中文（中国大陆） 中文（臺灣） 日本語 한국어 Getting Started Get Involved Bugzilla Easy Hacks Bug Hunting Sessions Join the QA discussion: via our IRC channel : # libreoffice-qa IRC:// XMPP:// which is bridged to Telegram or on our mailing list FAQs FAQs about Quality Assurance FAQs about Bugzilla Release Plan Policies and Procedures for users interacting with Bugzilla Bug Report How to Report Bugs in LibreOffice LibreOffice components in Bugzilla How to Report Bugs in LibreOffice Extensions Troubleshoot and Report Printing Problems Templates for searching in Bugzilla Table By Platform (OS) and gravity Table By Component and gravity Sorting Bug Triage All Bugzilla fields Version field Importance: Priority and Severity fields Whiteboard field Keywords field Status field Setting Bugs to NEEDINFO Status Meta Bugs (aka "Tracking Bugs") Most Annoying Bugs (MAB) LibreOffice bug tracking in Linux distributions Debian bug tracker Gentoo tracker Fedora tracker openSUSE tracker Ubuntu tracker Team QA Team Meetings Goals Projects QA-related Bugs Recurring QA Tasks QA Statistics Testing Installing several versions of LibreOffice in parallel GNU Linux Windows macOS Testing Daily Builds Automated Tests UI Tests Regression Tests Bibisecting Debug Information How to get a backtrace with WinDbg Media Support Summary Debugging Configuration Layers Contacts QA IRC Channel QA Mailing List Developer Mailing List Find the Expert Builds Stable Pre-Release Nightly Old Tinderbox Retrieved from " https://wiki.documentfoundation.org/index.php?title=QA&oldid=765303 " Category : QA This page was last edited 17:25, 30 July 2024 by Ilmari Lauhakangas . Based on work by Stéphane Guillou and L D 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:33 |
http://groovy-lang.org/syntax.html#integer_division | 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://www.atlassian.com/it/software/jira/guides/issues/tutorials | Tutorial sui ticket di Jira Software | Atlassian Close Visualizzare la pagina in tua lingua ? Lingue Scegli la tua lingua 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Ottienilo gratis Funzionalità Tutte le funzioni Rovo in Jira Back Soluzioni Team Casi d'uso Dimensione azienda Team Marketing Ingegneria Progettazione Operazioni IT Casi d'uso Guida introduttiva Pianificazione Gestione delle campagne Gestione dei progetti Agile Gestione dei programmi Dimensione azienda Enterprise Back Guida al prodotto Modelli Modelli Tutti i modelli Sviluppo software Marketing Progettazione Vendite Operazioni Gestione servizi Risorse umane Legale Operazioni IT Finanza Modelli di Jira Service Management Back Prezzi Altro + Riduci - Ottienilo gratis Back Ottienilo gratis Guida introduttiva Introduzione a Jira Jira per i team 7 passaggi per iniziare a utilizzare Jira Progetti Panoramica Tutorial Risorse Bacheche Panoramica Tutorial Risorse Ticket Panoramica Tutorial Risorse Flussi di lavoro Panoramica Tutorial Risorse Integrazioni Panoramica Tutorial Risorse Report e dashboard Panoramica Tutorial Risorse Approfondimenti Panoramica Tutorial Risorse Autorizzazioni Panoramica Tutorial Risorse JQL Panoramica Tutorial Scheda di riferimento rapido Risorse Navigazione Overview Tutorials Resources Automazione Panoramica Tutorial Risorse Sequenza temporale Panoramica Tutorial Risorse Advanced Roadmaps Panoramica Tutorial Risorse Jira per dispositivi mobili Panoramica Tutorial Risorse Maggiori informazioni su Jira Edizioni di Jira Opzioni di hosting Tutorial sui ticket di Jira Crea un ticket Seleziona "Crea" nella barra di navigazione in alto. Il ticket verrà visualizzato nel backlog o nella board del progetto. Trovare un ticket Eseguire una ricerca globale e trovare un ticket nel sito Tramite la barra di ricerca nella barra di navigazione in alto è possibile cercare rapidamente i ticket nell'intera istanza tramite il loro ID o le parole chiave corrispondenti. Puoi restringere la ricerca in base a progetto, assegnatario e/o stato. Eseguire una ricerca contestuale e trovare un ticket nella visualizzazione board, roadmap o backlog del progetto Le barre di ricerca sono disponibili nella visualizzazione roadmap, backlog e board. I ticket trovati in una di queste viste vengono visualizzati nei risultati di ricerca. Trovare un ticket di lavoro in un determinato progetto tramite lo strumento di navigazione dei ticket Spostati su "Ticket" nella barra di navigazione laterale. Passa dalla modalità "Basic" a "JQL", e viceversa, in alto a destra sullo schermo. Nella modalità Basic, puoi digitare parole chiave nella barra di ricerca e/o utilizzare i menu a discesa per filtrare i ticket per progetto, tipo di ticket, stato, assegnatario e qualsiasi altro campo che potrebbe essere presente in un ticket. Nella modalità JQL, puoi creare query strutturate utilizzando Jira Query Language (JQL) per cercare i ticket. Tieni presente che, per impostazione predefinita, lo strumento di navigazione dei ticket non è disponibile nei progetti gestiti dal team. Per abilitare questa funzione, accedi a Impostazioni progetto > Funzionalità > Strumento di navigazione dei ticket . Aggiungere un tipo di ticket a un progetto Nei progetti gestiti dal team: Seleziona "Impostazioni progetto" nella barra di navigazione a sinistra, quindi seleziona "Tipi di ticket" e premi "+ Aggiungi tipo di ticket". Trascina e rilascia i tipi di campi che desideri inserire nel tipo di ticket e assegna un nome a ogni campo. Puoi anche impostare i valori predefiniti per ogni campo, se preferisci. Nei progetti gestiti dall'azienda: Come collegare i ticket Apri un ticket. Seleziona Collega ticket nella parte superiore della finestra modale del ticket. Scegli il tipo di collegamento al ticket, ad esempio "questo ticket è bloccato da...". Specifica i ticket a cui desideri collegarti digitando il rispettivo identificatore completo, ad esempio ABC-123. Seleziona Link (Collega). Configurare il layout di un ticket Seleziona un ticket nella board. In basso a destra nella visualizzazione ticket, seleziona Configura . Trascina e rilascia i campi del ticket nelle aree appropriate. Azienda Opportunità di carriera Eventi Blog Relazioni investitori Fondazione Atlassian Kit per la stampa Contattaci Prodotti Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Vedi tutti i prodotti Risorse Supporto tecnico Acquisto e licenza Atlassian Community Knowledge base Marketplace Il mio account Crea ticket di supporto Impara Partner Formazione e certificazione Documentazione Risorse per lo sviluppo Servizi aziendali Vedi tutte le risorse Copyright © 2025 Atlassian Informativa sulla privacy Condizioni Impressum Scegli la Lingua Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:33 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3Aproperty | 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://www.tumblr.com/policy/terms-of-service#dmca | Tumblr Log in Sign up Terms of Service Last Modified: 2024-09-06 Tumblr is a U.S. company and subject to U.S. laws and jurisdiction. The original version of these Terms of Service (and any other terms, policies, or guidelines that we provide to you) are written in English. To the extent any translated version of these Terms of Service (or any other terms, policies, or guidelines that we provide to you) conflicts with the English version, the English version controls. THESE TERMS OF SERVICE CONTAIN LIMITATIONS OF TUMBLR'S LIABILITY IN SECTION 15. Hello! Welcome to Tumblr’s Terms of Service. Please read this carefully before using our site, services, or products. This is a contract between you and Tumblr. We've also included several annotations that aren't a part of the contract itself, but are intended to emphasize key sections and help you follow the text. We've tried to be fair and straightforward. Please feel free to contact us if you have any questions or suggestions! 1. Accepting the Terms of Service Please read these Terms of Service and our User Guidelines (collectively, the " Agreement ") carefully before using tumblr.com (the " Site ") and/or the other domains, websites, products, applications, mobile applications, services, and/or Content provided by Tumblr, Inc. (all of those collectively with the Site, the " Services ") (Tumblr, Inc., a Delaware corporation and wholly-owned subsidiary of Automattic Inc., a Delaware corporation (" Automattic "), collectively with its agents, representatives, consultants, employees, officers, and directors, " Tumblr ," " we ," or " us "). By using or accessing the Services, you agree to be bound by all the terms and conditions of this Agreement. If you don't agree to all the terms and conditions of this Agreement, you shouldn't, and aren't permitted to, use the Services. Tumblr’s personalized Services cannot be provided and the terms of this Agreement cannot be performed without Tumblr processing information about you and other users. Processing of the information you share with Tumblr is essential to the personalized Services which we provide and which you expect, including personalized Content (as described below) and ads, and is a necessary part of our performance of the agreement we have with you. We’re just letting you know, here, that Tumblr is now part of Automattic , a technology company that empowers people to build beautiful websites, tell their stories, and find and grow their audience and these Terms of Service , which apply to your use of Tumblr, have been updated to reflect this change. This section also includes an agreement where you're agreeing to agree to the terms of this Agreement. 2. Modifications to this Agreement Tumblr reserves the right to modify these Terms of Service or our User Guidelines by providing notice to you. We will provide notice to you by posting a revised version of the modified Terms of Service or User Guidelines on the Services, and, in some cases we may provide additional notice to you such as via email, or otherwise through the Services (such as through a notification on your Tumblr Dashboard or in our mobile applications). Modifications will not apply retroactively. You are responsible for reviewing and becoming familiar with any modifications to this Agreement. We may sometimes ask you to review and to explicitly agree to (or reject) a revised version of this Agreement. In such cases, modifications will be effective at the time of your agreement to the modified version of this Agreement. If you do not agree at that time, you are not permitted to use the Services. In cases where we do not ask for your explicit agreement to a modified version of this Agreement, but otherwise provide notice as set forth above, the modified version of this Agreement will become effective fourteen days after we have posted the modified Agreement and provided you notification of the modifications. Your use of the Services following that period constitutes your acceptance of the terms and conditions of this Agreement as modified. If you do not agree to the modifications, you are not permitted to use, and should discontinue your use of, the Services. Note that, if you have prepaid for any Paid Services (as defined below) prior to a modification of this Agreement, your use of such prepaid Paid Services is governed by the version of this Agreement in effect at the time Tumblr received your prepayment. As Tumblr grows and improves, we might have to make changes to these Terms of Service. When we do, we'll let you know. We're also going to make it a practice to post old versions so it's easy to see changes/additions/deletions. To see old versions, scroll down to the end of this document. 3. Use of the Services Eligibility: You may not use the Services, provide any personal information to Tumblr, or otherwise submit personal information through the Services (including, for example, a name, address, telephone number, or email address) if you are under the Minimum Age. The Minimum Age is (i) thirteen (13), (ii) sixteen (16) for users in the European Union or the United Kingdom, or (iii) eighteen (18) for certain features. You may only use the Services if you can form a binding contract with Tumblr and are not legally prohibited from using the Services. You have to be the Minimum Age to use Tumblr. We're serious: it's a hard rule. “But I’m, like, almost old enough!” you plead. Nope, sorry. If you're not old enough, don't use Tumblr. Ask your parents for a Playstation 4, or try books. Service Changes and Limitations: The Services change frequently, and their form and functionality may change without prior notice to you. Tumblr retains the right to create limits on and related to use of the Services in its sole discretion at any time with or without notice. Tumblr may also impose limits on certain Services or aspects of those Services or restrict your access to parts or all of the Services without notice or liability. Tumblr may change, suspend, or discontinue any or all of the Services at any time, including the availability of any product, feature, database, or Content (as defined below). Tumblr may also terminate or suspend Accounts (as defined below) at any time, in its sole discretion. Tumblr is an ever-evolving platform. With new products, services, and features launching all the time, we need flexibility to make changes, impose limits, and occasionally suspend or terminate certain offerings (like features that flop). We can also terminate or suspend any account at any time. That sounds harsh, but we only use that power when we have a reason, as outlined in these Terms of Service, our Privacy Policy , and our User Guidelines . Limitations on Automated Use: You may not, without express prior written permission, do any of the following while accessing or using the Services: (a) tamper with, or use non-public areas of the Services, or the computer or delivery systems of Tumblr and/or its service providers; (b) probe, scan, or test any system or network (particularly for vulnerabilities), or otherwise attempt to breach or circumvent any security or authentication measures; (c) access or search or attempt to access or search the Services by any means (automated or otherwise) other than through our currently available, published interfaces that are provided by Tumblr (and only pursuant to those terms and conditions) or unless permitted by Tumblr's robots.txt file or other robot exclusion mechanisms; (d) scrape the Services, and particularly scrape Content (as defined below) from the Services; (e) use the Services to send altered, deceptive, or false source-identifying information, including without limitation by forging TCP-IP packet headers or email headers; or (f) interfere with, or disrupt, (or attempt to do so), the access of any other user of the Services, host or network, including, without limitation, by sending a virus to, spamming, or overloading the Services, or by scripted use of the Services in such a manner as to interfere with or create an undue burden on the Services. Don't do bad things to Tumblr or to other users. Some particularly egregious examples of "bad things" are listed in this section. Recommender Systems: For more information on how content is displayed in Tumblr's feeds and our use of recommender systems to show you content we think you'll love, please see this Help Center article . 4. Registration, Tumblr URLs, and Security As a condition to using certain of the Services and in order for us to provide them to you, you may be required to create an account (an " Account "), provide your age and an email address and select a password and Tumblr username, which will serve as a default link to your default Tumblr blog of the form [username].tumblr.com (a " Tumblr URL "). You must select a different Tumblr URL for each new blog you create. You agree to provide Tumblr with accurate, complete, and updated registration information, particularly your email address. It's really important that the email address associated with your Tumblr account is accurate and up-to-date. If you ever forget your password - or worse, fall victim to a malicious phishing attack - a working email address is often the only way for us to recover your account. You are also responsible for maintaining the confidentiality of your Account password and for the security of your Account, and you will notify Tumblr immediately of any actual or suspected loss, theft, or unauthorized use of your Account or Account password. 5. Privacy For information about how Tumblr collects, uses, and shares your information, please review our Privacy Policy . By using the Services you agree you have read the Privacy Policy, which describes our collection, use, and sharing (as set forth in the Privacy Policy) of such information, including the transfer of this information to the United States and/or other countries for storage, processing, and use by Tumblr and the Tumblr Affiliates (as defined below). 6. Content and User Content Definitions: For purposes of this Agreement: (1) the term " Content " means a creative expression and includes, without limitation, video, audio, photographs, images, illustrations, animations, logos, tools, written posts, replies, comments, information, data, text, software, scripts, executable files, graphics, Themes (as defined below), and interactive features, any of which may be generated, provided, or otherwise made accessible on or through the Services; (2) the term " User Content " means Content that you or any other user of the Services (collectively, a " User ") submits, transfers, or otherwise provides to the Services. Content includes, without limitation, all User Content. Your Rights in User Content: Users retain ownership and/or other applicable rights in User Content, and Tumblr and/or third parties retain ownership and/or other applicable rights in all Content other than User Content. You retain ownership you have of any intellectual property you post to Tumblr. User Content License to Tumblr: When you provide User Content to Tumblr through the Services, you grant Tumblr a non-exclusive, worldwide, royalty-free, sublicensable, transferable right and license to use, host, store, cache, reproduce, publish, display (publicly or otherwise), perform (publicly or otherwise), distribute, transmit, modify, adapt (including, without limitation, in order to conform it to the requirements of any networks, devices, services, or media through which the Services are available), and create derivative works of, such User Content. The rights you grant in this license are for the limited purposes of allowing Tumblr to operate the Services in accordance with their functionality, improve and promote the Services, and develop new Services. The reference in this license to "creat[ing] derivative works" is not intended to give Tumblr a right to make substantive editorial changes or derivations, but does, for example, enable reblogging , which allows Tumblr Users to redistribute User Content from one Tumblr blog to another in a manner that allows them to add their own text or other Content before or after your User Content. When you upload your creations to Tumblr, you’re giving us permission to make them available in all the ways you would expect us to (for example, via your blog, RSS, the Tumblr Dashboard, etc.). We never want to do anything with your work that surprises you. Something else worth noting: Countless Tumblr blogs have gone on to spawn books, films, albums, brands, and more. Any royalties or reimbursement you get for your creations are, needless to say, entirely yours. It's your work, and we're proud to be a part (however small) of what you accomplish. You also agree that this license includes the right for Tumblr to make all publicly-posted Content available to third parties selected by Tumblr, so that those third parties can syndicate and/or analyze such Content on other media and services. An example of what it means to "make all publicly-posted Content available" to a Tumblr partner for distribution or analysis would be licensing the Tumblr "firehose," a live feed of all public activity on Tumblr, to partners like search engines. Note also that this license to your User Content continues even if you stop using the Services, primarily because of the social nature of Content shared through Tumblr’s Services - when you post something publicly, others may choose to comment on it, making your User Content part of a social conversation that can’t later be erased without retroactively censoring the speech of others. One thing you should consider before posting: When you make something publicly available on the Internet, it becomes practically impossible to take down all copies of it. You also agree that you will respect the intellectual property rights of others, and represent and warrant that you have all of the necessary rights to grant us this license for all User Content you provide. Tumblr may add its own affiliate code to links posted on Tumblr at its discretion, provided a user has not previously included their own affiliate code into the applicable link. Users may opt out of this functionality here . Content License to You: As a User of the Services, Tumblr grants you a worldwide, revocable, non-exclusive, non-sublicensable, and non-transferable license to download, store, view, display, perform, redistribute, and create derivative works of Content solely in connection with your use of, and in strict accordance with the functionality and restrictions of, the Services (including, without limitation, Paid Services, as defined below). This means, for example, that we license Content to you for purposes of reblogging. Compliance with User Guidelines: You agree that you won't violate Tumblr's User Guidelines . These Guidelines provide information on a few categories of content that are damaging to our community. If you violate the Guidelines, you may not be able to continue using Tumblr. Termination and Deletion: On termination of your Account, or upon your deletion of particular pieces of User Content from the Services, Tumblr shall make reasonable efforts to make such User Content inaccessible and cease use of it and, if required by the applicable Privacy Policy, delete your Account data and / or User Content unless permitted or required to keep this data in accordance with law; however, you acknowledge and agree that: (a) deleted User Content may persist in caches or backups for a reasonable period of time and (b) copies of or references to the User Content may not be entirely removed (due to the nature of reblogging, for example). You can delete your account at any time here . 7. Special Provisions for Application Developers If you develop software or services based on the Services or any Content, whether using the Tumblr Application Programming Interface or not, you will agree to and comply with the Tumblr Application Developer and API License Agreement . 8. Special Provisions for Advertising and Sponsored Content If you post or buy advertisements or sponsored Content, you must comply with our Global Advertising Policy 9. Use of Trademarks Any use of Tumblr's trademarks, branding, logos, and other such assets in connection with the Services shall use Tumblr’s approved branding and shall be in accordance with the Tumblr Trademark Guidelines . 10. Themes Tumblr makes available specialized HTML and CSS code (" Tumblr Template Code ") for the design and layout of blog pages available for use on some of the Services (" Themes "). Certain Themes are available for purchase as a Paid Service (as defined below) (such Themes, " Premium Themes "). Purchased Premium Themes may not be transferred between Accounts, between blogs, or between Services on a single Account and are subject to the payment terms herein. Tumblr grants you a license to customize the Tumblr Template Code to create your own Themes for use on your blog page (each a " Custom Theme "). If you choose, you may also contribute your Custom Themes for use by other Users as User Content. However, as a condition of this license allowing you to create Custom Themes, you agree that you won't distribute such Custom Themes from locations other than Tumblr-owned or approved websites without our permission, as set out in our User Guidelines . Note also that other Users may use your Custom Themes after you have removed them from distribution, and you hereby grant those Users an irrevocable license to use those Custom Themes as contributed by you. In other words, you can remove and stop distribution of your Custom Themes, but Users who are already using them can keep using them. To develop and distribute Custom Themes that are Premium Themes, please contact us . 11. Paid Services Some of the Services require payment of fees (the " Paid Services ," including without limitation Premium Themes, Blaze, and Subscriptions). All fees are stated in United States dollars. You shall pay all applicable fees, as described in the applicable Services, in connection with such Services, and any related taxes or additional charges. Paid Services are limited licenses for you to use particular for-pay aspects of the Services. Usage of terms like sell, sale, buy, purchase, or similar terms all refer to your acquisition of a license to use Paid Services, and do not represent any transfer of any right, title, or ownership interest of any kind. You may not relicense, resell, transfer, or exchange Paid Services within or outside of the Services, except as expressly allowed by the rules of those Paid Services. Tumblr may, in its sole discretion, modify the functionality of, or eliminate, Paid Services, or the terms and conditions under which Paid Services are provided. Purchases of Paid Services are final and non-refundable (particularly those Paid Services that may be used immediately, such as Promotions, as defined below), except at Tumblr's sole discretion and in accordance with the rules governing each Paid Service. Termination of your Account or your rights under this Agreement may result in forfeiture of purchased Paid Services. For example, if your Account is suspended, you forfeit your license to any Premium Themes you have purchased. Tumblr may change prices for Paid Services it provides at any time. To the extent applicable, Tumblr will provide you reasonable notice of any such pricing changes by posting the new prices on or through the applicable Paid Service and/or by sending you an email notification. If you do not wish to pay the new prices, you may choose not to purchase, or to cancel, the applicable Paid Service offered by Tumblr prior to the change going into effect. 12. Recurring Payments: Some Paid Services on Tumblr automatically renew as recurring subscriptions (“ Subscriptions ”). Subscriptions are charged on a monthly or yearly basis (“ Subscription Period ”) for the recurring amount shown to you when you enrolled (“ Subscription Fee ”). If you subscribed during a promotion, used a coupon code, or otherwise received a discount, your Subscription will automatically renew for the full Subscription Fee at the end of the discount period. By enrolling in a Subscription, you authorize the Subscription Fee (and any applicable taxes) to be automatically charged to your designated payment method at the beginning of each Subscription Period until you cancel the Subscription or payments are otherwise ended because the Subscription was terminated for other reasons. You must cancel your Subscription at least 14 days before the end of your current Subscription Period in order to avoid being charged for the next Subscription Period. If you enrolled through the Tumblr Site, you can modify your payment method or cancel your Subscriptions at: www.tumblr.com/settings/subscriptions . If you enrolled using an in-app payment platform, such as through an Apple or Android device, you must modify your payment method or cancel your Subscriptions directly with that platform. 13. Domain Names We may work with third-party registrars to provide domain name services. When you register a domain on Tumblr or transfer an existing domain to Tumblr, the policies of the respective registry apply, and you become bound by the relevant registrar’s terms and conditions. Depending on the domain, you may be subject to the terms of the Automattic Domain Name Registration Agreement , or the Key-Systems GmbH Registration Agreement , in addition to this Agreement. When you register a domain, you’re presented with and agree to the applicable domain registration agreement. If you didn’t make a note of it, please see the Domain Registration Agreements page to determine which domain registration agreements apply to you and your domains. These registrar terms are incorporated by reference into this Agreement. Your domain is also subject to the policies of the Internet Corporation for Assigned Names and Numbers (“ICANN”), and you can read about your rights and responsibilities as a domain name registrant . When you register a domain, you’re required to provide complete and accurate registration information, and you must keep this information current. For more information about your domain registration, like associated fees, how to update your contact information, or what happens during the domain expiration process, please see the Domains support doc . 14. Warranty Disclaimer; Services Available on an "AS IS" Basis Your access to and use of the Services or any Content is at your own risk. YOU UNDERSTAND AND AGREE THAT THE SERVICES ARE PROVIDED TO YOU ON AN "AS IS" AND "AS AVAILABLE" BASIS. WITHOUT LIMITING THE FOREGOING, TO THE FULL EXTENT PERMITTED BY LAW, TUMBLR DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. Tumblr makes no representations or warranties of any kind with respect to the Services, including any representation or warranty that the use of the Services will (a) be timely, uninterrupted or error-free or operate in combination with any other hardware, software, system, or data, (b) meet your requirements or expectations, (c) be free from errors or that defects will be corrected, (d) be free of viruses or other harmful components; or (e) be entirely secure or that the information you share with us will be secure. Tumblr also makes no representations or warranties of any kind with respect to Content; User Content, in particular, is provided by and is solely the responsibility of, the Users providing that Content. No advice or information, whether oral or written, obtained from Tumblr or through the Services, will create any warranty not expressly made herein. 15. Time Limitation on Claims and Releases From Liability You agree that any claim you may have arising out of or related to this Agreement or your relationship with Tumblr must be filed within one year after such claim arose; otherwise, your claim is permanently barred. You further release, to the fullest extent permitted by law, Tumblr and its employees, agents, consultants, directors, shareholders, any other person or entity that directly or indirectly controls, is under common control with, or is directly or indirectly controlled by, Tumblr (the “Tumblr Affiliates”) from responsibility, liability, claims, demands, and/or damages (actual and consequential) of every kind and nature, known and unknown (including but not limited to claims of negligence), arising out of or related to the following: Disputes between Users, including those between you and other Users. The acts of third parties generally (i.e., individuals or entities who are not Tumblr or a Tumblr Affiliate), including third party sites and services. Disputes concerning any use of or action taken using your Account by you or a third party. Claims relating to the unauthorized access to any data communications relating to, or Content stored under or relating to, your Account, including but not limited to unauthorized interception, use, or alteration of such communications or your Content. For the sake of clarity, this includes any and all claims related to the security of your Account credentials. Claims relating to any face-to-face meetings in any way related to Tumblr at any venues (" Meetups "), including without limitation claims related to the actions or omissions of any Users or third parties who organize, attend, or are otherwise involved in any Meetups. Unless otherwise expressly disclosed in writing, Tumblr does not sponsor, oversee, or in any manner control Meetups. If you are a California resident, you waive California Civil Code § 1542, which says: "A general release does not extend to claims which the creditor does not know or suspect to exist in his favor at the time of executing the release, which if known by him must have materially affected his settlement with the debtor." 16. Limitation of Liability TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, TUMBLR AND THE TUMBLR AFFILIATES SHALL NOT BE LIABLE FOR: (A) ANY INDIRECT, INCIDENTAL, EXEMPLARY PUNITIVE, OR CONSEQUENTIAL DAMAGES OF ANY KIND WHATSOEVER; (B) LOSS OF: PROFITS, REVENUE, DATA, USE, GOODWILL, OR OTHER INTANGIBLE LOSSES; (C) DAMAGES RELATING TO YOUR ACCESS TO, USE OF, OR INABILITY TO ACCESS OR USE THE SERVICES; (D) DAMAGES RELATING TO ANY CONDUCT OR CONTENT OF ANY THIRD PARTY OR USER USING THE SERVICES, INCLUDING WITHOUT LIMITATION, DEFAMATORY, OFFENSIVE OR ILLEGAL CONDUCT OR CONTENT; AND/OR (E) DAMAGES IN ANY MANNER RELATING TO ANY CONTENT. THIS LIMITATION APPLIES TO ALL CLAIMS, WHETHER BASED ON WARRANTY, CONTRACT, TORT, OR ANY OTHER LEGAL THEORY, WHETHER OR NOT TUMBLR HAS BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGE, AND FURTHER WHERE A REMEDY SET FORTH HEREIN IS FOUND TO HAVE FAILED ITS ESSENTIAL PURPOSE. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE TOTAL LIABILITY OF TUMBLR AND THE TUMBLR AFFILIATES, FOR ANY CLAIM UNDER THIS AGREEMENT, INCLUDING FOR ANY IMPLIED WARRANTIES, IS LIMITED TO THE GREATER OF ONE HUNDRED DOLLARS (US $100.00) OR THE AMOUNT YOU PAID US TO USE THE APPLICABLE SERVICE(S). 17. Exclusions to Warranties and Limitation of Liability Some jurisdictions may not allow the exclusion of certain warranties or the exclusion/limitation of liability as set forth in Section 13 and 15, so the limitations above may not apply to you. 18. Termination Either party may terminate this Agreement at any time by notifying the other party. Tumblr may terminate or suspend your access to or ability to use any and all Services immediately, without prior notice or liability, for any reason or no reason, including but not limited to if you breach any of the terms or conditions of this Agreement. In particular, Tumblr may immediately terminate or suspend Accounts that have been flagged for repeat copyright infringement. Upon termination of your access to or ability to use a Service, including but not limited to suspension of your Account on a Service, your right to use or access that Service and any Content will immediately cease. All provisions of this Agreement that by their nature should survive termination shall survive termination, including, without limitation, ownership provisions, warranty disclaimers, and limitations of liability. Termination of your access to and use of the Services shall not relieve you of any obligations arising or accruing prior to such termination or limit any liability that you otherwise may have to Tumblr or any third party and shall not relieve you of your rights if you are a user in the European Economic Area which are described in the Privacy Policy. 19. Choice of Law and Venue You and Tumblr agree that we will resolve any claim or controversy at law or equity that arises out of this Agreement or the Services in accordance with this Section or as you and Tumblr otherwise agree in writing. Before resorting to formal dispute resolution, we strongly encourage you to contact us to seek a resolution. Law and Forum for Legal Disputes: This Agreement shall be governed in all respects by the laws of the State of New York as they apply to agreements entered into and to be performed entirely within New York between New York residents, without regard to conflict of law provisions. You agree that any claim or dispute you may have against Tumblr must be resolved exclusively by a state or federal court located in New York County, New York, except as otherwise agreed by the parties. You agree to submit to the personal jurisdiction of the courts located within New York County, New York for the purpose of litigating all such claims or disputes. If you are (a) a United States federal, state, or local government agency or body, (b) using the Services in your official capacity, and (c) legally unable to accept the clauses in this Section, then this Section doesn’t apply to you. For such entities, this Agreement and any related action will be governed by the laws of the United States of America, without regard to conflict of law provisions, and, in the absence of federal law and to the extent permitted under federal law, the laws of the State of New York, excluding choice of law. 20. Miscellaneous This Agreement, as modified from time to time, constitutes the entire agreement between you and Tumblr with respect to the subject matter hereof. This Agreement replaces all prior or contemporaneous understandings or agreements, written or oral, regarding the subject matter hereof and constitutes the entire and exclusive agreement between the parties. The failure of either party to exercise, in any way, any right provided for herein shall not be deemed a waiver of any further rights hereunder. If any provision of this Agreement is found to be unenforceable or invalid, that provision shall be limited or eliminated to the minimum extent necessary so that this Agreement shall otherwise remain enforceable and in full force and effect. This Agreement is not assignable, transferable, or sublicensable by you except with Tumblr's prior written consent. Tumblr may assign this Agreement in whole or in part at any time without your consent. No agency, partnership, joint controllership, joint venture, or employment is created as a result of this Agreement and you do not have any authority of any kind to bind Tumblr in any respect whatsoever. Any notice to Tumblr that is required or permitted by this Agreement shall be in writing and shall be deemed effective upon receipt, when delivered in person by nationally recognized overnight courier or mailed by first class, registered or certified mail, postage prepaid, to Tumblr, Inc. (Automattic) 60 29th Street #343 San Francisco, CA 94110 Attn: Legal Department 21. Special Provisions for Users Located Outside of the United States Tumblr provides global products and services and enables a global community for individuals to share and follow the things they love. Tumblr's servers and operations are, however, located in the United States, and Tumblr's policies and procedures are based on United States law. As such, the following provisions apply specifically to Users located outside of the United States: (1) you acknowledge that we will transfer, store, and process your information, including but not limited to User Content and any personal information, in the United States and/or other countries in order to provide you with the Services and perform this Agreement; and (2) if you are using the Services from a country embargoed by the United States, or are on the United States Treasury Department's list of "Specially Designated Nationals," you agree that you will not engage in financial transactions, or conduct any commercial activities using or through the Services (for example, purchasing Premium Themes). Submit an infringement notice 22. DMCA Copyright Policy Tumblr has adopted the following policy toward copyright infringement on the Services in accordance with the Digital Millennium Copyright Act (the " DMCA "). The address of Tumblr's Designated Agent for copyright takedown notices (" Designated Agent ") is listed below. You may submit a notice under the DMCA using our copyright notice form . Reporting Instances of Copyright Infringement: If you believe that Content residing or accessible on or through the Services infringes a copyright, please send a notice of copyright infringement containing the following information to the Designated Agent at the address below: Identification of the work or material being infringed. Identification of the material that is claimed to be infringing, including its location, with sufficient detail so that Tumblr is capable of finding it and verifying its existence. Contact information for the notifying party (the "Notifying Party"), including name, address, telephone number, and email address. A statement that the Notifying Party has a good faith belief that the material is not authorized by the copyright owner, its agent or law. A statement made under penalty of perjury that the information provided in the notice is accurate and that the Notifying Party is authorized to make the complaint on behalf of the copyright owner. A physical or electronic signature of a person authorized to act on behalf of the owner of the copyright that has been allegedly infringed. Please also note that the information provided in a notice of copyright infringement may be forwarded to the User who posted the allegedly infringing content. After removing material pursuant to a valid DMCA notice, Tumblr will immediately notify the User responsible for the allegedly infringing material that it has removed or disabled access to the material. Tumblr will terminate, under appropriate circumstances, the Accounts of Users who are repeat copyright infringers, and reserves the right, in its sole discretion, to terminate any User for actual or apparent copyright infringement. Submitting a DMCA Counter-Notification: If you believe you are the wrongful subject of a DMCA notification, you may file a counter-notification with Tumblr by providing the following information to the Designated Agent at the address below: The specific URLs of material that Tumblr has removed or to which Tumblr has disabled access. Your name, address, telephone number, and email address. A statement that you consent to the jurisdiction of Federal District Court for the judicial district in which your address is located (or the federal district courts located in New York County, New York if your address is outside of the United States), and that you will accept service of process from the person who provided the original DMCA notification or an agent of such person. The following statement: "I swear, under penalty of perjury, that I have a good faith belief that the material was removed or disabled as a result of a mistake or misidentification of the material to be removed or disabled." Your signature. Upon receipt of a valid counter-notification, Tumblr will forward it to Notifying Party who submitted the original DMCA notification. The original Notifying Party (or the copyright holder he or she represents) will then have ten (10) days to notify us that he or she has filed legal action relating to the allegedly infringing material. If Tumblr does not receive any such notification within ten (10) days, we may restore the material to the Services. Designated Agent Tumblr, Inc. (Automattic) 60 29th Street #343 San Francisco, CA 94110 Attn: Copyright Agent Email: dmca@tumblr.com Copyright notice form: https://www.tumblr.com/dmca 23. Open Source Disclosures You can find disclosures related to our use of open source software packages at the following locations: https://www.tumblr.com/policy/ios-credits https://www.tumblr.com/policy/android-credits https://www.tumblr.com/policy/web-credits Link to Prior Versions You will find prior versions of our Terms of Service on GitHub, which will allow you to compare historical versions and see which terms have been updated. https://github.com/tumblr/policy/commits/master/terms-of-service.txt About Apps Tips Logo Business Buttons Press Info Jobs Developers Terms Accessibility Copyright Privacy Guidelines Security Global Advertising © Tumblr, Inc. Help About Apps Developers Themes Jobs Legal Terms Copyright Privacy 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:33 |
https://gitstar-ranking.com/EbookFoundation | EbookFoundation - Gitstar Ranking Gitstar Ranking Users Organizations Repositories Rankings Users Organizations Repositories Sign in with GitHub EbookFoundation Star 383235 Rank 18 Go to GitHub Fetched on 2026/01/09 08:52 37 Repositories free-programming-books 380163 free-science-books 2080 free-programming-books-search 357 ebookfoundation.github.io 281 regluit 59 capstone-projects 55 without-a-net 37 StandardEbooks-tools 20 river-of-ebooks 20 zimgutenberg 18 free-programming-books-parser 16 reading-lists 14 fef-questionnaire 14 bookshelf-management 14 readthedocs.org 9 library-privacy-pledge 8 alt-text 7 regluit-provisioning 6 ItemOrientedSurvey 6 doab-check 6 oapen-suggestion-service 5 gutenbergsite 5 bardo-copyright-db 5 autocat3 4 altpoet 4 thoth-wiki 3 cce-search-ansible 3 alt-text-frontend 3 pgmarc 2 cce-search-prototype 2 alt-text-editor 2 alt-text-backend 2 thoth 1 roe-pressbooks 1 puppeteer-tools 1 donor-calendar 1 .github 1 Released by @k0kubun in December 2014. Fork me on GitHub . | 2026-01-13T09:29:33 |
https://gitstar-ranking.com/symfony | symfony - Gitstar Ranking Gitstar Ranking Users Organizations Repositories Rankings Users Organizations Repositories Sign in with GitHub symfony Star 356021 Rank 21 Go to GitHub Fetched on 2026/01/09 03:42 385 Repositories symfony 30880 console 9833 http-foundation 8659 event-dispatcher 8561 finder 8465 http-kernel 8137 thanks 8101 polyfill-mbstring 7855 routing 7632 process 7470 css-selector 7451 var-dumper 7450 debug 7212 translation 6620 polyfill-php72 4758 filesystem 4653 config 4279 flex 4222 cache 4172 dependency-injection 4167 polyfill-ctype 4050 dom-crawler 4037 contracts 3940 yaml 3848 dotenv 3799 framework-bundle 3574 event-dispatcher-contracts 3441 maker-bundle 3396 polyfill-intl-idn 3368 options-resolver 3243 doctrine-bridge 3234 polyfill-php70 3201 asset 3163 panther 3055 browser-kit 3022 monolog-bundle 2924 expression-language 2848 mime 2834 property-access 2823 stopwatch 2822 polyfill 2798 form 2779 error-handler 2679 validator 2677 intl 2644 service-contracts 2631 translation-contracts 2607 polyfill-intl-icu 2603 monolog-bridge 2597 demo 2584 1 2 3 4 5 … › Released by @k0kubun in December 2014. Fork me on GitHub . | 2026-01-13T09:29:33 |
https://m.youtube.com/channel/UCxLxR_oW-NAmChIcSkAyZGQ | FreeBSD - YouTube var ytInitialData = {"responseContext":{"serviceTrackingParams":[{"service":"GFEEDBACK","params":[{"key":"route","value":"channel."},{"key":"is_owner","value":"false"},{"key":"is_alc_surface","value":"false"},{"key":"browse_id","value":"UCxLxR_oW-NAmChIcSkAyZGQ"},{"key":"browse_id_prefix","value":""},{"key":"logged_in","value":"0"},{"key":"visitor_data","value":"CgtwRWwxMG5JX1dlMCj7oJjLBjIKCgJLUhIEGgAgLA%3D%3D"}]},{"service":"GOOGLE_HELP","params":[{"key":"browse_id","value":"UCxLxR_oW-NAmChIcSkAyZGQ"},{"key":"browse_id_prefix","value":""}]},{"service":"CSI","params":[{"key":"c","value":"WEB"},{"key":"cver","value":"2.20260109.01.00"},{"key":"yt_li","value":"0"},{"key":"GetChannelPage_rid","value":"0xca93ba90b4d5bb76"}]},{"service":"GUIDED_HELP","params":[{"key":"logged_in","value":"0"}]},{"service":"ECATCHER","params":[{"key":"client.version","value":"2.20260109"},{"key":"client.name","value":"WEB"}]}],"maxAgeSeconds":300,"mainAppWebResponseContext":{"loggedOut":true,"trackingParam":"kx_fmPxhoPZR7WdQMq1VM0Wzw22qQ8tvcmv9wdjh4BDL8BwRgkuswmIBwOcCE59TDtslLKPQ-SS"},"webResponseContextExtensionData":{"webResponseContextPreloadData":{"preloadMessageNames":["pageHeaderRenderer","pageHeaderViewModel","imageBannerViewModel","dynamicTextViewModel","decoratedAvatarViewModel","avatarViewModel","contentMetadataViewModel","flexibleActionsViewModel","buttonViewModel","modalWithTitleAndButtonRenderer","buttonRenderer","descriptionPreviewViewModel","engagementPanelSectionListRenderer","engagementPanelTitleHeaderRenderer","sectionListRenderer","itemSectionRenderer","continuationItemRenderer","attributionViewModel","channelMetadataRenderer","twoColumnBrowseResultsRenderer","tabRenderer","shelfRenderer","horizontalListRenderer","gridVideoRenderer","thumbnailOverlayTimeStatusRenderer","thumbnailOverlayToggleButtonRenderer","thumbnailOverlayNowPlayingRenderer","menuRenderer","menuServiceItemRenderer","menuNavigationItemRenderer","unifiedSharePanelRenderer","lockupViewModel","collectionThumbnailViewModel","thumbnailViewModel","thumbnailOverlayBadgeViewModel","thumbnailBadgeViewModel","thumbnailHoverOverlayViewModel","lockupMetadataViewModel","reelShelfRenderer","shortsLockupViewModel","reelPlayerOverlayRenderer","sheetViewModel","listViewModel","listItemViewModel","postRenderer","backstageImageRenderer","commentActionButtonsRenderer","toggleButtonRenderer","hintRenderer","bubbleHintRenderer","pollRenderer","expandableTabRenderer","desktopTopbarRenderer","topbarLogoRenderer","fusionSearchboxRenderer","topbarMenuButtonRenderer","multiPageMenuRenderer","hotkeyDialogRenderer","hotkeyDialogSectionRenderer","hotkeyDialogSectionOptionRenderer","voiceSearchDialogRenderer","microformatDataRenderer"]},"ytConfigData":{"visitorData":"CgtwRWwxMG5JX1dlMCj7oJjLBjIKCgJLUhIEGgAgLA%3D%3D","rootVisualElementType":3611},"hasDecorated":true}},"contents":{"twoColumnBrowseResultsRenderer":{"tabs":[{"tabRenderer":{"endpoint":{"clickTrackingParams":"CCcQ8JMBGAUiEwittO2HmoiSAxUqRfUFHbSpNSbKAQR_-A9v","commandMetadata":{"webCommandMetadata":{"url":"/@FreeBSDProject/featured","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCxLxR_oW-NAmChIcSkAyZGQ","params":"EghmZWF0dXJlZPIGBAoCMgA%3D","canonicalBaseUrl":"/@FreeBSDProject"}},"title":"홈","selected":true,"content":{"sectionListRenderer":{"contents":[{"itemSectionRenderer":{"contents":[{"shelfRenderer":{"title":{"runs":[{"text":"동영상","navigationEndpoint":{"clickTrackingParams":"CLMCENwcGAAiEwittO2HmoiSAxUqRfUFHbSpNSbKAQR_-A9v","commandMetadata":{"webCommandMetadata":{"url":"/@FreeBSDProject/videos?view=0\u0026sort=dd\u0026shelf_id=2","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCxLxR_oW-NAmChIcSkAyZGQ","params":"EgZ2aWRlb3MYAyAAcALyBg0KCzoEIgIIBKIBAggB","canonicalBaseUrl":"/@FreeBSDProject"}}}]},"endpoint":{"clickTrackingParams":"CLMCENwcGAAiEwittO2HmoiSAxUqRfUFHbSpNSbKAQR_-A9v","commandMetadata":{"webCommandMetadata":{"url":"/@FreeBSDProject/videos?view=0\u0026sort=dd\u0026shelf_id=2","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCxLxR_oW-NAmChIcSkAyZGQ","params":"EgZ2aWRlb3MYAyAAcALyBg0KCzoEIgIIBKIBAggB","canonicalBaseUrl":"/@FreeBSDProject"}},"content":{"horizontalListRenderer":{"items":[{"gridVideoRenderer":{"videoId":"q4PNSeNXEww","thumbnail":{"thumbnails":[{"url":"https://i.ytimg.com/vi/q4PNSeNXEww/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLBogtILjPWWpTE1Z9NnwynkRc_F0w","width":168,"height":94},{"url":"https://i.ytimg.com/vi/q4PNSeNXEww/hqdefault.jpg?sqp=-oaymwEiCMQBEG5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLDO7OIk0AfkT4m80I3wsckc40TFsQ","width":196,"height":110},{"url":"https://i.ytimg.com/vi/q4PNSeNXEww/hqdefault.jpg?sqp=-oaymwEjCPYBEIoBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLBSKCIBHmzTZm0xdTmhgPH39StkMA","width":246,"height":138},{"url":"https://i.ytimg.com/vi/q4PNSeNXEww/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLBOdy52e4MJW_3V9vSC345y0KN3BQ","width":336,"height":188}]},"title":{"accessibility":{"accessibilityData":{"label":"FreeBSD에 모든 윈도우 관리자 설치하기 10분 3초"}},"simpleText":"FreeBSD에 모든 윈도우 관리자 설치하기"},"publishedTimeText":{"simpleText":"3주 전"},"viewCountText":{"simpleText":"조회수 12,571회"},"navigationEndpoint":{"clickTrackingParams":"CPkCEJQ1GAAiEwittO2HmoiSAxUqRfUFHbSpNSYyCmctaGlnaC1jcnZaGFVDeEx4Ul9vVy1OQW1DaEljU2tBeVpHUZoBBRDyOBhmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=q4PNSeNXEww","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"q4PNSeNXEww","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr2---sn-ab02a0nfpgxapox-bh2zz.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026oreouc=1\u0026id=ab83cd49e357130c\u0026ip=1.208.108.242\u0026initcwndbps=3540000\u0026mt=1768296063\u0026oweuc="}}}}},"trackingParams":"CPkCEJQ1GAAiEwittO2HmoiSAxUqRfUFHbSpNSZAjKbcmp6p88GrAQ==","shortViewCountText":{"accessibility":{"accessibilityData":{"label":"조회수 1.2만회"}},"simpleText":"조회수 1.2만회"},"menu":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"현재 재생목록에 추가"}]},"icon":{"iconType":"ADD_TO_QUEUE_TAIL"},"serviceEndpoint":{"clickTrackingParams":"CP4CEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CP4CEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"q4PNSeNXEww","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CP4CEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["q4PNSeNXEww"],"params":"CAQ%3D"}},"videoIds":["q4PNSeNXEww"],"videoCommand":{"clickTrackingParams":"CP4CEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=q4PNSeNXEww","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"q4PNSeNXEww","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr2---sn-ab02a0nfpgxapox-bh2zz.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026oreouc=1\u0026id=ab83cd49e357130c\u0026ip=1.208.108.242\u0026initcwndbps=3540000\u0026mt=1768296063\u0026oweuc="}}}}}}}]}},"trackingParams":"CP4CEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUm"}},{"menuNavigationItemRenderer":{"text":{"runs":[{"text":"재생목록에 저장"}]},"icon":{"iconType":"BOOKMARK_BORDER"},"navigationEndpoint":{"clickTrackingParams":"CP0CEJSsCRgGIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CP0CEJSsCRgGIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","showSheetCommand":{"panelLoadingStrategy":{"requestTemplate":{"panelId":"PAadd_to_playlist","params":"-gYNCgtxNFBOU2VOWEV3dw%3D%3D"}}}}}},"trackingParams":"CP0CEJSsCRgGIhMIrbTth5qIkgMVKkX1BR20qTUm"}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"공유"}]},"icon":{"iconType":"SHARE"},"serviceEndpoint":{"clickTrackingParams":"CPkCEJQ1GAAiEwittO2HmoiSAxUqRfUFHbSpNSbKAQR_-A9v","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtxNFBOU2VOWEV3dw%3D%3D","commands":[{"clickTrackingParams":"CPkCEJQ1GAAiEwittO2HmoiSAxUqRfUFHbSpNSbKAQR_-A9v","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CPwCEI5iIhMIrbTth5qIkgMVKkX1BR20qTUm","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}},"trackingParams":"CPkCEJQ1GAAiEwittO2HmoiSAxUqRfUFHbSpNSY=","hasSeparator":true}}],"trackingParams":"CPkCEJQ1GAAiEwittO2HmoiSAxUqRfUFHbSpNSY=","accessibility":{"accessibilityData":{"label":"작업 메뉴"}}}},"thumbnailOverlays":[{"thumbnailOverlayTimeStatusRenderer":{"text":{"accessibility":{"accessibilityData":{"label":"10분 3초"}},"simpleText":"10:03"},"style":"DEFAULT"}},{"thumbnailOverlayToggleButtonRenderer":{"isToggled":false,"untoggledIcon":{"iconType":"WATCH_LATER"},"toggledIcon":{"iconType":"CHECK"},"untoggledTooltip":"나중에 볼 동영상","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"CPsCEPnnAxgBIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"q4PNSeNXEww","action":"ACTION_ADD_VIDEO"}]}},"toggledServiceEndpoint":{"clickTrackingParams":"CPsCEPnnAxgBIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"q4PNSeNXEww"}]}},"untoggledAccessibility":{"accessibilityData":{"label":"나중에 볼 동영상"}},"toggledAccessibility":{"accessibilityData":{"label":"추가됨"}},"trackingParams":"CPsCEPnnAxgBIhMIrbTth5qIkgMVKkX1BR20qTUm"}},{"thumbnailOverlayToggleButtonRenderer":{"untoggledIcon":{"iconType":"ADD_TO_QUEUE_TAIL"},"toggledIcon":{"iconType":"PLAYLIST_ADD_CHECK"},"untoggledTooltip":"현재 재생목록에 추가","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"CPoCEMfsBBgCIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CPoCEMfsBBgCIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"q4PNSeNXEww","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CPoCEMfsBBgCIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["q4PNSeNXEww"],"params":"CAQ%3D"}},"videoIds":["q4PNSeNXEww"]}}]}},"untoggledAccessibility":{"accessibilityData":{"label":"현재 재생목록에 추가"}},"toggledAccessibility":{"accessibilityData":{"label":"추가됨"}},"trackingParams":"CPoCEMfsBBgCIhMIrbTth5qIkgMVKkX1BR20qTUm"}},{"thumbnailOverlayNowPlayingRenderer":{"text":{"runs":[{"text":"지금 재생 중"}]}}}]}},{"gridVideoRenderer":{"videoId":"vbWOLzGDa4I","thumbnail":{"thumbnails":[{"url":"https://i.ytimg.com/vi/vbWOLzGDa4I/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLBAfRUpmCEW3hL4SkPodUPHtmVwdQ","width":168,"height":94},{"url":"https://i.ytimg.com/vi/vbWOLzGDa4I/hqdefault.jpg?sqp=-oaymwEiCMQBEG5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLCEbD2I3oAF0hye4gMgV4wDN8IUvw","width":196,"height":110},{"url":"https://i.ytimg.com/vi/vbWOLzGDa4I/hqdefault.jpg?sqp=-oaymwEjCPYBEIoBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLDb1IR7vxQNbIeky76Z2pd7LEGtwQ","width":246,"height":138},{"url":"https://i.ytimg.com/vi/vbWOLzGDa4I/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLAYipmgauxkdA4hCVXjfaVFNahR6Q","width":336,"height":188}]},"title":{"accessibility":{"accessibilityData":{"label":"FreeBSD 데스크톱 설치 프로그램 기술 미리보기 5분 26초"}},"simpleText":"FreeBSD 데스크톱 설치 프로그램 기술 미리보기"},"publishedTimeText":{"simpleText":"2개월 전"},"viewCountText":{"simpleText":"조회수 48,458회"},"navigationEndpoint":{"clickTrackingParams":"CPMCEJQ1GAEiEwittO2HmoiSAxUqRfUFHbSpNSYyCmctaGlnaC1jcnZaGFVDeEx4Ul9vVy1OQW1DaEljU2tBeVpHUZoBBRDyOBhmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=vbWOLzGDa4I","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"vbWOLzGDa4I","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2ez.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026oreouc=1\u0026id=bdb58e2f31836b82\u0026ip=1.208.108.242\u0026initcwndbps=3722500\u0026mt=1768296063\u0026oweuc="}}}}},"trackingParams":"CPMCEJQ1GAEiEwittO2HmoiSAxUqRfUFHbSpNSZAgteNjPPF49q9AQ==","shortViewCountText":{"accessibility":{"accessibilityData":{"label":"조회수 4.8만회"}},"simpleText":"조회수 4.8만회"},"menu":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"현재 재생목록에 추가"}]},"icon":{"iconType":"ADD_TO_QUEUE_TAIL"},"serviceEndpoint":{"clickTrackingParams":"CPgCEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CPgCEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"vbWOLzGDa4I","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CPgCEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["vbWOLzGDa4I"],"params":"CAQ%3D"}},"videoIds":["vbWOLzGDa4I"],"videoCommand":{"clickTrackingParams":"CPgCEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=vbWOLzGDa4I","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"vbWOLzGDa4I","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2ez.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026oreouc=1\u0026id=bdb58e2f31836b82\u0026ip=1.208.108.242\u0026initcwndbps=3722500\u0026mt=1768296063\u0026oweuc="}}}}}}}]}},"trackingParams":"CPgCEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUm"}},{"menuNavigationItemRenderer":{"text":{"runs":[{"text":"재생목록에 저장"}]},"icon":{"iconType":"BOOKMARK_BORDER"},"navigationEndpoint":{"clickTrackingParams":"CPcCEJSsCRgGIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CPcCEJSsCRgGIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","showSheetCommand":{"panelLoadingStrategy":{"requestTemplate":{"panelId":"PAadd_to_playlist","params":"-gYNCgt2YldPTHpHRGE0SQ%3D%3D"}}}}}},"trackingParams":"CPcCEJSsCRgGIhMIrbTth5qIkgMVKkX1BR20qTUm"}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"공유"}]},"icon":{"iconType":"SHARE"},"serviceEndpoint":{"clickTrackingParams":"CPMCEJQ1GAEiEwittO2HmoiSAxUqRfUFHbSpNSbKAQR_-A9v","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"Cgt2YldPTHpHRGE0SQ%3D%3D","commands":[{"clickTrackingParams":"CPMCEJQ1GAEiEwittO2HmoiSAxUqRfUFHbSpNSbKAQR_-A9v","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CPYCEI5iIhMIrbTth5qIkgMVKkX1BR20qTUm","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}},"trackingParams":"CPMCEJQ1GAEiEwittO2HmoiSAxUqRfUFHbSpNSY=","hasSeparator":true}}],"trackingParams":"CPMCEJQ1GAEiEwittO2HmoiSAxUqRfUFHbSpNSY=","accessibility":{"accessibilityData":{"label":"작업 메뉴"}}}},"thumbnailOverlays":[{"thumbnailOverlayTimeStatusRenderer":{"text":{"accessibility":{"accessibilityData":{"label":"5분 26초"}},"simpleText":"5:26"},"style":"DEFAULT"}},{"thumbnailOverlayToggleButtonRenderer":{"isToggled":false,"untoggledIcon":{"iconType":"WATCH_LATER"},"toggledIcon":{"iconType":"CHECK"},"untoggledTooltip":"나중에 볼 동영상","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"CPUCEPnnAxgBIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"vbWOLzGDa4I","action":"ACTION_ADD_VIDEO"}]}},"toggledServiceEndpoint":{"clickTrackingParams":"CPUCEPnnAxgBIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"vbWOLzGDa4I"}]}},"untoggledAccessibility":{"accessibilityData":{"label":"나중에 볼 동영상"}},"toggledAccessibility":{"accessibilityData":{"label":"추가됨"}},"trackingParams":"CPUCEPnnAxgBIhMIrbTth5qIkgMVKkX1BR20qTUm"}},{"thumbnailOverlayToggleButtonRenderer":{"untoggledIcon":{"iconType":"ADD_TO_QUEUE_TAIL"},"toggledIcon":{"iconType":"PLAYLIST_ADD_CHECK"},"untoggledTooltip":"현재 재생목록에 추가","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"CPQCEMfsBBgCIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CPQCEMfsBBgCIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"vbWOLzGDa4I","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CPQCEMfsBBgCIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["vbWOLzGDa4I"],"params":"CAQ%3D"}},"videoIds":["vbWOLzGDa4I"]}}]}},"untoggledAccessibility":{"accessibilityData":{"label":"현재 재생목록에 추가"}},"toggledAccessibility":{"accessibilityData":{"label":"추가됨"}},"trackingParams":"CPQCEMfsBBgCIhMIrbTth5qIkgMVKkX1BR20qTUm"}},{"thumbnailOverlayNowPlayingRenderer":{"text":{"runs":[{"text":"지금 재생 중"}]}}}]}},{"gridVideoRenderer":{"videoId":"HV-wUUzRCMo","thumbnail":{"thumbnails":[{"url":"https://i.ytimg.com/vi/HV-wUUzRCMo/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLAY1-DO1iFxjGIb9A9mEVmiEIZKkQ","width":168,"height":94},{"url":"https://i.ytimg.com/vi/HV-wUUzRCMo/hqdefault.jpg?sqp=-oaymwEiCMQBEG5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLBhaL6mgD-vUgZKoGVs2pLshUqeKA","width":196,"height":110},{"url":"https://i.ytimg.com/vi/HV-wUUzRCMo/hqdefault.jpg?sqp=-oaymwEjCPYBEIoBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLBSDZoAl64PQEykUiJT2vZa1kxMDQ","width":246,"height":138},{"url":"https://i.ytimg.com/vi/HV-wUUzRCMo/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLDQD9xgvIptWqT8xn1NBkBeoiHbxg","width":336,"height":188}]},"title":{"accessibility":{"accessibilityData":{"label":"FreeBSD에서 Linux 컨테이너를 실행하세요! 5분 40초"}},"simpleText":"FreeBSD에서 Linux 컨테이너를 실행하세요!"},"publishedTimeText":{"simpleText":"2개월 전"},"viewCountText":{"simpleText":"조회수 12,032회"},"navigationEndpoint":{"clickTrackingParams":"CO0CEJQ1GAIiEwittO2HmoiSAxUqRfUFHbSpNSYyCmctaGlnaC1jcnZaGFVDeEx4Ul9vVy1OQW1DaEljU2tBeVpHUZoBBRDyOBhmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=HV-wUUzRCMo","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"HV-wUUzRCMo","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2s6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026oreouc=1\u0026id=1d5fb0514cd108ca\u0026ip=1.208.108.242\u0026initcwndbps=3976250\u0026mt=1768296063\u0026oweuc="}}}}},"trackingParams":"CO0CEJQ1GAIiEwittO2HmoiSAxUqRfUFHbSpNSZAypHE5pSK7K8d","shortViewCountText":{"accessibility":{"accessibilityData":{"label":"조회수 1.2만회"}},"simpleText":"조회수 1.2만회"},"menu":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"현재 재생목록에 추가"}]},"icon":{"iconType":"ADD_TO_QUEUE_TAIL"},"serviceEndpoint":{"clickTrackingParams":"CPICEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CPICEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"HV-wUUzRCMo","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CPICEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["HV-wUUzRCMo"],"params":"CAQ%3D"}},"videoIds":["HV-wUUzRCMo"],"videoCommand":{"clickTrackingParams":"CPICEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=HV-wUUzRCMo","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"HV-wUUzRCMo","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2s6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026oreouc=1\u0026id=1d5fb0514cd108ca\u0026ip=1.208.108.242\u0026initcwndbps=3976250\u0026mt=1768296063\u0026oweuc="}}}}}}}]}},"trackingParams":"CPICEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUm"}},{"menuNavigationItemRenderer":{"text":{"runs":[{"text":"재생목록에 저장"}]},"icon":{"iconType":"BOOKMARK_BORDER"},"navigationEndpoint":{"clickTrackingParams":"CPECEJSsCRgGIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CPECEJSsCRgGIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","showSheetCommand":{"panelLoadingStrategy":{"requestTemplate":{"panelId":"PAadd_to_playlist","params":"-gYNCgtIVi13VVV6UkNNbw%3D%3D"}}}}}},"trackingParams":"CPECEJSsCRgGIhMIrbTth5qIkgMVKkX1BR20qTUm"}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"공유"}]},"icon":{"iconType":"SHARE"},"serviceEndpoint":{"clickTrackingParams":"CO0CEJQ1GAIiEwittO2HmoiSAxUqRfUFHbSpNSbKAQR_-A9v","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtIVi13VVV6UkNNbw%3D%3D","commands":[{"clickTrackingParams":"CO0CEJQ1GAIiEwittO2HmoiSAxUqRfUFHbSpNSbKAQR_-A9v","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CPACEI5iIhMIrbTth5qIkgMVKkX1BR20qTUm","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}},"trackingParams":"CO0CEJQ1GAIiEwittO2HmoiSAxUqRfUFHbSpNSY=","hasSeparator":true}}],"trackingParams":"CO0CEJQ1GAIiEwittO2HmoiSAxUqRfUFHbSpNSY=","accessibility":{"accessibilityData":{"label":"작업 메뉴"}}}},"thumbnailOverlays":[{"thumbnailOverlayTimeStatusRenderer":{"text":{"accessibility":{"accessibilityData":{"label":"5분 40초"}},"simpleText":"5:40"},"style":"DEFAULT"}},{"thumbnailOverlayToggleButtonRenderer":{"isToggled":false,"untoggledIcon":{"iconType":"WATCH_LATER"},"toggledIcon":{"iconType":"CHECK"},"untoggledTooltip":"나중에 볼 동영상","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"CO8CEPnnAxgBIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"HV-wUUzRCMo","action":"ACTION_ADD_VIDEO"}]}},"toggledServiceEndpoint":{"clickTrackingParams":"CO8CEPnnAxgBIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"HV-wUUzRCMo"}]}},"untoggledAccessibility":{"accessibilityData":{"label":"나중에 볼 동영상"}},"toggledAccessibility":{"accessibilityData":{"label":"추가됨"}},"trackingParams":"CO8CEPnnAxgBIhMIrbTth5qIkgMVKkX1BR20qTUm"}},{"thumbnailOverlayToggleButtonRenderer":{"untoggledIcon":{"iconType":"ADD_TO_QUEUE_TAIL"},"toggledIcon":{"iconType":"PLAYLIST_ADD_CHECK"},"untoggledTooltip":"현재 재생목록에 추가","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"CO4CEMfsBBgCIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CO4CEMfsBBgCIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"HV-wUUzRCMo","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CO4CEMfsBBgCIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["HV-wUUzRCMo"],"params":"CAQ%3D"}},"videoIds":["HV-wUUzRCMo"]}}]}},"untoggledAccessibility":{"accessibilityData":{"label":"현재 재생목록에 추가"}},"toggledAccessibility":{"accessibilityData":{"label":"추가됨"}},"trackingParams":"CO4CEMfsBBgCIhMIrbTth5qIkgMVKkX1BR20qTUm"}},{"thumbnailOverlayNowPlayingRenderer":{"text":{"runs":[{"text":"지금 재생 중"}]}}}]}},{"gridVideoRenderer":{"videoId":"83lM4NZmheA","thumbnail":{"thumbnails":[{"url":"https://i.ytimg.com/vi/83lM4NZmheA/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLDVgW_lx2hGEWZhtZJBQ-Kuxg2msw","width":168,"height":94},{"url":"https://i.ytimg.com/vi/83lM4NZmheA/hqdefault.jpg?sqp=-oaymwEiCMQBEG5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLDzJNOjeP8hAj61wOnGHA_6EM8XGw","width":196,"height":110},{"url":"https://i.ytimg.com/vi/83lM4NZmheA/hqdefault.jpg?sqp=-oaymwEjCPYBEIoBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLBUpJetrOj6a-Rs2HNTLCkh1uz0KQ","width":246,"height":138},{"url":"https://i.ytimg.com/vi/83lM4NZmheA/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLB5iT3Biy6oyN4aGsvzAcHNp-H78g","width":336,"height":188}]},"title":{"accessibility":{"accessibilityData":{"label":"Introducing the FreeBSD Meetings Channel! 58초"}},"simpleText":"Introducing the FreeBSD Meetings Channel!"},"publishedTimeText":{"simpleText":"3개월 전"},"viewCountText":{"simpleText":"조회수 798회"},"navigationEndpoint":{"clickTrackingParams":"COcCEJQ1GAMiEwittO2HmoiSAxUqRfUFHbSpNSYyCmctaGlnaC1jcnZaGFVDeEx4Ul9vVy1OQW1DaEljU2tBeVpHUZoBBRDyOBhmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=83lM4NZmheA","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"83lM4NZmheA","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr4---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026oreouc=1\u0026id=f3794ce0d66685e0\u0026ip=1.208.108.242\u0026initcwndbps=4535000\u0026mt=1768296063\u0026oweuc="}}}}},"trackingParams":"COcCEJQ1GAMiEwittO2HmoiSAxUqRfUFHbSpNSZA4Iuas42c07zzAQ==","shortViewCountText":{"accessibility":{"accessibilityData":{"label":"조회수 798회"}},"simpleText":"조회수 798회"},"menu":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"현재 재생목록에 추가"}]},"icon":{"iconType":"ADD_TO_QUEUE_TAIL"},"serviceEndpoint":{"clickTrackingParams":"COwCEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"COwCEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"83lM4NZmheA","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"COwCEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["83lM4NZmheA"],"params":"CAQ%3D"}},"videoIds":["83lM4NZmheA"],"videoCommand":{"clickTrackingParams":"COwCEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=83lM4NZmheA","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"83lM4NZmheA","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr4---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026oreouc=1\u0026id=f3794ce0d66685e0\u0026ip=1.208.108.242\u0026initcwndbps=4535000\u0026mt=1768296063\u0026oweuc="}}}}}}}]}},"trackingParams":"COwCEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUm"}},{"menuNavigationItemRenderer":{"text":{"runs":[{"text":"재생목록에 저장"}]},"icon":{"iconType":"BOOKMARK_BORDER"},"navigationEndpoint":{"clickTrackingParams":"COsCEJSsCRgGIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"COsCEJSsCRgGIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","showSheetCommand":{"panelLoadingStrategy":{"requestTemplate":{"panelId":"PAadd_to_playlist","params":"-gYNCgs4M2xNNE5abWhlQQ%3D%3D"}}}}}},"trackingParams":"COsCEJSsCRgGIhMIrbTth5qIkgMVKkX1BR20qTUm"}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"공유"}]},"icon":{"iconType":"SHARE"},"serviceEndpoint":{"clickTrackingParams":"COcCEJQ1GAMiEwittO2HmoiSAxUqRfUFHbSpNSbKAQR_-A9v","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"Cgs4M2xNNE5abWhlQQ%3D%3D","commands":[{"clickTrackingParams":"COcCEJQ1GAMiEwittO2HmoiSAxUqRfUFHbSpNSbKAQR_-A9v","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"COoCEI5iIhMIrbTth5qIkgMVKkX1BR20qTUm","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}},"trackingParams":"COcCEJQ1GAMiEwittO2HmoiSAxUqRfUFHbSpNSY=","hasSeparator":true}}],"trackingParams":"COcCEJQ1GAMiEwittO2HmoiSAxUqRfUFHbSpNSY=","accessibility":{"accessibilityData":{"label":"작업 메뉴"}}}},"thumbnailOverlays":[{"thumbnailOverlayTimeStatusRenderer":{"text":{"accessibility":{"accessibilityData":{"label":"58초"}},"simpleText":"0:58"},"style":"DEFAULT"}},{"thumbnailOverlayToggleButtonRenderer":{"isToggled":false,"untoggledIcon":{"iconType":"WATCH_LATER"},"toggledIcon":{"iconType":"CHECK"},"untoggledTooltip":"나중에 볼 동영상","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"COkCEPnnAxgBIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"83lM4NZmheA","action":"ACTION_ADD_VIDEO"}]}},"toggledServiceEndpoint":{"clickTrackingParams":"COkCEPnnAxgBIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"83lM4NZmheA"}]}},"untoggledAccessibility":{"accessibilityData":{"label":"나중에 볼 동영상"}},"toggledAccessibility":{"accessibilityData":{"label":"추가됨"}},"trackingParams":"COkCEPnnAxgBIhMIrbTth5qIkgMVKkX1BR20qTUm"}},{"thumbnailOverlayToggleButtonRenderer":{"untoggledIcon":{"iconType":"ADD_TO_QUEUE_TAIL"},"toggledIcon":{"iconType":"PLAYLIST_ADD_CHECK"},"untoggledTooltip":"현재 재생목록에 추가","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"COgCEMfsBBgCIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"COgCEMfsBBgCIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"83lM4NZmheA","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"COgCEMfsBBgCIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["83lM4NZmheA"],"params":"CAQ%3D"}},"videoIds":["83lM4NZmheA"]}}]}},"untoggledAccessibility":{"accessibilityData":{"label":"현재 재생목록에 추가"}},"toggledAccessibility":{"accessibilityData":{"label":"추가됨"}},"trackingParams":"COgCEMfsBBgCIhMIrbTth5qIkgMVKkX1BR20qTUm"}},{"thumbnailOverlayNowPlayingRenderer":{"text":{"runs":[{"text":"지금 재생 중"}]}}}]}},{"gridVideoRenderer":{"videoId":"y82-t1tDLWg","thumbnail":{"thumbnails":[{"url":"https://i.ytimg.com/vi/y82-t1tDLWg/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLDcpxtNBSnS3sltF3Z2wAyIJ4FCnw","width":168,"height":94},{"url":"https://i.ytimg.com/vi/y82-t1tDLWg/hqdefault.jpg?sqp=-oaymwEiCMQBEG5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLD1lxLUesbxlLoEVgkWhqp5wwY40A","width":196,"height":110},{"url":"https://i.ytimg.com/vi/y82-t1tDLWg/hqdefault.jpg?sqp=-oaymwEjCPYBEIoBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLC_mMWZ2wH-pdrprmzuHtHNFmuHSw","width":246,"height":138},{"url":"https://i.ytimg.com/vi/y82-t1tDLWg/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLABsdTxBo2EF9UwlJ57C7ATu9dP1w","width":336,"height":188}]},"title":{"accessibility":{"accessibilityData":{"label":"Rust Device Drivers on FreeBSD | Google Summer of Code 5분 44초"}},"simpleText":"Rust Device Drivers on FreeBSD | Google Summer of Code"},"publishedTimeText":{"simpleText":"3개월 전"},"viewCountText":{"simpleText":"조회수 1,579회"},"navigationEndpoint":{"clickTrackingParams":"COECEJQ1GAQiEwittO2HmoiSAxUqRfUFHbSpNSYyCmctaGlnaC1jcnZaGFVDeEx4Ul9vVy1OQW1DaEljU2tBeVpHUZoBBRDyOBhmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=y82-t1tDLWg","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"y82-t1tDLWg","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr2---sn-ab02a0nfpgxapox-bh26z.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026oreouc=1\u0026id=cbcdbeb75b432d68\u0026ip=1.208.108.242\u0026initcwndbps=4218750\u0026mt=1768296063\u0026oweuc="}}}}},"trackingParams":"COECEJQ1GAQiEwittO2HmoiSAxUqRfUFHbSpNSZA6NqM2vXW7-bLAQ==","shortViewCountText":{"accessibility":{"accessibilityData":{"label":"조회수 1.5천회"}},"simpleText":"조회수 1.5천회"},"menu":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"현재 재생목록에 추가"}]},"icon":{"iconType":"ADD_TO_QUEUE_TAIL"},"serviceEndpoint":{"clickTrackingParams":"COYCEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"COYCEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"y82-t1tDLWg","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"COYCEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["y82-t1tDLWg"],"params":"CAQ%3D"}},"videoIds":["y82-t1tDLWg"],"videoCommand":{"clickTrackingParams":"COYCEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=y82-t1tDLWg","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"y82-t1tDLWg","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr2---sn-ab02a0nfpgxapox-bh26z.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026oreouc=1\u0026id=cbcdbeb75b432d68\u0026ip=1.208.108.242\u0026initcwndbps=4218750\u0026mt=1768296063\u0026oweuc="}}}}}}}]}},"trackingParams":"COYCEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUm"}},{"menuNavigationItemRenderer":{"text":{"runs":[{"text":"재생목록에 저장"}]},"icon":{"iconType":"BOOKMARK_BORDER"},"navigationEndpoint":{"clickTrackingParams":"COUCEJSsCRgGIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"COUCEJSsCRgGIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","showSheetCommand":{"panelLoadingStrategy":{"requestTemplate":{"panelId":"PAadd_to_playlist","params":"-gYNCgt5ODItdDF0RExXZw%3D%3D"}}}}}},"trackingParams":"COUCEJSsCRgGIhMIrbTth5qIkgMVKkX1BR20qTUm"}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"공유"}]},"icon":{"iconType":"SHARE"},"serviceEndpoint":{"clickTrackingParams":"COECEJQ1GAQiEwittO2HmoiSAxUqRfUFHbSpNSbKAQR_-A9v","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"Cgt5ODItdDF0RExXZw%3D%3D","commands":[{"clickTrackingParams":"COECEJQ1GAQiEwittO2HmoiSAxUqRfUFHbSpNSbKAQR_-A9v","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"COQCEI5iIhMIrbTth5qIkgMVKkX1BR20qTUm","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}},"trackingParams":"COECEJQ1GAQiEwittO2HmoiSAxUqRfUFHbSpNSY=","hasSeparator":true}}],"trackingParams":"COECEJQ1GAQiEwittO2HmoiSAxUqRfUFHbSpNSY=","accessibility":{"accessibilityData":{"label":"작업 메뉴"}}}},"thumbnailOverlays":[{"thumbnailOverlayTimeStatusRenderer":{"text":{"accessibility":{"accessibilityData":{"label":"5분 44초"}},"simpleText":"5:44"},"style":"DEFAULT"}},{"thumbnailOverlayToggleButtonRenderer":{"isToggled":false,"untoggledIcon":{"iconType":"WATCH_LATER"},"toggledIcon":{"iconType":"CHECK"},"untoggledTooltip":"나중에 볼 동영상","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"COMCEPnnAxgBIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"y82-t1tDLWg","action":"ACTION_ADD_VIDEO"}]}},"toggledServiceEndpoint":{"clickTrackingParams":"COMCEPnnAxgBIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"y82-t1tDLWg"}]}},"untoggledAccessibility":{"accessibilityData":{"label":"나중에 볼 동영상"}},"toggledAccessibility":{"accessibilityData":{"label":"추가됨"}},"trackingParams":"COMCEPnnAxgBIhMIrbTth5qIkgMVKkX1BR20qTUm"}},{"thumbnailOverlayToggleButtonRenderer":{"untoggledIcon":{"iconType":"ADD_TO_QUEUE_TAIL"},"toggledIcon":{"iconType":"PLAYLIST_ADD_CHECK"},"untoggledTooltip":"현재 재생목록에 추가","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"COICEMfsBBgCIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"COICEMfsBBgCIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"y82-t1tDLWg","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"COICEMfsBBgCIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["y82-t1tDLWg"],"params":"CAQ%3D"}},"videoIds":["y82-t1tDLWg"]}}]}},"untoggledAccessibility":{"accessibilityData":{"label":"현재 재생목록에 추가"}},"toggledAccessibility":{"accessibilityData":{"label":"추가됨"}},"trackingParams":"COICEMfsBBgCIhMIrbTth5qIkgMVKkX1BR20qTUm"}},{"thumbnailOverlayNowPlayingRenderer":{"text":{"runs":[{"text":"지금 재생 중"}]}}}]}},{"gridVideoRenderer":{"videoId":"vVpd34bWCJA","thumbnail":{"thumbnails":[{"url":"https://i.ytimg.com/vi/vVpd34bWCJA/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLAX7SD54nkDbveYtO296kZffJRqmA","width":168,"height":94},{"url":"https://i.ytimg.com/vi/vVpd34bWCJA/hqdefault.jpg?sqp=-oaymwEiCMQBEG5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLDLTCzqGhkZtzCfFThJ26ouOyiiyA","width":196,"height":110},{"url":"https://i.ytimg.com/vi/vVpd34bWCJA/hqdefault.jpg?sqp=-oaymwEjCPYBEIoBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLB_q5ZwzjgcjxWbrpOz4MgWKFQwjw","width":246,"height":138},{"url":"https://i.ytimg.com/vi/vVpd34bWCJA/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLAUufUjl00S9u7t9DyHFdRYgrcO0w","width":336,"height":188}]},"title":{"accessibility":{"accessibilityData":{"label":"Build Secure FreeBSD Containers in 5 Minutes 5분 54초"}},"simpleText":"Build Secure FreeBSD Containers in 5 Minutes"},"publishedTimeText":{"simpleText":"4개월 전"},"viewCountText":{"simpleText":"조회수 4,706회"},"navigationEndpoint":{"clickTrackingParams":"CNsCEJQ1GAUiEwittO2HmoiSAxUqRfUFHbSpNSYyCmctaGlnaC1jcnZaGFVDeEx4Ul9vVy1OQW1DaEljU2tBeVpHUZoBBRDyOBhmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=vVpd34bWCJA","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"vVpd34bWCJA","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr4---sn-ab02a0nfpgxapox-bh2s6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026oreouc=1\u0026id=bd5a5ddf86d60890\u0026ip=1.208.108.242\u0026initcwndbps=3976250\u0026mt=1768296063\u0026oweuc="}}}}},"trackingParams":"CNsCEJQ1GAUiEwittO2HmoiSAxUqRfUFHbSpNSZAkJHYtvi7l629AQ==","shortViewCountText":{"accessibility":{"accessibilityData":{"label":"조회수 4.7천회"}},"simpleText":"조회수 4.7천회"},"menu":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"현재 재생목록에 추가"}]},"icon":{"iconType":"ADD_TO_QUEUE_TAIL"},"serviceEndpoint":{"clickTrackingParams":"COACEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"COACEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"vVpd34bWCJA","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"COACEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["vVpd34bWCJA"],"params":"CAQ%3D"}},"videoIds":["vVpd34bWCJA"],"videoCommand":{"clickTrackingParams":"COACEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=vVpd34bWCJA","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"vVpd34bWCJA","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr4---sn-ab02a0nfpgxapox-bh2s6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026oreouc=1\u0026id=bd5a5ddf86d60890\u0026ip=1.208.108.242\u0026initcwndbps=3976250\u0026mt=1768296063\u0026oweuc="}}}}}}}]}},"trackingParams":"COACEP6YBBgFIhMIrbTth5qIkgMVKkX1BR20qTUm"}},{"menuNavigationItemRenderer":{"text":{"runs":[{"text":"재생목록에 저장"}]},"icon":{"iconType":"BOOKMARK_BORDER"},"navigationEndpoint":{"clickTrackingParams":"CN8CEJSsCRgGIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CN8CEJSsCRgGIhMIrbTth5qIkgMVKkX1BR20qTUmygEEf_gPbw==","showSheetCommand":{"panelLoadingStrategy":{"requestTemplate":{"panelId":"PAadd_to_playlist","params":"-gYNCgt2VnBkMzRiV0NKQQ%3D%3D"}}}}}},"trackingParams":"CN8CEJSsCRgGIhMIrbTth5qIkgMVKkX1BR20qTUm"}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"공유"}]},"icon":{"iconType":"SHARE"},"serviceEndpoint":{"clickTrackingParams":"CNsCEJQ1GAUiEwittO2HmoiSAxUqRfUFHbSpNSbKAQR_-A9v","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"Cgt2VnBkMzRiV0NKQQ%3D%3D","commands":[{"clickTrackingParams":"CNsCEJQ1GAUiEwittO2HmoiSAxUqRfUFHbSpNSbKAQR_-A9v","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CN4CEI5iIhMIrbTth5qIkgMVKkX1BR20qTUm","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}},"trackingParams":"CNsCEJQ1GAUiEwittO2HmoiSAxUqRfUFHbSpNSY=","hasSeparator":true}}],"trackingParams":"CNsCEJQ1GAUiEwittO2HmoiSAxUqRfUFHbSpNSY=","accessibility":{"accessibilityData":{"label":"작업 메뉴"}}}},"thumbnailOverlays":[{"thumbnailOverlayTimeStatusRenderer":{"text":{"accessibility":{"accessibilityData":{"label":"5분 54초"}},"simpleText":"5:54"},"style":"DEFAULT"}},{"thumbnailOverlayToggleButtonRenderer":{"isToggled":false,"untoggledIcon":{"iconType":"WATCH_LATER"},"toggledIcon":{"iconType":"CHECK"},"untoggledTooltip":"나중에 볼 동영상","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"CN0CE | 2026-01-13T09:29:33 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3Alink | 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://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://chromewebstore.google.com/detail/category/top-charts/detail/askbelynda-sustainable-sh/category/extensions/productivity/detail/chat-with-all-ai-models-g/becfinhbfclcgokjlobojlnldbfillpf | 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://www.ecns.cn/contactus.shtml | Contact Us - Headlines, stories and photos from ecns.cn If you can read Chinese, please visit our Chinese website www.chinanews.com Share the news or just email us your thoughts. Save your time reading the web? Click the RSS and we will help you. more HOME NEWS FEATURE BUSINESS MILITARY EXPERIENCE VIDEO PHOTO Contact Us Ecns.cn Address: 12 Baiwanzhuang South St., Xicheng District, Beijing 100037, PRC Tel: 8610-88311100 Fax: 8610-68327649 Hotline: 15699788000 Email: en@chinanews.com.cn Media Relationship Tel: 8610-68990787 Fax: 8610-68327649 Email: en@chinanews.com.cn �� Links ���� About Us ���� Jobs ���� Contact Us ���� Privacy Policy Copyright ©1999-2011 Chinanews.com. All rights reserved. Reproduction in whole or in part without permission is prohibited. | 2026-01-13T09:29:33 |
https://cn.chinadaily.com.cn/a/202511/17/WS691abe05a310942cc4991c5d.html | 【世界说】菲分析人士：高市早苗“生存威胁”论存多重逻辑谬误 尊重历史方为正途 - 中国日报网 【世界说】菲分析人士：高市早苗“生存威胁”论存多重逻辑谬误 尊重历史方为正途 菲律宾经济政治分析家李天荣指出，高市早苗近期在国会答辩时公然发表的涉台露骨挑衅言论，绝非单纯的外交失言，更是对历史的严重误读。 站内搜索 搜狗搜索 中国搜索 --> 订阅 移动 English 首页 时政 时政要闻 评论频道 理论频道 学习时代 两岸频道 资讯 独家 中国日报专稿 传媒动态 每日一词 法院公告 C财经 证券 独家 科技 产业 视频 专栏 双语 双语财讯 每日一词 双语新闻 新闻热词 译词课堂 --> 漫画 观天下 中国观察 中国日报网评 中国那些事儿 海外手记 侨一瞧 地方 文创 文旅 生活 中国有约 China Daily Homepage 中文网首页 时评 资讯 C财经 生活 视频 专栏 双语 --> 漫画 原创 观天下 地方频道 --> 关闭 中国日报网 > 世界说 > 【世界说】菲分析人士：高市早苗“生存威胁”论存多重逻辑谬误 尊重历史方为正途 来源：中国日报网 2025-11-17 14:17 --> 分享到微信 中国日报网11月17日电 日前，以鲜明右翼保守立场著称的日本首相高市早苗，在国会答辩时公然发表涉台露骨挑衅言论，暗示可能武力介入台海问题，性质极其恶劣，影响极为负面。 对此，《菲律宾星报》专栏作者、经济政治分析家李天荣（Wilson Lee Flores）在《中国日报》撰文指出，高市早苗近期发表不当言论，宣称中国在台湾周边的军事行动可能构成对日本的“生存威胁”，绝非单纯的外交失言。这些言论折射出对历史的严重误读，更违背了半个世纪以来维系东亚和平稳定的基本准则。其内在逻辑亦难以成立，尤其考虑到“生存威胁事态”是日本政府依法调动自卫队的前提之一。 高市早苗涉台言论是鲁莽不负责任的，必将会给日本带来灾难性后果。（作者：中国日报 罗杰） 颇具讽刺意味的是，台湾问题的产生，部分源于日本自身的帝国主义侵略行径。在19世纪末之前，台湾长期隶属于中国行政管辖范围。1894年，日本发动侵略中国的“甲午战争”，并于次年迫使清政府签订不平等的《马关条约》，强行割让台湾及澎湖列岛。 李天荣表示，这绝非和平移交，而是殖民胁迫下的非道德行径——日本以武力强行将台湾从中国分割出去，使其遭受长达五十年的外国殖民统治。因此，当前的台湾问题并非现代地缘政治的偶然产物，在很大程度上实为日本侵略行径留下的直接遗毒。 在此背景下，高市早苗宣称台湾局势可能“威胁”日本生存的说法不仅荒谬，更存在逻辑谬误。其论点包含多重错漏：其一为因果谬误，错误暗示台湾问题必然决定日本的安全态势；其二为非因果推论，将地区事务直接等同于国家生存威胁，脱离现实关联与基本常识；其三为错误等同，将日本的自卫权与干涉中国内政混为一谈。此类主张，无异于在虚幻想象的基础上构建外交政策，势必招致不必要的风险。 报道截图 高市早苗的论调，不仅逻辑混乱，更是对历史毫无敬畏之心的体现。日本作为曾以侵略手段割占台湾的国家，如今竟妄图自居为台湾分离状态的所谓“捍卫者”，这种说辞在历史的反讽面前不攻自破。 更值得警惕的是，此类言论严重破坏了战后东亚国际秩序的基础。1972年9月29日，中日两国政府正式签署《中日联合声明》，实现了邦交正常化，其中明确日本政府“充分理解和尊重”中国政府有关“台湾是中华人民共和国领土不可分割的一部分”的立场。 亚洲未来的稳定发展，不取决于日本的高调宣示，而在于其能否明智地铭记历史、汲取教训。从法理与历史双重维度来看，台湾的地位早已明确无误。日本在二战战败后，依据《开罗宣言》（1943年）、《波茨坦公告》（1945年）及《日本投降书》（1945年）的明确规定，必须放弃以武力窃取的领土，包括台湾及澎湖列岛。台湾问题，根源在于内战遗留问题及外部势力干涉，并非存在合法或持久的国际争议。 李天荣强调，日本的发展道路，绝不应重拾旧式军国主义话语，或将战略野心包装为道德诉求。真正负责任的治国之道，应建立在历史清醒与严谨逻辑之上。 对于日本自诩为当前台海问题的“武装捍卫者”，作者认为，这种现状恰与其过去的帝国主义行径紧密相关，实属极致讽刺。日本真正的出路不在于言辞挑衅或军事示警，而在于恪守国际承诺、尊重历史事实，以审慎和理性的外交行动促进区域稳定。 亚洲的和平未来，不取决于哪国的声音更大，而取决于各国，尤其是日本，能否以史为鉴，以诚意与克制开展对外交往，共守区域和平稳定。 （编译：马芮 编辑：高琳琳 韩鹤） 【责任编辑：马芮】 COMPO WS691abe05a310942cc4991c5d https://cn.chinadaily.com.cn/a/202511/17/WS691abe05a310942cc4991c5d.html 世界说 【世界说】杰弗里·萨克斯：中国是合作伙伴而非威胁 美国遏制战略是损害自身的“回旋镖” 聚焦2025APEC丨一个视频带你了解含金量如此之高的APEC 【世界说】美国贸易政策又把养牛业者惹怒了：做法昧良心，感觉遭“背刺”！ 【世界说】美国GDP的虚拟泡沫：繁荣背后的经济“虚胖”幻象 【世界说】枪支令美国社会充斥消极氛围：对安全焦虑、对枪暴麻木 【世界说】两党互责，苦了民众伤了机构……美联邦政府停摆僵局持续 【世界说】美媒：关税非解决美国制造业痼疾良方，不如专注提高自身生产率 【世界说】美国滑雪爱好者或迎“昂贵一冬” 本地商家：“还不都是关税闹的” 推荐阅读 前三季度我国银行业整体运行稳健 贴息“红包”撬动消费潜能 璀璨非遗：一个绣郎的苏绣宇宙 北京迎来大风天气 工业经济高质量发展扎实推进 上市公司新消费潜力迸发 从第38届金鸡奖看中国电影发展趋势 刚果（金）一矿区简易桥梁坍塌 至少32人死亡 为你推荐 神奇的中国 海外手记 和评理 中国那些事儿 世界说 中国观察 新华社 中国日报网评 侨一瞧 事事关心 每日一词 中国经济网 中国新闻网 环球时报 中央电视台 中央人民广播电台 解放军报 中国新闻周刊 人民日报海外版 中国青年网 经济日报 光明日报 中国军网 求是 中国侨网 消费日报网 中国警察网 参考消息网 中国搜索 海外网 法制网 环球网 中青在线 中工网 中国西藏网 中国台湾网 央广网 光明网 人民网 国际在线 中国网 未来网 每日一词 一财网 新华网 为你推荐 神奇的中国 海外手记 和评理 中国那些事儿 世界说 中国观察 新华社 中国日报网评 侨一瞧 事事关心 每日一词 中国经济网 中国新闻网 环球时报 中央电视台 中央人民广播电台 解放军报 中国新闻周刊 人民日报海外版 中国青年网 经济日报 光明日报 中国军网 求是 中国侨网 消费日报网 中国警察网 参考消息网 中国搜索 海外网 法制网 环球网 中青在线 中工网 中国西藏网 中国台湾网 央广网 光明网 人民网 国际在线 中国网 未来网 每日一词 一财网 新华网 推荐阅读 前三季度我国银行业整体运行稳健 贴息“红包”撬动消费潜能 璀璨非遗：一个绣郎的苏绣宇宙 北京迎来大风天气 工业经济高质量发展扎实推进 上市公司新消费潜力迸发 从第38届金鸡奖看中国电影发展趋势 刚果（金）一矿区简易桥梁坍塌 至少32人死亡 关于我们 | 联系我们 首页 时评 资讯 财经 生活 视频 专栏 漫画 独家 招聘 地方频道： 北京 天津 河北 山西 辽宁 吉林 黑龙江 上海 江苏 浙江 福建 江西 山东 河南 湖北 湖南 广东 广西 海南 重庆 四川 贵州 云南 西藏 陕西 新疆 深圳 友情链接： 人民网 新华网 中国网 国际在线 央视网 中国青年网 中国经济网 中国台湾网 中国西藏网 央广网 光明网 中国军网 中国新闻网 人民政协网 法治网 违法和不良信息举报 互联网新闻信息服务许可证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://ja-jp.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ストア Meta Quest Ray-Ban Meta Meta AI Meta AIのコンテンツをもっと見る Instagram Threads 投票情報センター プライバシーポリシー プライバシーセンター Facebookについて 広告を作成 ページを作成 開発者 採用情報 Cookie AdChoices 規約 ヘルプ 連絡先のアップロードと非ユーザー 設定 アクティビティログ Meta © 2026 | 2026-01-13T09:29:33 |
http://www.chinadaily.com.cn/a/202601/13/WS6965f4bda310d6866eb336fe.html | Cold front coats Guizhou mountains in rime 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 Home > News Cold front coats Guizhou mountains in rime By Yang Jun and Liu Boqian in Guiyang | chinadaily.com.cn| Updated: 2026-01-12 Print 1154317 2026-01-12 17:09:44.0 Yang Jun and Liu Boqian in Guiyang Cold front coats Guizhou mountains in rime guizhou 48 15554 News 2@guizhouen /enpproperty--> An aerial view of the terraced fields in Qianxi, Guizhou province, cloaked in white rime. [Photo by Wu Chuanjuan/For chinadaily.com.cn] A fresh cold front swept the south in recent days, coating the terraced fields of Qianxi, Guizhou province, with white rime. The verdant distant peaks are wrapped in a pale mist that drifts slowly above the fields. Steep terrain limits farmland in Guizhou, so residents have long reclaimed and cultivated the small plots on the hillsides that circle their villages. An aerial view of the terraced fields in Qianxi, Guizhou province, cloaked in white rime. [Photo by Wu Chuanjuan/For chinadaily.com.cn] An aerial view of the terraced fields in Qianxi, Guizhou province, cloaked in white rime. [Photo by Wu Chuanjuan/For chinadaily.com.cn] An aerial view of the terraced fields in Qianxi, Guizhou province, cloaked in white rime. [Photo by Wu Chuanjuan/For chinadaily.com.cn] Regions Overview Guiyang Guian New Area Liupanshui Anshun Qianxinan Qiandongnan Qiannan Zunyi Tongren Bijie Specials China (Guizhou) Intl Alcoholic Beverages Expo Big Data Expo 2025 Videos On the journey to modernization Reports 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:33 |
https://wiki.documentfoundation.org/Marketing/ConferenceKit | LibreOffice Conference Kit - 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 Contents move to sidebar hide Beginning 1 Resources Available for Conferences 2 Booth Resources 3 Clothing and Promotional Items (SWAG) 4 Computer/Software/Electronics related 5 LibreOffice DVD 6 Miscellaneous Resources 7 Best Practices Toggle Best Practices subsection 7.1 Organizing your own conference 7.1.1 Accessibility 7.1.2 Discoverability 7.1.3 Sound 7.1.4 Seats 7.1.5 Conference package 7.1.6 Child care 7.1.7 Recording of the presentations 7.2 Participating in a conference organized by another entity 7.2.1 Booth Layout 7.2.2 Booth Services 7.2.3 Sponshorship and Funding Toggle the table of contents LibreOffice Conference Kit 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 < Marketing 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 Resources Available for Conferences This page lists different elements that should/could be considered for completion in preparation for a conference. Consultation with any other appropriate LibreOffice group may be necessary . ( Italo : Marketing communiqués; Design team ) Booth Resources Event/Conference Catalogue Text (samples): Text that could be used on conference website listing/catalogues   LibreOffice 3-Fold Pamphlet : A4 and Letter formats LibreOffice Flyer : See Gallery Flyers for flyers created in Draw (and translations) LibreOffice Business Card (TBA) LibreOffice Marketing PostCards:   LibreOffice Postcards in different sizes and Examples of LibreOffice postcards for specific events LibreOffice Stickers (TBA) Example of German stickers   ' prepared by the German team for CeBIT2011 in Hannover LibreOffice Posters LibreOffice Appeal for Funding Poster (TBA) Example of German appeal for funding poster   prepared by the German team for CeBIT2011 in Hannover LibreOffice Booth Banners: Horizontal and vertical banners used at conferences Clothing and Promotional Items (SWAG) LibreOffice T-Shirts: Various size T-Shirts available for sale (not available on LibreOffice Store as of yet) and examples of T-Shirts made for specific events LibreOffice Promotional Items: Promotional items available at conferences (pens, lanyards, bags ...) and examples of items made for specific events Computer/Software/Electronics related Branding Guidelines: Branding material and information to ensure both consistent and fresh appearance ; OFFICIAL logos are found on this page Miscellaneous Logos: Third Party Logos: Weblinks to official 3rd party logo pages: ODF, PDF, SVC; CC; LGPL; W3 conformance; Logo proposals for Paris Conference October 2011 Marketing Material: Official marketing material for both The Document Foundation and LibreOffice LibreOffice Wallpapers:   LibreOffice wallpapers and LibreOffice wallpapers made for specific events. LibreOffice Website Banners: Banners for official or external website use or for special projects (i.e. funding drives) LibreOffice Presentations (.odp): Presentation by Florian Effenberger @ OpenSuse Conference October 22 2010 File:Introducing LibreOffice.odp by user:kinshuksunil at OSScamp Lucknow 11.03, March 26 2010 LibreOffice Videos: (TBA) LibreOffice DVD LibreOffice DVD/Jewel Case Cover: no official English DVD ISO disk is available as of yet (TBA) LibreOffice Box DVD   by German Team is available in German language Examples of DVD/Jewel Case Covers : an exhaustive list of DVD/DVD Content proposals and designs Example of provided by OpenSourcePress North American DVD project : DVD project including countries: Canada, USA.' This is a sample of the North American Community DVD Label, which is included in the .iso disk download on LibreOffice's DVD download page(s). Miscellaneous Resources Quick Reference Cards: Tri-fold reference cards for keyboard shortcuts in LibreOffice Applications Paper AirPlane: Paper airplane with LibreOffice marketing related message(s) LibreOffice in Print: a copy of some printed LibreOffice manuals could be displayed at the booth/table. Available from Lulu Calc ScoreSheet Examples: illustrate the use of a LibreOffice Calc file as a personal sports scoresheet Best Practices Organizing your own conference Accessibility The location needs to be accessible with a wheelchair. Discoverability In the vicinity of the conference location, set up signs that guide to the location. Inside the location, set up signs that guide to the conference rooms. Beside the door to each room, attach the time table for the talks scheduled to happen inside. On the conference website, include instructions on how to arrive at the location using public transportation. Sound When picking the location, pay attention to the acoustics. Do not choose a location with rooms that make it impossible to follow presentations due to strong reverb. Make sure microphone logistics are solved for audience questions as well. Seats The seats should be accompanied by tables and preferably integrated power sockets. Conference package Every participant should get a printed leaflet of the conference program. Make sure the conference name badge is either two-sided or equipped with a clip mechanism that keeps the side with name of the participant visible. Child care Make preparations to have child care on the conference site, if needed. Recording of the presentations Recording conference presentations on video is not trivial. You must practice the workflow on-site from start to finished end product before the conference begins. The ideal situation is that you are able to capture the video signal from the presenter's computer and freely mix it with the presentation recording in the editing phase. Working sound is, again, crucial. Watching presentation videos with poor sound is torture. Participating in a conference organized by another entity Booth Layout larger banners hung in different directions, so that they can be seen from anywhere, some of the small banners directed towards the outside Example of booth layout at FOSDEM 2011   and some others here http://hedgehogpainter.livejournal.com/11599.html can offer some green coloured sweets a "booth emergency pack" should contain: tape (different types), a knife, twine, flipchart pens (different colors), cough drops (very important for events > 1 day) cashbox if items are for sale - make sure you have enough currency for resolving cash purchases donation box Booth Services offer to copy LibreOffice media onto flash drives to conference attendees depending on conference, show LibreOffice on different platforms. Requirement of multiple computers at the booth computer showing what's new in this version maybe one computer running the build process cards summarizing the project and telling people where to get support locally Sponshorship and Funding LibreOffice funds Corporate sponsorship (Italo -- LibreOffice marketing guru -- should be kept informed) sales of LibreOffice marketing items donations Retrieved from " https://wiki.documentfoundation.org/index.php?title=Marketing/ConferenceKit&oldid=176537 " Categories : EN Conferences This page was last edited 11:49, 8 May 2019 by Ilmari Lauhakangas . Based on work by Valerii Goncharuk and Mike Saunders 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:33 |
https://developer.wordpress.com/docs/developer-tools/github-deployments/ | Use GitHub deployments on WordPress.com – WordPress.com Support Products Features Resources Plans & Pricing Log in Get started Menu WordPress Hosting WordPress for Agencies Become an Affiliate Domain Names AI Website Builder Website Builder Create a Blog Newsletter Professional Email Website Design Services Commerce WordPress Studio Enterprise WordPress Overview WordPress Themes WordPress Plugins WordPress Patterns Google Apps Support Center WordPress News Business Name Generator Logo Maker Discover New Posts Popular Tags Blog Search Close the navigation menu Get started Sign up Log in About Plans & Pricing Products WordPress Hosting WordPress for Agencies Become an Affiliate Domain Names AI Website Builder Website Builder Create a Blog Newsletter Professional Email Website Design Services Commerce WordPress Studio Enterprise WordPress Features Overview WordPress Themes WordPress Plugins WordPress Patterns Google Apps Resources Support Center WordPress News Business Name Generator Logo Maker Discover New Posts Popular Tags Blog Search Jetpack App Learn more Support Center Guides Courses Forums Contact Search Support Center / Guides Support Center Guides Courses Forums Contact Guides / Plugins and tools / Tools / Use GitHub deployments on WordPress.com Use GitHub deployments on WordPress.com Last reviewed on November 6, 2025 GitHub Deployments integrates your GitHub repositories directly with your WordPress.com site, giving you a version-controlled, automated workflow for deploying plugins, themes, or complete site changes. This guide covers the setup process and how to manage your connected repositories. This feature is available on sites with the WordPress.com Business and Commerce plans . If you have a Business plan, make sure to activate it . For free sites and sites on the Personal and Premium plans, upgrade your plan to access this feature. In this guide Video tutorial Connect a repository Manage deployment settings Advanced deployment Deploy your code Manage existing connections Deployment run logs Disconnect a repository Disconnect WordPress.com from GitHub Have a question? Ask our AI assistant Back to top Video tutorial Connect a repository Before you can deploy a GitHub repository to your WordPress.com site, you’ll first need to set up the connection between the two using the following steps: Visit your Sites page: https://wordpress.com/sites/ Click the name of your site to view the site overview. Click on the Deployments tab. Click the “ Connect repository ” button. Then, if you see repositories listed, you have already connected your GitHub account. Continue to step 11. Click the “ Install the WordPress.com app ” button. A new window will open, and you will be prompted to log into your GitHub account if you haven’t already done so. Then you’ll see this screen: Click the “ Authorize WordPress.com for Developers ” button. Select the GitHub organization or account where your repository is located. Select which repository/repositories you’d like to connect: All repositories: Selecting this option will grant WordPress.com access to all current and future repositories owned by the selected GitHub account. This includes public repositories that are read-only. Only select repositories: Selecting this option will allow you to choose which repositories WordPress.com can access on the selected GitHub account. Once you’ve selected an option, click the Install button. The new window will close, and you will be taken back to WordPress.com. Your selected repository/repositories should be listed along with the GitHub account associated with that repository: Click Select next to the repository you wish to connect. At this point, you should see WordPress.com for Developers under your Authorized GitHub Apps and Installed GitHub Apps . Manage deployment settings Once you select a repository, you will need to adjust the deployment settings: Deployment branch: Defaults to the default branch of the repository (typically main ) but can be changed to the branch you wish to use. Destination directory: The server folder where you want to deploy the files. For plugins, it will be /wp-content/plugins/my-plugin-name . For themes, it will be /wp-content/themes/my-theme-name . For a partial site deployment (i.e., multiple plugins or themes), you can use /wp-content . The contents of a repository will be merged with the existing contents of the WordPress site in the specified directory. Automatic deployments: There are two ways you can deploy to WordPress.com: Automatic: Once the code is committed, it will be deployed to your WordPress.com site. Automatic deployments are recommended for staging sites. Manual: The code will be deployed once you request a deployment . Manual deployments are recommended for production sites. Deployment mode: There are two types of deployments: Simple: This mode will copy all files from a branch of the repository to the site and deploy them with no post-processing. Advanced: With this mode, you can use a workflow script, enabling custom build steps such as installing Composer dependencies, conducting pre-deployment code testing, and controlling file deployment. Ideal for repositories that need Composer or Node software. See Advanced Deployment below for more information . Once all settings have been configured, click the Connect button. Your repository will be added: Note that you must trigger the first deployment, either automatically or manually . You can then connect another repository at any time by clicking the “ Connect repository ” button. Advanced deployment With Advanced Deployment, you can provide a workflow script to process files in your repository before deployment. This opens up many possibilities, such as checking your code to ensure it meets your team’s coding standards, running unit tests, excluding files from the deployment, installing dependencies, and much more. To get started, check out our workflow recipes . To set up Advanced Deployment: A form will appear where you can configure the deployment. Click the repository’s name to manage the connection. On the right side, under “ Pick your deployment mode “, choose Advanced . If the repository already contains a workflow file, you can select it here. The system will check the file for any errors. If no errors are found, proceed to step 7. You can also select the “ Create new workflow ” option to add a preconfigured workflow file. Choosing this option will overwrite the wpcom.yml workflow file if it already exists in your repository. Click the “ Install workflow for me ” button to commit the workflow file to the repository. Once a workflow has been added and verified, click Update . Your repository will now use advanced deployment. Deploy your code After connecting your GitHub repository to a site, the next step is actually deploying your code. There are two deployment methods available: Automatic and Manual . Automatic deployments are not recommended for live production sites, as any code changes in the repository are automatically deployed from GitHub to the live site. Instead, consider setting up automatic deployment to a staging site and syncing it to production once you’re ready. Manual deployments give you more control over when your code changes are pushed live, as you will manually need to trigger each deployment. We recommend manual deployments if you don’t want to use a staging site. To manually trigger a deployment: Visit your Sites page: https://wordpress.com/sites/ Click the name of your site to view the site overview. Click on the Deployments tab. Click the ellipsis menu (⋮) on the repository you wish to deploy. Choose “ Trigger manual deployment “. You should see a banner notification that says, “Deployment run created,” and the deployment status will change to “Queued.” Wait for the deployment to complete (the status will change to “Deployed”). Click the ellipsis menu (⋮) again and choose “ See deployment runs “. The Deployment run log displays the Author and the deployed commit. If you click the deployment run entry, you can view more information. Manage existing connections To manage your existing GitHub repository connections: Visit your Sites page: https://wordpress.com/sites/ Click the name of your site to view the site overview. Click on the Deployments tab. You should then see the connections list. The connection list is shown if there is at least one connection between a GitHub repository and your site. The list includes relevant information for each connection, such as the repository name and branch, the last commit that was deployed to a site, when it happened, where the code was placed, how long the deployment run took, and its status. There are additional actions available after clicking the ellipsis menu (⋮): Trigger manual deployment: Starts a deployment run on the latest commit of the configured branch. See deployment runs: Opens the deployment run logs view for the connected repository. Configure connection: Opens the manage connection view for the repository. Disconnect repository: Removes the connection between the repository and the site. Deployment run logs Deployment run logs provide a detailed, step-by-step record of each deployment, whether triggered automatically or manually. These logs help you track changes, monitor deployment status, and troubleshoot any issues that arise. With access to logs from the last 10 runs within 30 days, you can easily review what happened during each deployment and ensure everything is running smoothly. To check the logs of a deployment: Visit your Sites page: https://wordpress.com/sites/ Click the name of your site to view the site overview. Click on the Deployments tab. Click the ellipsis menu (⋮) next to the repository you want to view logs for. Select “ See deployment runs “. The Deployment runs list view shows commits that were deployed to the site, the deployment status, the date, and the duration. Click anywhere on a run to expand and view more information about the deployment. The logs provide a record of all executed commands, from fetching code from GitHub to placing it in the target directory. You can expand log lines to see more information by clicking “ show more “. Disconnect a repository When you disconnect a GitHub repository from your site, any future changes to the repository will no longer impact your site. By default, the deployed files remain on your site, but you have the option to remove them during the disconnection process. To remove a repository: Visit your Sites page: https://wordpress.com/sites/ Click the name of your site to view the site overview. Click on the Deployments tab. Click the ellipsis menu (⋮) on the repository. Select “ Disconnect repository “. A dialog window will appear. Click the switch to remove associated files from the site. Click “ Disconnect repository ” to close the dialog and disconnect the repository. Note that WordPress.com for Developers will still appear in your Installed GitHub Apps and your Authorized GitHub Apps . This is because WordPress.com still has access to the repository, but the connection has been deleted. Disconnect WordPress.com from GitHub You may also choose to revoke WordPress.com’s access to your GitHub account. You can do so at any time by visiting your Applications settings on GitHub. To revoke authorized app access to your GitHub account: Go to Authorized GitHub Apps . Click Revoke next to WordPress.com for Developers . Click the “ I understand, revoke access ” button. Even if you revoke authorized app access, code can still be deployed because the WordPress.com for Developers app remains installed on the selected accounts. To revoke access to the WordPress.com installation and disable the ability to deploy code to your WordPress.com site: Go to Installed GitHub Apps . Click Configure next to WordPress.com for Developers . In the Danger zone area, click Uninstall , then click OK when prompted. Removing WordPress.com from the list of authorized apps does not mean that the repositories will be deleted or stop working; your repositories will still exist on GitHub after you revoke WordPress.com’s access, but WordPress.com will no longer be able to deploy code. Was this guide helpful for you? Yay Nay Not quite what you're looking for? Get Help! Get Help What can we do to make this guide more helpful? (Optional) This form is not monitored for support. Need support? Get help here . Get help here. Related guides Workflow recipes for GitHub Deployments 3 min read Troubleshooting GitHub Deployments 2 min read View your site’s activity 3 min read Use SFTP on WordPress.com 3 min read In this guide Video tutorial Connect a repository Manage deployment settings Advanced deployment Deploy your code Manage existing connections Deployment run logs Disconnect a repository Disconnect WordPress.com from GitHub Have a question? Ask our AI assistant Back to top Couldn't find what you needed? Contact us Get answers from our AI assistant, with access to 24/7 expert human support on paid plans. Ask a question in our forum Browse questions and get answers from other experienced users. Copied to clipboard! WordPress.com Products WordPress Hosting WordPress for Agencies Become an Affiliate Domain Names AI Website Builder Website Builder Create a Blog Professional Email Website Design Services WordPress Studio Enterprise WordPress Features Overview WordPress Themes WordPress Plugins WordPress Patterns Google Apps Resources WordPress.com Blog Business Name Generator Logo Maker WordPress.com Reader Accessibility Remove Subscriptions Help Support Center Guides Courses Forums Contact Developer Resources Company About Press Terms of Service Privacy Policy Do Not Sell or Share My Personal Information Privacy Notice for California Users 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 Mobile Apps Download on the App Store Get it on Google Play Social Media WordPress.com on Facebook WordPress.com on X (Twitter) WordPress.com on Instagram WordPress.com on YouTube Automattic Automattic Work With Us Loading Comments... Write a Comment... Email Name Website | 2026-01-13T09:29:33 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3Acombobox | 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://www.atlassian.com/zh/jira/solutions/planning | 规划项目管理软件 | 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 免费获取 Atlassian 在 2025 年 Gartner 协作工作管理魔力象限™ 中被评为领导者！ 了解更多 用于规划的 Jira 为每个团队提供灵活的规划 让团队和利益相关者保持同步、异步并与您的目标保持一致。 免费获取 Jira 加入我们 30 多万个客户的行列，携手 Atlassian 赋能团队协作 为什么使用 Jira 进行规划？ 将您的工作可视化 将复杂的项目分解为小的、易于管理的部分。轻松添加和调整工作，以可视化不同任务的时间和顺序。 轻松共享 随着工作的进展，时间线也会实时更新，从而可以立即与团队、领导和利益相关者分享。 您的计划，您的风格 无论您是从头开始还是使用模板，都可以根据自己的条件和需求自由定制计划。 了解您的工作如何融入公司目标 规划功能比较 高级 基本 计划 是 Jira Premium 中的一项高级规划功能，允许 多个 团队就共享的计划或目标进行协作。 时间线 是所有 Jira 版本都可用的项目视图，允许您规划和跟踪单个团队内的工作。 使用 Jira 推动跨职能工作 跟踪全局 规划功能比较 高级 基本 “计划”可帮助您跟踪 多个团队和项目 的工作。在计划的摘要屏幕中，可以全面了解工作进度、依赖关系和团队速度。 通过时间线视图，您可以规划工作并跟踪 单个团队 的依赖关系。 提前了解依赖关系 规划功能比较 高级 基本 映射 团队、项目等之间 的依赖关系，提前应对潜在的资源或时间安排冲突。通过在 Confluence 页面上嵌入计划，向利益相关者标记依赖关系。 映射项目内的工作项之间的依赖关系，以识别和考虑潜在的障碍。 Align delivery across multiple teams Advanced only Use program boards to bring teams of teams onto a single plan. Align delivery across multiple sprints and keep complex projects progressing smoothly and on schedule. 规划时考虑团队的工作量 仅限高级 通过保证团队有足够的能力来完成自己分内的工作，确保您的目标按计划推进。以冲刺为单位查看多个团队的工作量。 设想不同的场景 仅限高级 通过根据不同的选项或最佳和最坏情况创建多个版本的计划，更全面地描绘潜在结果。 Release with confidence Advanced only Use releases to track progress, manage timelines, and keep every launch focused. Achieve smoother, more predictable releases that move the business forward. 专为规划而打造的模板 探索适用于各类计划的可定制 Jira 模板。 高层次规划 规划、跟踪和报告全公司范围内的工作，如计划或举措。 跨团队规划 跨多个 Scrum 团队来安排和分配工作、管理产能以及跟踪进度。 项目管理 从组织任务到可视化时间线，让团队能够全方位了解项目进度。 浏览更多模板 规划资源 浏览免费教程、文章和指南以了解更多信息。 如何使用 Jira 进行规划 有关如何规划工作、跟踪进度和映射依赖关系的教程。 查看指南 使用 Jira 进行战略规划 了解战略规划框架及其如何帮助您实现重大目标。 了解更多 冲刺规划要点 在团队的工作流中应用 Scrum 方法的要点。 立即浏览 转换工作方式 让组织和团队团结协作。 免费获取 企业 诚聘英才 活动 博文 投资者关系 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:33 |
https://www.atlassian.com/es/software/jira/templates/marketing | Plantillas de marketing | Biblioteca de plantillas de Jira | 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 Plantillas de Jira Open and close the navigation menu Categorías Desarrollo de software Marketing Diseño Ventas Operaciones Gestión de servicios RR. HH. Legal Operaciones de TI Finanzas Plantillas de gestión de proyectos Consíguelo gratis Categorías Desarrollo de software Marketing Diseño Ventas Operaciones Gestión de servicios RR. HH. Legal Operaciones de TI Finanzas Plantillas de gestión de proyectos Plantillas de marketing Consigue que el marketing tenga el impacto que buscas con Jira. Con las plantillas prediseñadas y personalizables para equipos de marketing, ponerse en marcha es fácil. Gestión de proyectos Gestiona las actividades para completar un proyecto empresarial. Gestión de contenido Gestiona el ciclo de vida de los contenidos, desde la priorización hasta la entrega. Gestión de campañas Lleva a cabo una campaña de marketing desde la idea inicial hasta la puesta en marcha. Comercialización Coordina el lanzamiento al mercado. Gestión de servicios de marketing Gestiona y supervisa todas tus solicitudes de marketing. Campaña por correo electrónico Planifica y ejecuta las campañas por correo electrónico desde el borrador hasta el lanzamiento Recursos de marketing Jira para equipos de marketing Desata la agilidad de tu equipo de marketing. Consulta más información sobre cómo Jira ayuda a agilizar el trabajo. Más información Pon tus proyectos en piloto automático Céntrate en lo que importa y automatiza el resto. Crea reglas personalizadas para tu equipo o empieza utilizando directamente automatizaciones predefinidas. Explorar las automatizaciones Conéctate a tus herramientas favoritas Aprovecha más de 500 integraciones para trabajar sin problemas, y más de 3000 extensiones adicionales para crear el proceso perfecto para tu equipo. Explorar el Marketplace de aplicaciones 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:33 |
https://reports.jenkins.io/jelly-taglib-ref.html#hudson.3AabstractItemLink | 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.3AbooleanRadio | 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://www.splunk.com/ko_kr/products/enterprise-security.html | Splunk 엔터프라이즈 시큐리티 | Splunk English Deutsch Francais 日本語 中文 繁體中文 false 로고 지원 고객 지원 지원 포털 Splunk에 문의 Splunk 응답 페이지 시스템 상태 Cisco 서포트 앱다이나믹스 지원 제품 보안 업데이트 Languages English Deutsch Francais 日本語 简体中文 繁體中文 로그인 사용자 계정 클릭 로그인 가입하기 나의 대시 보드 인스턴스 나의 교육 로그 아웃 PRODUCT LOGINS Splunk Observability Cloud Splunk Cloud Services Splunk On-Call Splunk Synthetic Monitoring Splunk Web Optimization Splunk AppDynamics 로고 플랫폼 플랫폼 Splunk의 확장형 데이터 플랫폼은 통합 보안, 풀스택 옵저버빌리티 및 커스텀 어플리케이션을 무제한으로 제공합니다. 가격 체계 무료 평가판 및 다운로드 제품 둘러보기 제품 클라우드 플랫폼 엔터프라이즈 Splunkbase 이용 사례 인공 지능(AI) 블록체인 모니터링 클라우드 혁신 규정 준수 데이터 관리 데이터 최적화 IT 현대화 IT 서비스 상태 분석 회복 탄력성 평가 서버리스 모니터링 플랫폼 개요 모든 유즈 케이스 보기 보안 엔터프라이즈 시큐리티 통합형 위협 탐지, 조사 및 대응을 통해 SOC를 현대화함으로써 디지털 회복 탄력성 강화. 가격 체계 무료 평가판 및 다운로드 제품 둘러보기 구성 통합 TDIR 플랫폼 SIEM SOAR UEBA 어텍 어넬라이저 자산 및 리스크 인텔리전스 이용 사례 이상 징후 탐지 인공 지능(AI) 대응 워크플로우 오케스트레이션 규정 준수 데이터 최적화 사기 방지 인시던트 관리 IT 문제 해결 보안 모니터링 위협 헌팅 보안 개요 모든 유즈 케이스 보기 옵저버빌리티 옵저버빌리티 성능 문제 탐지, 진단 및 해결을 위한 가시성 확보를 통해 어플리케이션 및 비즈니스의 원활한 운영 보장. 가격 체계 무료 평가판 및 다운로드 제품 둘러보기 제품 Observability Cloud IT 서비스 인텔리전스 앱다이나믹스 이용 사례 경보 노이즈 감소 애플리케이션 최신화 인공 지능(AI) 클라우드 마이그레이션 클라우드 모니터링 최적화 최종 사용자 경험 개선 IT 서비스 상태 마이크로서비스 내의 문제 디버깅 서비스 중단 예방 셀프 서비스 옵저버빌리티 옵저버빌리티 모든 유즈 케이스 보기 산업군 산업군 Splunk를 통해 모든 산업의 기업은 생산성, 규정 준수 및 보안 강화 실현. 항공우주 및 방위 커뮤니케이션 및 미디어 에너지 및 공공산업 금융 서비스 보건 의 고등 교육 제조 비영리 단체 온라인 서비스 공공 부문 소매업 기술 모든 산업 보기 리소스 이벤트 가까운 장소의 이벤트에 참여하기. 블로그 Splunk가 무엇을 하고 있는지 확인하기. 시작하기 Splunk 시작하기 Splunk Lantern 커뮤니티 및 유저 그룹 고객 성공 리소스 센터 알아보기 교육 및 인증 문건 블로그 이벤트 .conf26 Splunk를 사용해야 하는 이유 Splunk를 사용해야 하는 이유 Splunk 정보 수상 및 인증 고객 사례 Splunk 대 경쟁업체 파트너 모든 리소스 보기 검색 클릭 도움 받기 지원 고객 지원 지원 포털 Splunk에 문의 Splunk 응답 페이지 시스템 상태 Cisco 서포트 앱다이나믹스 지원 제품 보안 업데이트 Languages English Deutsch Francais 日本語 简体中文 繁體中文 로그인 사용자 계정 클릭 로그인 가입하기 나의 대시 보드 인스턴스 나의 교육 로그 아웃 PRODUCT LOGINS Splunk Observability Cloud Splunk Cloud Services Splunk On-Call Splunk Synthetic Monitoring Splunk Web Optimization Splunk AppDynamics 평가판 및 다운로드 검색 클릭 도움 받기 평가판 및 다운로드 로고 평가판 및 다운로드 플랫폼 보안 옵저버빌리티 산업군 리소스 지원 Account 로그인 | 가입하기 English Deutsch Francais 日本語 简体中文 繁體中文 플랫폼 보안 옵저버빌리티 산업군 리소스 지원 플랫폼 Splunk의 확장형 데이터 플랫폼은 통합 보안, 풀스택 옵저버빌리티 및 커스텀 어플리케이션을 무제한으로 제공합니다. 가격 체계 무료 평가판 및 다운로드 제품 둘러보기 제품 클라우드 플랫폼 엔터프라이즈 Splunkbase 이용 사례 인공 지능(AI) 블록체인 모니터링 클라우드 혁신 규정 준수 데이터 관리 데이터 최적화 IT 현대화 IT 서비스 상태 분석 회복 탄력성 평가 서버리스 모니터링 플랫폼 개요 모든 유즈 케이스 보기 엔터프라이즈 시큐리티 통합형 위협 탐지, 조사 및 대응을 통해 SOC를 현대화함으로써 디지털 회복 탄력성 강화. 가격 체계 무료 평가판 및 다운로드 제품 둘러보기 구성 통합 TDIR 플랫폼 SIEM SOAR UEBA 어텍 어넬라이저 자산 및 리스크 인텔리전스 이용 사례 이상 징후 탐지 인공 지능(AI) 대응 워크플로우 오케스트레이션 규정 준수 데이터 최적화 사기 방지 인시던트 관리 IT 문제 해결 보안 모니터링 위협 헌팅 보안 개요 모든 유즈 케이스 보기 옵저버빌리티 성능 문제 탐지, 진단 및 해결을 위한 가시성 확보를 통해 어플리케이션 및 비즈니스의 원활한 운영 보장. 가격 체계 무료 평가판 및 다운로드 제품 둘러보기 제품 Observability Cloud IT 서비스 인텔리전스 앱다이나믹스 이용 사례 경보 노이즈 감소 애플리케이션 최신화 인공 지능(AI) 클라우드 마이그레이션 클라우드 모니터링 최적화 최종 사용자 경험 개선 IT 서비스 상태 마이크로서비스 내의 문제 디버깅 서비스 중단 예방 셀프 서비스 옵저버빌리티 옵저버빌리티 모든 유즈 케이스 보기 산업군 Splunk를 통해 모든 산업의 기업은 생산성, 규정 준수 및 보안 강화 실현. 항공우주 및 방위 커뮤니케이션 및 미디어 에너지 및 공공산업 금융 서비스 보건 의 고등 교육 제조 비영리 단체 온라인 서비스 공공 부문 소매업 기술 모든 산업 보기 이벤트 가까운 장소의 이벤트에 참여하기. 블로그 Splunk가 무엇을 하고 있는지 확인하기. 시작하기 Splunk 시작하기 Splunk Lantern 커뮤니티 및 유저 그룹 고객 성공 리소스 센터 알아보기 교육 및 인증 문건 블로그 이벤트 .conf26 Splunk를 사용해야 하는 이유 Splunk를 사용해야 하는 이유 Splunk 정보 수상 및 인증 고객 사례 Splunk 대 경쟁업체 파트너 모든 리소스 보기 고객 지원 지원 포털 Splunk에 문의 Splunk 응답 페이지 시스템 상태 Cisco 서포트 앱다이나믹스 지원 제품 보안 업데이트 로그인 가입하기 나의 대시 보드 인스턴스 나의 교육 로그 아웃 PRODUCT LOGINS Splunk Observability Cloud Splunk Cloud Services Splunk On-Call Splunk Synthetic Monitoring Splunk Web Optimization Splunk AppDynamics Splunk 엔터프라이즈 시큐리티 Splunk 엔터프라이즈 시큐리티 Splunk 엔터프라이즈 시큐리티 기능 구성 구성 SIEM SOAR UEBA More Splunk 엔터프라이즈 시큐리티 TDIR 통합 도구의 무분별한 확장 감소 AI를 통한 가속화 SOC의 역량 강화 단절된 도구에 지치셨나요? 위협 탐지, 조사, 대응(TDIR)의 새로운 표준을 만나보세요. Enterprise Security(ES)는 에이전트 AI, SOAR, UEBA, SIEM과 원활하게 통합된 통합 TDIR 플랫폼입니다. 안내를 받아 둘러보기를 시작하세요 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); Splunk를 사용하여 새로운 위협을 찾고 차단하세요 Splunk Enterprise Security는 고객이 경고로 인한 피로를 줄이고, 보안 결과를 빠르게 얻고, 위험을 크게 최소화하고, 에이전트 AI 시대에 맞게 복원력을 강화하는 데 도움을 줍니다. 전체 스펙트럼 가시성 111% 더 많은 위협의 정확한 탐지 1 간소화된 경험 64% SecOps 효율성 향상 2 SOC 가속화 55% 더 빠른 사고 해결 1 x 그 외 고객 최고의 AI 기반 SecOps 플랫폼으로 분석가의 피로를 없애세요 데이터의 완전한 가시성을 확보하세요 Enterprise Security는 데이터가 어디에 있든 모든 도메인, 클라우드, 장치에서 데이터를 관리하고, 검색하고, 분석할 수 있도록 도와줍니다. 광범위한 가시성, AI 기반 탐지, AI 기반 경고 우선순위 지정 기능을 통해 SOC 팀은 실제 위협 탐지에 집중하고 정확도 높은 경고에 신속하게 대응할 수 있습니다. TDIR을 하나의 보안 플랫폼으로 통합하세요 탐지, 조사, 대응을 통합하는 엔드투엔드 플랫폼으로 사일로와 작업 전환을 없애세요. Enterprise Security는 SOC 워크플로를 중앙 집중화하여 탐지부터 문제 해결까지 모든 단계를 직관적인 단일 작업 공간 내에서 간소화합니다. UEBA를 사용하여 내부자 위협 및 제로데이 공격을 탐지하세요 Enterprise Security는 머신 러닝 기반의 사용자 및 엔터티 행동 분석(UEBA)을 사용하여 이상 징후와 행동 변화를 식별함으로써 팀이 계정 및 자산 손상을 완화하도록 지원합니다. SOC 전반에 걸친 자동화 및 추가 문맥 정보를 이용하세요 각 SOC 구성원이 보안 오케스트레이션, 자동화, 대응(SOAR) 및 자동 위협 강화를 통해 자동화를 활용할 수 있도록 지원합니다. 조사를 간소화하고, 대응 계획을 사용하여 추측을 없애며, 일관된 대응을 보장합니다. AI 기반 워크플로로 모든 분석가의 역량을 강화하세요 모든 분석가에게 AI를 제공하여 수동 작업을 최소화하고, 조사를 가속화하며, 자연어 쿼리, 단계별 안내 워크플로, 즉각적인 요약 및 자동화된 보고서를 사용하여 더 빠르게 대응할 수 있습니다. 자신 있게 탐지 규칙을 배포하고 평균 탐지 시간을 줄이세요 Detection Studio*는 엔지니어가 탐지 규칙을 원활하게 테스트, 배포, 모니터링할 수 있도록 완전한 탐지 라이프사이클 경험을 제공합니다. MITRE ATT&CK® 프레임워크에 매핑되는 커버리지를 측정하고 개선하여 팀이 진화하는 TTP를 따라잡고 탐지 취약점에 신속하게 조치를 취할 수 있게 만드세요. *가능한 경우 알파 버전에서 제공됩니다. 더 많은 Enterprise Security 기능을 살펴보세요 모든 기능 보기 리스크 기반 경보(RBA) SOAR UEBA 리스크 및 탐지 조정 AI 어시스턴트 데이터 관리 및 페더레이션 리스크 기반 경보(RBA) 위협 탐지 가속화 및 대응 우선화 정확도 높은 위협 탐지를 통해 SOC의 생산성을 향상시키고 경고 양을 최대 90%까지 줄입니다. RBA는 실제 위협 탐지 비율을 높이고 팀이 가장 중요한 위협에 집중할 수 있도록 보장합니다. SOAR 자동화된 TDIR 워크플로를 통해 효율성을 높이세요 Splunk SOAR은 보안 워크플로를 자동화하여 수동 작업, 경고 피로 및 대응 시간을 줄입니다. Splunk Enterprise Security와 원활하게 통합되어 대규모 TDIR 자동화가 가능합니다. UEBA 리스크 및 탐지 조정 머신 러닝 모델과 사용자 중심 워크플로를 맞춤화하세요 머신 러닝 및 사용자 행동 모델을 맞춤화하여 특정 프로세스, 정책, 자산, 사용자 역할, 운영 기능을 반영하고, 내부자 및 고급 위협을 탐지하고 완화하는 능력을 향상시키세요. AI 어시스턴트 즉각적인 AI를 활용하여 지침, 쿼리, 요약, 보고서를 작성하세요 워크플로에 통합된 AI 어시스턴트를 통해 모든 분석가에게 즉각적 맞춤형 조사 지침, 간단히 생성된 쿼리, 명확한 요약, 자동화된 보고서를 제공하여 업무를 지원합니다.* *사용 가능한 경우 제한적 제공 데이터 관리 및 페더레이션 보안팀을 위한 데이터 관리 및 접근성 간소화 고급 관리 기능(예: 연합 검색 및 연합 분석)을 통해 경계 없는 데이터 가시성을 확보하고, 보안 사용 사례의 비용을 최적화하며, SOC가 그 어느 때보다 빠르게 위협을 탐지, 조사, 대응할 수 있도록 지원합니다. Enterprise Security(ES) 구매 옵션 자세히 알아보기 ES Essentials ES Premier 포함 항목 보안 모니터링 온프레미스, 하이브리드 및 멀티클라우드 환경을 실시간으로 모니터링하여 위협을 조기에 발견하고 리스크를 줄입니다. ✓ ✓ 위협 탐지 RBA 및 Detection Studio*를 사용하여 위협을 빠르고 정확하게 탐지하고 실시간 모니터링, 고급 분석 및 위협 인텔리전스를 이용합니다. *Alpha에서 사용 가능한 경우 ✓ ✓ 위협 조사 고급 검색, 상관관계, 분석을 결합하여 협업과 효율적인 워크플로를 가능하게 하는 통합 플랫폼을 사용하여 모든 위협의 세부 정보를 파악합니다. ✓ ✓ 위협 헌팅 강력한 검색, 상관관계, 분석 및 위협 인텔리전스 보강을 활용하여 숨겨진 위협과 새로운 위협을 밝혀냅니다. ✓ ✓ 자동화 모든 분석가가 사용할 수 있는 SOAR을 통해 작업을 자동화하고, 워크플로를 조정하며, 사용자 정의 가능한 플레이북을 실행합니다. ✓ 내부자 위협 탐지 실시간 모니터링과 고급 머신 러닝을 사용하여 내부자 위협을 조기에 발견하고 이상 징후를 플래그하며 정확도 높은 경고를 표시합니다. ✓ 데이터 관리 및 페더레이션* 연합 검색 및 연합 분석을 통해 데이터 가시성을 확보합니다. *추가 비용이 발생할 수 있습니다. ✓ ✓ 고객이 Splunk를 통해 어떤 가치를 얻고 있는지 알아보세요 모든 사례 보기 40% 사이버 위협 탐지 능력이 향상되었으며, 기록적인 시간 내에 공격을 차단할 수 있게 되었습니다. 사례 읽기 $120B 시가총액이 보호되고 위험 기반 경고를 통해 불필요한 경고가 크게 감소했습니다. 사례 읽기 3배 더 빠른 위협 대응 시간과 더 많은 팀 역량이 확보되어 가치가 더 큰 업무에 집중할 수 있게 되었습니다. 사례 읽기 x FAQ(자주 묻는 질문) Splunk Enterprise Security(ES)란 무엇인가요? Splunk Enterprise Security(ES)는 위협 탐지, 조사, 대응(TDIR) 기능을 통합하여 보안 워크플로를 통합된 경험으로 간소화하는 플랫폼입니다. 보안 정보 및 이벤트 관리(SIEM), 에이전트 AI, 자동화를 위한 SOAR, UEBA, 탐지 정확도 및 응답 속도 향상을 위한 AI/ML 등의 기능이 통합됩니다. Enterprise Security는 이러한 기능을 하나의 인터페이스로 통합함으로써, 비효율성을 줄이고 도구의 단절을 없애며, SOC 팀이 위협을 더 효과적으로 탐지하고, 조사하고, 대응할 수 있게 보장합니다. 고객으로서 ES Premier로 전환할 때 얻을 수 있는 즉각적인 이점은 무엇인가요? ES Premier로 전환하면 현재 Splunk 고객에게 즉각적이고 실질적인 혜택을 제공합니다. 혜택에는 다음이 포함됩니다. 도구 통합: 다양한 보안 도구를 TDIR을 위한 통합 플랫폼으로 통합하면 워크플로가 간소화되고 팀이 사고를 관리할 때 직면하는 시간과 복잡성이 크게 줄어듭니다. 고객은 다양한 도구를 하나의 인터페이스로 통합하여 작업 전환을 제거하고 수동 작업 단계를 줄이며 위협과 경고를 중앙에서 파악할 수 있습니다. 통합 머신러닝 기반 UEBA: 고객은 비정상적인 사용자 및 엔터티 행동에 대한 심층적인 인사이트를 얻어 내부자 위협, 손상된 계정, 고급 공격 방법(제로데이 공격 등)을 식별할 수 있습니다. 전체 SOC를 위한 SOAR 기능: ES Premier는 보안 오케스트레이션, 자동화, 대응(SOAR)에 존재했던 사용 권한 제한을 제거하여, 역할이나 직급에 관계없이 모든 팀원이 자동화를 사용할 수 있게 합니다. 이것은 모든 SOC 역할이 워크플로우를 간소화하고, 경고를 풍부하게 하며, 대응 조치를 실행할 수 있도록 보장합니다. 지금 ES Premier를 도입하면 고객은 운영 비효율성을 줄이고, 보안 운영을 확장하며, 최신 AI 기반 기능을 활용할 수 있습니다. *사용 가능한 경우 제한적으로 제공됩니다. Splunk Enterprise Security Essentials와 Enterprise Security Premier의 차이점은 무엇인가요? 현재 Enterprise Security는 고객이 선택할 수 있는 두 가지 에디션인 Essentials와 Premier를 제공합니다. ES Essentials는 잘 알려진 SIEM뿐만 아니라 보안용 AI 어시스턴트(AIA)와 사용 가능한 경우 Detection Studio도 제공합니다. Splunk Enterprise Security Essentials는 10년 넘게 시장을 선도해 온 보안 정보 및 이벤트 관리(SIEM) 솔루션입니다. 한편, Splunk Enterprise Security Premier는 단순한 SIEM의 기능을 넘어서는 확장성을 제공합니다. ES Premier는 위협 탐지, 조사, 대응을 위한 새로운 통합 플랫폼으로, SIEM, UEBA, SOAR, AI 기능을 하나의 플랫폼에 결합하여 오늘날 급변하는 보안 환경에 대응합니다. Splunk Enterprise Security는 에이전트 AI를 통해 SOC 효율성을 어떻게 향상시키나요? Splunk Enterprise Security(ES)는 에이전트 AI를 활용하여 점진적인 자율성을 통해 일상적이고 복잡도가 낮은 작업을 자동화함으로써 보안 운영 센터(SOC) 팀의 효율성을 높입니다. 이 접근 방식은 SOC 팀이 인간의 감독을 유지하면서 완전 자동화된 작업에서 승인이 필요한 AI 제안까지 AI의 역할을 점진적으로 확대할 수 있게 합니다. ES에는 멀웨어 리버싱과 같은 고급 기능이 포함되어 있으며, 이는 악성 스크립트를 한 줄씩 자동으로 분해하고, 침해 지표를 추출하며, 회피 기술을 플래그하고, 반복되는 행동을 그룹화하여 분석 속도를 높입니다. 또한, 경고를 평가하고 우선순위를 지정하며 설명하는 분류 에이전트가 있어 SOC 팀이 가장 중요한 위협에 집중할 수 있도록 도와줍니다. SOC 팀은 자연어 명령어를 통해 고급 기술 없이도 자동화 플레이북과 탐지 규칙을 신속하게 구축하고 맞춤화할 수 있습니다. ES는 경고 강화, 분류, 조사, 멀웨어 분석을 간소화하여 운영 부담을 줄이고 SOC 분석가가 중요한 보안 작업에 집중할 수 있게 합니다. 1 Splunk가 후원한 IDC Business Value Snapshot, Splunk 시큐리티의 비즈니스 가치: 통합 TDIR 플랫폼, #US53392325, 2025년 5월 2 Splunk 시큐리티의 경제적 이점 분석, Enterprise Strategy Group, 2023년 9월 Enterprise Security로 시작하세요 Splunk가 전체 TDIR 워크플로를 하나의 강력하고 통합된 에이전트 SOC 플랫폼으로 통합하는 방법을 알아보세요. 가이드식 둘러보기 기업 기업 Splunk 소개 커리어 Splunk는 어떻게 비교되나요 리더쉽 뉴스룸 파트너 Splunk의 정책적 입장 Splunk는 보호합니다 SURGe 왜 Splunk인가? 제품 제품 무료 평가판 및 다운로드 가격 문의 모든 제품 보기 스플렁크 사이트 스플렁크 사이트 .conf 문건 투자 설명(IR) 교육 및 인증 Splunk 스토어 비디오 모든 리소스 보기 Splunk에 문의 Splunk에 문의 영업팀에 문의 서포트에 문의 사용자 리뷰 사용자 리뷰 Gartner Peer Insights™ PeerSpot TrustRadius 스플렁크 로고 Twitter Facebook Linked In Youtube Instagram --> © 2005 - 2026 Splunk LLC 모든 권리는 Splunk에 있습니다. 법률 프라이버시 사이트맵 Cookies 웹사이트 이용약관 Modern Slavery 스플렁크 로고 © 2005 - 2026 Splunk LLC 모든 권리는 Splunk에 있습니다. × | 2026-01-13T09:29:33 |
https://reports.jenkins.io/jelly-taglib-ref.html#dropdowns | 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://www.atlassian.com/ja/software/jira/guides/issues/tutorials | Jira Software 課題のチュートリアル | Atlassian Close あなたの言語 でこのページを表示しますか？ すべての言語 言語を選択する 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 無料で入手する 機能 すべての機能 Jira の Rovo Back ソリューション チーム ユースケース 企業規模 チーム マーケティング エンジニアリング デザイン オペレーション 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 クエリ言語) を使用して構造的なクエリを作成して作業項目を検索できます。 注意: チーム管理対象プロジェクトでは、作業項目ナビゲーターは既定では使用できません。この機能を有効にするには、[ プロジェクト設定 ] > [ 機能 ] > [ 作業項目ナビゲーター ] に移動します。 作業タイプをプロジェクトに追加する チーム管理対象プロジェクト: 左側のサイドバー ナビゲーションで [プロジェクト設定] を選択し、[作業タイプ] を選択し、[+ 作業タイプを追加] を押します。 作業タイプに含めるフィールドのタイプをドラッグ & ドロップして、各フィールド タイプに名前を付けます。必要に応じて、各フィールドの既定値を設定することもできます。 企業管理対象プロジェクト: 作業項目をリンクする方法 作業項目を開きます。 作業項目モーダルの上部にある [ 作業項目をリンク ] を選択します。 作業項目リンクのタイプを選択します (例: "this work item is blocked by...")。 作業項目キーをすべて入力して (ABC-123 など) リンクする作業項目を指定します。 リンク を選択します。 作業項目のレイアウトを設定する ボードから任意の作業項目を選択します。 作業項目ビューの右下にある [ 設定 ] を選択します。 作業項目フィールドを適切な領域にドラッグ & ドロップします。 会社名 アトラシアンで働く イベント ブログ 投資家向け アトラシアン基金 プレスキット お問い合わせ 製品 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket すべての製品を見る リソース 技術サポート 購入とライセンス アトラシアン コミュニティ ナレッジ ベース Marketplace アカウント管理 サポートを依頼する 学ぶ パートナー トレーニングと認定 ドキュメント 開発者向けリソース エンタープライズ サービス 全リソースを見る Copyright © 2025 Atlassian プライバシーポリシー 利用規約 サイト管理者情報 言語の選択 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:33 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3Apassword | 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://wiki.documentfoundation.org/Special:MyLanguage/Events | Events - 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 Contents move to sidebar hide Beginning 1 Event Calendar 2 Years 3 Current Year Toggle Current Year subsection 3.1 Global 3.2 EMEA 3.3 India/APAC 3.4 Ibero-America 4 Other Events 5 Beer Bank Toggle the table of contents Events 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 Calendar Document Freedom Day LibreOffice Conference This page is the central resource for Events that members of the LibreOffice and The Document Foundation communities attend. Events By Year ← previous  ▪  next → Dates -------- Location everywhere Website Events Event Calendar Help keep this up-to-date: Email mike.saunders documentfoundation.org (or post on the marketing mailing list) with details if you are organising or attending an event on behalf of the LibreOffice community Events on this calendar are displayed in GMT/UTC. Visit the Events Calendar FAQ for more information. View the events calendar in Nextcloud LibreOffice Conference Kit Years Keep track of events by creating an Event/ page for each of them. List details, participants, link to slides and photos, etc. Click on a year below: 2025 2024 2023 2022 2021 2020 2019 2018 2017 2016 2015 2014 2013 2012 2011 Current Year Global Name Country, City Date from to Attendees Call for Papers Comments Document Freedom Day 2025 2025-03-26 Main page LibreOffice Conference 2025 (Official Annual) Members of LibreOffice community https://conference.libreoffice.org/ In Person Event EMEA Europe, Middle East & Africa Name City, Country Date from ... to ... Attendees Call for Papers Comments FOSDEM In Person Only 2025-02-01 2025-02-02 main page Linuxdays Prague 2025-10-04 2025-10-05 main page . LibreOffice booth. India/APAC India, Asia and Australia Name City, Country Date from ... to ... Attendees Call for Papers Comments LibreOffice Hackfest Online #225 Japan, Online 2025-01-06 2025-01-06 Shinji Enoki, Hidemune Tanaka, Sudo, Jun Meguro Event page (JA) LibreOffice Hackfest Online #226 Japan, Online 2025-01-13 2025-01-13 Shinji Enoki, Hidemune Tanaka, Sudo, Jun Meguro Event page (JA) LibreOffice Hackfest Online #227 Japan, Online 2025-01-20 2025-01-20 Shinji Enoki, Hidemune Tanaka, Sudo, Jun Meguro Event page (JA) LibreOffice day vol.109 @Coworking-Kinkan Japan, Osaka 2025-01-23 2025-01-23 Shinji Enoki Event page (JA) Open Source Conference 2025 Osaka Japan, Osaka 2025-01-25 2025-01-25 Shinji Enoki, Namikawa Event page (JA) , booth LibreOffice Hackfest Online #228 Japan, Online 2025-01-27 2025-01-27 Shinji Enoki, Sudo, Jun Meguro Event page (JA) LibreOffice Hackfest Online #229 Japan, Online 2025-02-10 2025-02-10 Shinji Enoki, Sudo, Jun Meguro Event page (JA) LibreOffice Hackfest Online #230 Japan, Online 2025-02-17 2025-02-17 Shinji Enoki, Hidemune Tanaka, Sudo, Jun Meguro Event page (JA) Open Source Conference 2025 Tokyo/Spring Japan, Tokyo 2025-02-21 2025-02-22 Shinji Enoki, Sudo, Tomaž Vajngerl, Kenta Ito, Po Event page (JA) booth LibreOffice/FLOSS/OpenData Hackfest Tokyo 2025-02 Japan, Tokyo 2025-02-23 2025-02-23 Shinji Enoki, Sudo Event page (JA) LibreOffice Hackfest Online #231 Japan, Online 2025-02-24 2025-02-24 Shinji Enoki, Hidemune Tanaka, Sudo, Jun Meguro Event page (JA) LibreOffice day vol.110 @Coworking-Kinkan Japan, Osaka 2025-02-27 2025-02-27 Shinji Enoki Event page (JA) LibreOffice Hackfest Online #232 Japan, Online 2025-03-03 2025-03-03 Shinji Enoki, Sudo, Jun Meguro Event page (JA) LibreOffice Hackfest Online #233 Japan, Online 2025-03-10 2025-03-10 Shinji Enoki, Hidemune Tanaka, Sudo, Jun Meguro Event page (JA) LibreOffice Hackfest Online #234 Japan, Online 2025-03-19 2025-03-19 Shinji Enoki, Hidemune Tanaka, Sudo, Jun Meguro Event page (JA) LibreOffice Hackfest Online #235 Japan, Online 2025-03-24 2025-03-24 Shinji Enoki, Hidemune Tanaka, Sudo, Jun Meguro Event page (JA) Document Freedom Day 2025 JA online meetup Japan, Online 2025-03-26 2025-03-26 Shinji Enoki, Hidemune Tanaka, Sudo, Jun Meguro Event page (JA) LibreOffice Hackfest Online #236 Japan, Online 2025-03-31 2025-03-31 Shinji Enoki, Hidemune Tanaka, Sudo, Jun Meguro Event page (JA) LibreOffice Hackfest Online #237 Japan, Online 2025-04-07 2025-04-07 Shinji Enoki, Hidemune Tanaka, Sudo Event page (JA) LibreOffice Hackfest Online #238 Japan, Online 2025-04-14 2025-04-14 Shinji Enoki, Sudo Event page (JA) LibreOffice Online Study Party #13 Japan, Online 2025-04-19 2025-04-19 Jun Meguro, Shinji Enoki, Yuichi Kojima Event page (JA) LibreOffice Hackfest Online #239 Japan, Online 2025-04-21 2025-04-21 Shinji Enoki, Sudo, Ironami, Sabr0 Event page (JA) LibreOffice day vol.111 @Minna no Toshokan Saikuru Japan, Osaka 2025-04-24 2025-04-24 Shinji Enoki Event page (JA) LibreOffice Hackfest Online #240 Japan, Online 2025-04-28 2025-04-28 Shinji Enoki, Sudo, Ironami, Sabr0 Event page (JA) LibreOffice Hackfest Online #241 Japan, Online 2025-05-05 2025-05-05 Shinji Enoki, Sudo, Ironami, Jun Meguro Event page (JA) LibreOffice Hackfest Online #242 Japan, Online 2025-05-12 2025-05-12 Shinji Enoki, Ironami, Sudo Event page (JA) Open Source Conference 2025 Shirahama Japan, Wakayama 2025-05-17 2025-05-17 Shinji Enoki Event page (JA) booth LibreOffice Hackfest Online #243 Japan, Online 2025-05-19 2025-05-19 Shinji Enoki, Ironami, Sudo Event page (JA) LibreOffice day vol.112 @Minna no Toshokan Saikuru Japan, Osaka 2025-05-22 2025-05-22 Shinji Enoki Event page (JA) LibreOffice Hackfest Online #244 Japan, Online 2025-05-26 2025-05-26 Shinji Enoki, Ironami, Sudo, Sabr0 Event page (JA) Open Source Conference 2025 Nagoya Japan, Nagoya 2025-05-31 2025-05-31 Shinji Enoki, Masaki Tamakoshi Event page (JA) booth FLOSS/LibreOffice/OpenData Hackfest Nagoya 2025-06 Japan, Nagoya 2025-06-01 2025-06-01 Shinji Enoki Event page (JA) LibreOffice Hackfest Online #245 Japan, Online 2025-06-02 2025-06-02 Shinji Enoki, Sudo Event page (JA) LibreOffice Hackfest Online #246 Japan, Online 2025-06-09 2025-06-09 Shinji Enoki, Sudo, Ironami Event page (JA) LibreOffice Hackfest Online #247 Japan, Online 2025-06-16 2025-06-16 Shinji Enoki, Sudo Event page (JA) LibreOffice Hackfest Online #248 Japan, Online 2025-06-23 2025-06-23 Shinji Enoki, Sudo, Ironami Event page (JA) LibreOffice Hackfest Online #249 Japan, Online 2025-06-30 2025-06-30 Shinji Enoki, Sudo, Ironami Event page (JA) Open Source Conference 2025 Hokkaido Japan, Sapporo 2025-07-05 2025-07-05 Shinji Enoki Event page (JA) booth FLOSS/LibreOffice/OpenData Hackfest Hokkaido 2025 Japan, Sapporo 2025-07-06 2025-07-06 Shinji Enoki Event page (JA) LibreOffice Hackfest Online #250 Japan, Online 2025-07-07 2025-07-07 Shinji Enoki, Sudo, Ironami Event page (JA) LibreOffice Hackfest Online #251 Japan, Online 2025-07-14 2025-07-14 Shinji Enoki, Sudo, Ironami Event page (JA) LibreOffice Hackfest Online #252 Japan, Online 2025-07-21 2025-07-21 Shinji Enoki, Sudo, Jun Meguro Event page (JA) LibreOffice day vol.113 @Minna no Toshokan Saikuru Japan, Osaka 2025-07-24 2025-07-24 Shinji Enoki Event page (JA) LibreOffice Hackfest Online #253 Japan, Online 2025-07-29 2025-07-29 Shinji Enoki, Sudo, Ironami Event page (JA) Open Source Conference 2025 Kyoto Japan, Kyoto 2025-08-03 2025-08-03 Shinji Enoki Event page (JA) booth LibreOffice Hackfest Online #254 Japan, Online 2025-08-04 2025-08-04 Shinji Enoki, Sudo, Ironami Event page (JA) COSCUP 2025 Taiwan, Taipei 2025-08-09 2025-08-10 Franklin Weng, Shinji Enoki, Sudo, Kenta Ito, Yuichi Kojima talk1 , talk2 , talk3 UbuCon Korea 2025 Seoul, South Korea 2025-08-10 2025-08-10 DaeHyun Sung Talk abstract page (Korean) LibreOffice Hackfest Online #255 Japan, Online 2025-08-18 2025-08-18 Shinji Enoki, Sudo Event page (JA) LibreOffice Online Study Party #14 Japan, Online 2025-08-24 2025-08-24 Jun Meguro, Shinji Enoki, sudo, Kenta Ito Event page (JA) LibreOffice Hackfest Online #256 Japan, Online 2025-08-25 2025-08-25 Shinji Enoki, Sudo, Ironami, Yuichi Kojima Event page (JA) LibreOffice Hackfest Online #257 Japan, Online 2025-09-02 2025-09-02 Shinji Enoki, Sudo, Ironami, Yuichi Kojima Event page (JA) LibreOffice Hackfest Online #258 Japan, Online 2025-09-15 2025-09-15 Shinji Enoki, Sudo, Yuichi Kojima Event page (JA) LibreOffice Hackfest Online #259 Japan, Online 2025-09-22 2025-09-22 Shinji Enoki, Sudo, Ironami, Yuichi Kojima Event page (JA) LibreOffice Hackfest Online #260 Japan, Online 2025-09-29 2025-09-29 Shinji Enoki, Sudo, Ironami, Yuichi Kojima Event page (JA) LibreOffice Hackfest Online #261 Japan, Online 2025-10-06 2025-10-06 Shinji Enoki Event page (JA) LibreOffice Hackfest Online #262 Japan, Online 2025-10-13 2025-10-13 Shinji Enoki, Ironami, Yuichi Kojima Event page (JA) LibreOffice Hackfest Online #263 Japan, Online 2025-10-20 2025-10-20 Shinji Enoki, Ironami, Yuichi Kojima Event page (JA) Open Source Conference 2025 Tokyo/Fall Japan, Tokyo 2025-10-25 2025-10-25 Shinji Enoki, Sudo, Kenta Ito, Ironami, Yuichi Kojima Event page (JA) booth FLOSS/LibreOffice/OpenData Hackfest Tokyo 2025-10 Japan, Tokyo 2025-10-26 2025-10-26 Shinji Enoki, Sudo, Ironami Event page (JA) LibreOffice Hackfest Online #264 Japan, Online 2025-10-27 2025-10-27 Shinji Enoki, Ironami, Sudo Event page (JA) LibreOffice Hackfest Online #265 Japan, Online 2025-11-03 2025-11-03 Shinji Enoki, Ironami, Sudo Event page (JA) Kansai Open Forum (KOF) 2025 Japan, Osaka 2025-11-08 2025-11-08 Shinji Enoki Event page (JA) Seminar FOSS For All Conference 2025 Seoul, Korea 2025-11-08 2025-11-08 DaeHyun Sung Event page (KO) LibreOffice Hackfest Online #266 Japan, Online 2025-11-11 2025-11-11 Shinji Enoki, Sudo Event page (JA) LibreOffice Hackfest Online #267 Japan, Online 2025-11-17 2025-11-17 Shinji Enoki Event page (JA) Open Source Conference 2025 Fukuoka Japan, Fukuoka 2025-11-22 2025-11-22 Shinji Enoki, Sudo, koutarou Watanabe Event page (JA) , booth LibreOffice Hackfest Online #268 Japan, Online 2025-11-25 2025-11-25 Shinji Enoki, Sudo, Sabr0 Event page (JA) LibreOffice Hackfest Online #269 Japan, Online 2025-12-02 2025-12-02 Shinji Enoki, Sudo, Hidemune Tanaka Event page (JA) LibreOffice Asia Conference 2025 Japan, Tokyo 2025-12-13 2025-12-14 Shinji Enoki, Fuminobu Takeyama, Sudo, Naruhiko Ogasawara, Kazuhiko Inaba, Hatori, Hayama, Kankawa cfp Wiki , web Registration , Party registration LibreOffice Hackfest Online #270 Japan, Online 2025-12-23 2025-12-23 Shinji Enoki, Sudo, Hidemune Tanaka Event page (JA) Ibero-America Ibero-American countries Name City, Country Date from ... to ... Attendees Comments Other Events Here are some upcoming events where it may be useful to have someone from the LibreOffice community attending: Name Country, City Date(s) Comments Beer Bank If you owe someone a beer, you maybe both meet at one of our events, so add it on that page with the reason why :) Beer Bank Retrieved from " https://wiki.documentfoundation.org/index.php?title=Events&oldid=836500 " Category : Events This page was last edited 15:57, 25 June 2025 by Shinji Enoki . Based on work by Regis Perdreau and Dennis Roczek 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:33 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3Acheckbox | 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#newFromList | 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://giga.global/get-involved/governments/ | Get Involved | Government Support for School Connectivity | Giga What We Do How We Work Mapping Modeling Finance Contracting Capacity Development Our Solutions Where We Work Who We Are Our Story Our Collaboration Our Centres Get Involved Governments Partnerships Events and Trainings Resources Newsroom Impact Press Media Kit Multimedia Digital Repository Contact Us Giga Maps Governments Home Get Involved Governments Home Get Involved Governments Governments Giga works with Ministries of ICT and Education, ICT regulators and Universal Service Agencies to find solutions to fit each country’s unique context and local challenges. We support in a number key areas: School mapping and real-time monitoring of connectivity. infrastructure modeling and cost analysis, financing and contracting, plus capacity development. School mapping and real-time monitoring of connectivity Having an accurate map of school locations and their connectivity status is critical to help governments connect schools to the internet. Giga maps and verifies the precise locations of schools, using data collected from government bodies, private companies, open-data sources, satellite imagery and artificial intelligence models. We also continuously monitor the real-time connectivity status of schools for troubleshooting and improvement of quality of service. Mapping schools helps us understand our goal. Infrastructure modeling and cost analysis Giga analyses the current infrastructure, identifies needs and costs, and provides a cost analysis of connectivity options. We collect and use data to identify gaps, understand costs and design connectivity plans. This includes school locations, connectivity status and electricity supply, distance to telecommunication infrastructure and other infrastructure data such as road networks or population density. Cost calculations estimate the investment required based on selected technologies and routes. Factors include fiber length, terrain type and last-mile deployment challenges. We evaluate the impact of a government’s policy and regulatory choices on school connectivity plans, and make recommendations to facilitate connectivity. All this information is visualized in interactive maps to help governments plan and design a connectivity strategy to achieve high-quality, sustainable school connectivity. Financing and investment facilitation for sustainable connectivity Giga advises governments on options for scalable, blended finance solutions to bridge the investment gap and deliver connectivity to every school in the world. Giga facilitates access to development loans, technical assistance grants, and blended finance instruments that align with national priorities, instead of disbursing grants or providing funding directly to countries. By coordinating public-private partnerships, engaging international finance institutions and advocating for the inclusion of last-mile school connectivity into large infrastructure projects, we unlock new funding streams, aggregate private capital and accelerate digital infrastructure finance. Giga prioritizes commercial viability of projects to attract a broad set of capital partners and enable innovative, blended financing solutions. By piloting sustainable business models underpinned by connectivity credits, Giga also promotes the long-term sustainability of connectivity. From initial project planning to monitoring service quality, Giga supports governments throughout the lifecycle of connectivity projects, ensuring that the desired social and financial outcomes are achieved. Contracting for cost reduction Giga also assists governments in evaluating market conditions in the ICT sector and provides guidance on procurement and competitive bidding processes for school connectivity. This effort helps mitigate risks and leads to a reduction in connectivity costs by assessing providers’ capabilities to deliver infrastructure, equipment and services. Giga has helped realize significant savings for countries. With Giga’s support, governments have successfully negotiated better connectivity contracts, resulting in significant cost savings. Capacity development Strengthening capacity to advance school connectivity underpins all four of Giga’s primary activities. Giga’s capacity development programs help government leaders and tech experts design effective, tailored connectivity strategies in the countries where Giga works. Engage with Giga Giga operates through partnerships at every level – engaging governments, UN agencies, private sector leaders, research institutions and funding organizations to achieve universal school connectivity. Our mission to connect every school to the internet is ambitious, and it cannot be achieved alone. Let’s build a connected future together Get involved Stay connected with Giga Join the Newsletter Follow us on Home FAQ Jobs Contact us Terms of Use Privacy Notice © Copyright 2025 Giga | 2026-01-13T09:29:33 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3Aclass-entry | 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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.