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://giga.global/get-involved/ | Get Involved | Help Connect Every School to the Internet | 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 Get Involved Home Get Involved Home Get Involved Get Involved Let’s build a connected future together. Learn more about how you can get involved today. Governments Governments can leverage our suite of products and services to advance school connectivity. Find out more. Governments Partnerships Collaboration is core to Giga success and growth, with partners providing invaluable support including funding, technical expertise, data and infrastructure. Partnerships Events and Trainings Explore Giga’s upcoming events in Geneva, Barcelona, and around the world. Events and Trainings 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:32 |
https://www.atlassian.com/ko/jira/solutions/planning#tab-cdd6eeec-3ac3-4e70-8c7d-6d694d4e327d | 계획 프로젝트 관리 소프트웨어 | Atlassian Close 선택한 언어 로 이 페이지를 보고 계십니까? 모든 언어 언어를 선택합니다. 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 무료로 시작 기능 모든 기능 Jira의 Rovo Back 솔루션 팀 사용 사례 회사 규모 팀 마케팅 엔지니어링 디자인 운영팀 IT 사용 사례 시작하기 계획 캠페인 관리 애자일 프로젝트 관리 프로그램 관리 회사 규모 Enterprise Back 제품 가이드 템플릿 템플릿 모든 템플릿 소프트웨어 개발 마케팅 디자인 영업 운영팀 서비스 매니지먼트 HR 법무 IT 운영 재무 Jira Service Management 템플릿 Back 가격 자세한 내용 + 간략히 보기 - 무료로 시작 Back 무료로 시작 Atlassian이 2025년 Gartner Magic Quadrant™의 공동 작업 관리 부문에서 리더로 선정되었습니다! 자세히 알아보기 계획을 위한 Jira 모든 팀을 위한 유연한 계획 팀 및 이해 관계자가 동기화, 비동기화 및 목표에 정렬된 상태를 유지하세요. Jira Free 받기 Atlassian으로 팀 공동 작업을 강화하는 30만 명 이상의 고객과 함께하세요 계획에 Jira를 사용하는 이유는 무엇입니까? 작업 시각화 복잡한 프로젝트를 관리하기 쉬운 작은 작업으로 나누세요. 작업을 쉽게 추가하고 조정하여 다양한 작업의 시기 및 순서를 시각화하세요. 간편한 공유 작업이 진행되면서 타임라인이 실시간으로 업데이트되어 팀, 리더 및 이해 관계자와 즉시 공유할 준비가 됩니다. 원하는 스타일로 계획 처음부터 시작하든 템플릿을 사용하든 조건 및 요구 사항에 따라 자유롭게 계획을 사용자 지정할 수 있습니다. 작업이 회사 목표에 어떻게 기여하는지 확인하세요 계획 기능 비교 Advanced Basic Jira Premium의 고급 계획 기능인 계획 을 사용하면 여러 팀이 공동의 프로그램 또는 목표에 대해 공동 작업할 수 있습니다. 모든 Jira 에디션에서 사용할 수 있는 프로젝트 보기인 타임라인 을 사용하면 단일 팀 내에서 작업을 계획하고 추적할 수 있습니다. Jira로 교차 기능 작업을 추진하세요 큰 그림 추적 계획 기능 비교 Advanced Basic 계획을 통해 여러 팀 및 프로젝트에 걸쳐 작업을 추적할 수 있습니다. 계획 요약 화면에서 작업 진행률, 종속성 및 팀 작업 수용량을 총체적으로 확인할 수 있습니다. 타임라인 보기를 통해 단일 팀 의 작업을 계획하고 종속성을 추적할 수 있습니다. 종속성 미리 파악 계획 기능 비교 Advanced Basic 팀, 프로젝트 등 간 종속성을 매핑하여 잠재적인 리소싱 또는 일정 충돌을 미리 파악하세요. 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. 팀 역량을 염두에 두고 계획 Advanced 전용 팀이 범위가 지정된 작업을 완료하는 데 필요한 역량을 갖추도록 하여 목표에 맞게 진행하세요. 스프린트별로 여러 팀의 작업 수용량을 확인하세요. 서로 다른 시나리오 구상 Advanced 전용 다양한 옵션 또는 최고 및 최악의 시나리오에 따라 계획을 여러 버전으로 만들어 잠재적인 결과에 대해 더 완전한 그림을 그리세요. 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의 사용자 지정 가능한 템플릿을 살펴보세요. 개략적인 계획 프로그램 또는 이니셔티브와 같은 대규모 작업을 계획하고 추적하고 보고하세요. 교차 팀 계획 여러 스크럼 팀 간에 작업 일정을 수립 및 할당하고 작업 수용량을 관리하고 진행률을 추적합니다. 프로젝트 관리 작업 체계화부터 타임라인 시각화까지, 팀이 프로젝트 진행률을 360도로 볼 수 있도록 하세요. 더 많은 템플릿 탐색 계획 리소스 자세히 알아보려면 무료 자습서, 문서 및 가이드를 살펴보세요. 계획에 Jira를 사용하는 방법 작업 계획, 진행률 추적 및 종속성 매핑 방법에 대한 자습서입니다. 가이드 보기 Jira를 사용한 전략적 계획 전략적 계획 프레임워크 및 이것이 큰 목표를 달성하는 데 어떻게 도움이 되는지 알아보세요. 자세히 알아보기 스프린트 계획 필수 사항 팀의 워크플로에 스크럼 방법론을 적용하기 위한 필수 사항입니다. 지금 살펴보기 업무 수행 방식의 혁신 조직 및 팀이 하나가 되어 일할 수 있는 곳. 무료로 시작 회사 구직 이벤트 블로그 투자자 관계 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:32 |
https://cloudflare.com/pl-pl/events/ | Wydarzenia Cloudflare | Cloudflare Zarejestruj się Języki English English (United Kingdom) Deutsch Español (Latinoamérica) Español (España) Français Italiano 日本語 한국어 Polski Português (Brasil) Русский 繁體中文 简体中文 Platforma Connectivity cloud Connectivity cloud Cloudflare oferuje ponad 60 usług z zakresu sieci, bezpieczeństwa i poprawiających wydajność. Enterprise Dla dużych i średnich organizacji Mała firma Dla małych organizacji Partner Zostań partnerem Cloudflare Przypadki użycia Modernizacja aplikacji Zwiększona wydajność Zapewnianie dostępności aplikacji Optymalizacja działania środowiska internetowego Modernizacja zabezpieczeń Zastąpienie VPN Ochrona przed phishingiem Zabezpieczanie aplikacji Internet i interfejsów API Modernizacja sieci Tworzenie sieci w kawiarniach Modernizacja WAN Uproszczenie sieci firmowej Tematyka CXO Wdrażaj AI Wprowadź SI do środowisk pracy i cyfrowych Zabezpieczenia SI Zapewnij bezpieczeństwo agentowych i generatywnych aplikacji AI. Zgodność ze standardami Usprawnienie procesu zapewnienia zgodności i minimalizowanie ryzyka Kryptografia postkwantowa Zabezpieczanie danych i spełnianie standardów zgodności Branże Opieka zdrowotna Bankowość Handel detaliczny Gry Sektor publiczny Zasoby Przewodniki po produktach Architektury referencyjne Raporty analityczne Angażowanie Wydarzenia Prezentacje Webinaria Warsztaty Umów się na prezentację Produkty Produkty Bezpieczeństwo w miejscu pracy Dostęp do sieci w modelu Zero Trust Bezpieczna brama internetowa Bezpieczeństwo poczty e‑mail Broker zabezpieczeń dostępu do chmury (CASB) Bezpieczeństwo aplikacji Ochrona przed atakami DDoS na warstwę L7 Zapora aplikacji internetowych Bezpieczeństwo API Zarządzanie dostępem botów Wydajność aplikacji CDN DNS Inteligentny routing Load balancing Sieci i SASE Ochrona przed atakami DDoS na warstwy L3/4 NaaS / SD — WAN Zapora jako usługa Połączenia międzysieciowe Plany i ceny Pakiety Enterprise Plany dla małych firm Plany indywidualne Porównaj plany Usługi globalne Pakiety wsparcia i sukcesu Zoptymalizowane doświadczenie Cloudflare Usługi profesjonalne Wdrożenie prowadzone przez ekspertów Technical Account Management Skoncentrowane zarządzanie techniczne Security Operations Service Monitorowanie i reagowanie Cloudflare Rejestracja domen Kupuj domeny i zarządzaj nimi 1.1.1.1 Free resolwer DNS Zasoby Przewodniki po produktach Architektury referencyjne Raporty analityczne Interaktywne prezentacje i demo dla produktów Pomoc w wyborze Dla programistów Dokumentacja Biblioteka programistyczna Dokumentacja i przewodniki Prezentacje aplikacji Sprawdź, co możesz zbudować Samouczki Samouczki budowania krok po kroku Architektura referencyjna Diagramy i wzorce projektowe Produkty Sztuczna inteligencja AI Gateway Obserwacja i kontrola aplikacji AI Workers AI Uruchamianie modeli uczenia maszynowego w sieci Cloudflare Przetwarzanie Observability Dzienniki, metryki i ślady Workers Budowa i wdrażanie aplikacji bezserwerowych Media Images Przekształcanie, optymalizacja obrazów Realtime Tworzenie aplikacji audio i wideo działających w czasie rzeczywistym Przechowywanie i bazy danych D1 Budowa bezserwerowych baz danych SQL R2 Przechowywanie danych bez kosztownych opłat za ruch wychodzący Plany i ceny Workers Tworzenie i wdrażanie aplikacji bezserwerowe Workers KV Bezserwerowy magazyn par klucz‑wartość dla aplikacji R2 Przechowywanie danych bez kosztownych opłat za ruch wychodzący Poznaj projekty Historie klientów Prezentacja AI w 30 sekund Krótki przewodnik wprowadzający Poznaj środowisko Workers Playground Tworzenie, testowanie i wdrażanie Discord dla programistów Dołącz do społeczności Rozpocznij tworzenie Partnerzy Sieć partnerska Rozwijaj się, wprowadzaj innowacje i spełniaj potrzeby klientów dzięki Cloudflare Portal dla partnerów Znajdowanie zasobów i rejestrowanie transakcji Rodzaje partnerstw Program PowerUP Rozwijaj swoją firmę, zapewniając klientom łączność i ochronę Partnerzy technologiczni Poznaj nasz ekosystem partnerów technologicznych i integratorów Globalni integratorzy systemów Wspieraj bezproblemową transformację cyfrową na dużą skalę Dostawcy usług Poznaj naszą sieć cenionych dostawców usług Program dla agencji samoobsługowych Zarządzaj kontami samoobsługowymi dla swoich klientów Portal równorzędny Analiza ruchu w Twojej sieci Znajdź partnera PowerUP swój biznes - połącz się z partnerami Cloudflare Powered+. Zasoby Angażowanie Prezentacje demo produktu Prezentacje produktów na żądanie Studia przypadków Jak osiągnąć sukces z Cloudflare Webinaria Wnikliwe dyskusje Warsztaty Warsztaty wirtualne Biblioteka Przewodniki, plany rozwoju i inne Raporty Wnioski z badań Cloudflare Blog Szczegółowa analiza techniczna i nowości produktowe. Centrum edukacyjne Narzędzia edukacyjne i poradniki Tworzenie Architektura referencyjna Przewodniki techniczne Przewodniki po produktach i rozwiązaniach Dokumentacja produktu Dokumentacja Dokumentacja dla programistów Poznaj theNET Informacje dla kadry kierowniczej dotyczące przedsiębiorstwa cyfrowego Cloudflare TV Innowacyjne programy i wydarzenia Cloudforce One Badania nad zagrożeniami i ich eliminowanie Radar Trendy w zakresie ruchu internetowego i cyberbezpieczeństwa Raporty analityczne Raporty z badań branżowych Wydarzenia Nadchodzące wydarzenia regionalne Zaufanie, prywatność i zgodność z przepisami Informacje i zasady dotyczące zgodności Pomoc techniczna Skontaktuj się z nami Forum społecznościowe Masz problem z dostępem do konta? Discord dla programistów Uzyskaj pomoc Firma informacje o firmie Zarząd Poznaj naszych liderów Relacje z inwestorami Informacje dla inwestorów Dla prasy Zapoznaj się z ostatnimi wiadomościami Kariera Zapoznaj się z dostępnymi stanowiskami Zaufanie, prywatność i bezpieczeństwo Prywatność Polityka, dane i ochrona Zaufanie Zasady, procesy i bezpieczeństwo Zgodność ze standardami Certyfikacja i regulacje Przejrzystość Polityka i ujawnianie informacji Organizacje reprezentujące ważny interes społeczny Wartości humanitarne Projekt Galileo Instytucje rządowe Projekt Athenian Wybory Cloudflare dla kampanii Zdrowie Projekt Fair Shot Sieć globalna Globalne lokalizacje i status Zaloguj się Skontaktuj się z działem sprzedaży Zarezerwuj termin: Cloudflare Connect San Francisco 2026 19–22 października 2026 Dołącz do tysięcy liderów z branży i skorzystaj z wyjątkowej okazji do wspólnego tworzenia innowacji oraz nawiązywania wartościowych relacji podczas Cloudflare Connect 2025. Dowiedz się więcej Wszystkie zaplanowane wydarzenia Ameryki EMEA APJC Washington, DC GovCIO AI Summit • Jan 9 Coming soon San Diego, CA AFCEA West • Feb 10 - Feb 12 Coming soon Dallas, TX Immerse Dallas • Feb 12 Learn more Bogota, CO Immerse Bogota, Colombia • Feb 19 Coming soon New York, NY NASTD East-West • Mar 2 - Mar 5 Coming soon Washington, DC Billington State & Local • Mar 9 - Mar 11 Coming soon Mexico City, MX Immerse CDMX, Mexico • Mar 12 Coming soon San Jose, CA NVIDIA GTC • Mar 16 - Mar 17 Coming soon San Francisco, CA RSAC • Mar 23 - Mar 24 Coming soon Houston, TX Immerse Houston • Apr 2 Coming soon New York, NY Immerse New York • Apr 14 Coming soon São Paulo, BR Immerse Sao Paulo, Brazil • Apr 15 Coming soon Boston, MA Immerse Boston • Apr 16 Coming soon Montreal, CA Immerse Montreal • Apr 22 Coming soon Las Vegas, NV Google Cloud Next • Apr 22 - Apr 23 Coming soon Minneapolis, MN Immerse Minneapolis • Apr 23 Coming soon Philadelphia, PA NASCIO Midyear • Apr 28 - May 1 Coming soon Buenos Aires, AR Immerse Buenos Aires, Argentina • May Coming soon Kansas City, MO NLIT • May 4 - May 6 Coming soon Anaheim, CA Immerse Anaheim/SoCal • May 6 Coming soon Tampa, FL SOF Week • May 18 - May 21 Coming soon Toronto, CA Immerse Toronto • May 20 Coming soon Chicago, IL Immerse Chicago • May 28 Coming soon National Harbor, MD Gartner Security & Risk Management Summit (USA) • Jun 1 - Jun 2 Coming soon Baltimore, MD TechNet Cyber • Jun 2 - Jun 4 Coming soon Austin, TX NASTD Midwest-South • Jun 8 - Jun 11 Coming soon Vancouver, CA Immerse Vancouver • Jun 10 Coming soon Seattle, WA Immerse Seattle • Jun 18 Coming soon Las Vegas, NV Black Hat USA • Aug 3 - Aug 6 Coming soon Denver, CO NASTD Annual • Aug 23 - Aug 26 Coming soon Las Vegas, NV Crowdstrike fal.con • Aug 31 - Sept 1 Coming soon San Diego, CA NASCIO Annual • Sept 27 - Sept 30 Coming soon Denver, CO EDUCAUSE Annual • Sept 29 - Oct 2 Coming soon Santiago, CL Immerse Santiago, Chile • Oct Coming soon San Francisco, CA Cloudflare Global Connect 2026 • Oct 19 - Oct 20 Coming soon Orlando, FL Gartner IT Symposium • Oct 19 - Oct 20 Coming soon Atlanta, GA Immerse Atlanta • Nov 12 Coming soon Las Vegas, NV AWS re:Invent • Nov 30 - Dec 4 Coming soon ROZPOCZĘCIE Bezpłatne plany Plany dla małych firm Dla firm Uzyskaj rekomendację Umów się na prezentację Skontaktuj się z działem sprzedaży ROZWIĄZANIA Globalna chmura połączeń Usługi dotyczące aplikacji SASE i bezpieczeństwo przestrzeni roboczej Usługi sieciowe Platforma programistyczna OBSŁUGA Centrum pomocy Wsparcie klienta Forum społecznościowe Discord dla programistów Masz problem z dostępem do konta? Status Cloudflare ZGODNOŚĆ Z PRZEPISAMI Zasoby dotyczące zgodności Zaufanie RODO Odpowiedzialna SI Raport dotyczący transparentności Zgłoś naruszenie INTERES PUBLICZNY Projekt Galileo Projekt Athenian Cloudflare for Campaigns Projekt Fairshot FIRMA O firmie Cloudflare Mapa sieci Nasz zespół Logo i zestaw prasowy Różnorodność, sprawiedliwość i integracja Wpływ/ESG © 2026 Cloudflare, Inc. Polityka prywatności Regulamin usługi Zgłaszanie problemów z bezpieczeństwem Preferencje dotyczące plików cookie Znak handlowy | 2026-01-13T09:29:32 |
https://www.atlassian.com/ko/jira/solutions/planning#tab-ca7d11c7-9d68-49d0-a074-2431a99f2a25 | 계획 프로젝트 관리 소프트웨어 | Atlassian Close 선택한 언어 로 이 페이지를 보고 계십니까? 모든 언어 언어를 선택합니다. 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 무료로 시작 기능 모든 기능 Jira의 Rovo Back 솔루션 팀 사용 사례 회사 규모 팀 마케팅 엔지니어링 디자인 운영팀 IT 사용 사례 시작하기 계획 캠페인 관리 애자일 프로젝트 관리 프로그램 관리 회사 규모 Enterprise Back 제품 가이드 템플릿 템플릿 모든 템플릿 소프트웨어 개발 마케팅 디자인 영업 운영팀 서비스 매니지먼트 HR 법무 IT 운영 재무 Jira Service Management 템플릿 Back 가격 자세한 내용 + 간략히 보기 - 무료로 시작 Back 무료로 시작 Atlassian이 2025년 Gartner Magic Quadrant™의 공동 작업 관리 부문에서 리더로 선정되었습니다! 자세히 알아보기 계획을 위한 Jira 모든 팀을 위한 유연한 계획 팀 및 이해 관계자가 동기화, 비동기화 및 목표에 정렬된 상태를 유지하세요. Jira Free 받기 Atlassian으로 팀 공동 작업을 강화하는 30만 명 이상의 고객과 함께하세요 계획에 Jira를 사용하는 이유는 무엇입니까? 작업 시각화 복잡한 프로젝트를 관리하기 쉬운 작은 작업으로 나누세요. 작업을 쉽게 추가하고 조정하여 다양한 작업의 시기 및 순서를 시각화하세요. 간편한 공유 작업이 진행되면서 타임라인이 실시간으로 업데이트되어 팀, 리더 및 이해 관계자와 즉시 공유할 준비가 됩니다. 원하는 스타일로 계획 처음부터 시작하든 템플릿을 사용하든 조건 및 요구 사항에 따라 자유롭게 계획을 사용자 지정할 수 있습니다. 작업이 회사 목표에 어떻게 기여하는지 확인하세요 계획 기능 비교 Advanced Basic Jira Premium의 고급 계획 기능인 계획 을 사용하면 여러 팀이 공동의 프로그램 또는 목표에 대해 공동 작업할 수 있습니다. 모든 Jira 에디션에서 사용할 수 있는 프로젝트 보기인 타임라인 을 사용하면 단일 팀 내에서 작업을 계획하고 추적할 수 있습니다. Jira로 교차 기능 작업을 추진하세요 큰 그림 추적 계획 기능 비교 Advanced Basic 계획을 통해 여러 팀 및 프로젝트에 걸쳐 작업을 추적할 수 있습니다. 계획 요약 화면에서 작업 진행률, 종속성 및 팀 작업 수용량을 총체적으로 확인할 수 있습니다. 타임라인 보기를 통해 단일 팀 의 작업을 계획하고 종속성을 추적할 수 있습니다. 종속성 미리 파악 계획 기능 비교 Advanced Basic 팀, 프로젝트 등 간 종속성을 매핑하여 잠재적인 리소싱 또는 일정 충돌을 미리 파악하세요. 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. 팀 역량을 염두에 두고 계획 Advanced 전용 팀이 범위가 지정된 작업을 완료하는 데 필요한 역량을 갖추도록 하여 목표에 맞게 진행하세요. 스프린트별로 여러 팀의 작업 수용량을 확인하세요. 서로 다른 시나리오 구상 Advanced 전용 다양한 옵션 또는 최고 및 최악의 시나리오에 따라 계획을 여러 버전으로 만들어 잠재적인 결과에 대해 더 완전한 그림을 그리세요. 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의 사용자 지정 가능한 템플릿을 살펴보세요. 개략적인 계획 프로그램 또는 이니셔티브와 같은 대규모 작업을 계획하고 추적하고 보고하세요. 교차 팀 계획 여러 스크럼 팀 간에 작업 일정을 수립 및 할당하고 작업 수용량을 관리하고 진행률을 추적합니다. 프로젝트 관리 작업 체계화부터 타임라인 시각화까지, 팀이 프로젝트 진행률을 360도로 볼 수 있도록 하세요. 더 많은 템플릿 탐색 계획 리소스 자세히 알아보려면 무료 자습서, 문서 및 가이드를 살펴보세요. 계획에 Jira를 사용하는 방법 작업 계획, 진행률 추적 및 종속성 매핑 방법에 대한 자습서입니다. 가이드 보기 Jira를 사용한 전략적 계획 전략적 계획 프레임워크 및 이것이 큰 목표를 달성하는 데 어떻게 도움이 되는지 알아보세요. 자세히 알아보기 스프린트 계획 필수 사항 팀의 워크플로에 스크럼 방법론을 적용하기 위한 필수 사항입니다. 지금 살펴보기 업무 수행 방식의 혁신 조직 및 팀이 하나가 되어 일할 수 있는 곳. 무료로 시작 회사 구직 이벤트 블로그 투자자 관계 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:32 |
https://www.atlassian.com/ko/software/jira/guides/basic-roadmaps/overview | 미리 계획: Jira의 타임라인 마스터하기 | Atlassian Close 선택한 언어 로 이 페이지를 보고 계십니까? 모든 언어 언어를 선택합니다. 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 무료로 시작 기능 모든 기능 Jira의 Rovo Back 솔루션 팀 사용 사례 회사 규모 팀 마케팅 엔지니어링 디자인 운영팀 IT 사용 사례 시작하기 계획 캠페인 관리 애자일 프로젝트 관리 프로그램 관리 회사 규모 Enterprise Back 제품 가이드 템플릿 템플릿 모든 템플릿 소프트웨어 개발 마케팅 디자인 영업 운영팀 서비스 매니지먼트 HR 법무 IT 운영 재무 Jira Service Management 템플릿 Back 가격 자세한 내용 + 간략히 보기 - 무료로 시작 Back 무료로 시작 시작하기 Jira 소개 팀을 위한 Jira Jira를 시작하기 위한 7가지 단계 프로젝트 개요 튜토리얼 리소스 보드 개요 튜토리얼 리소스 업무 항목/이슈 개요 튜토리얼 리소스 워크플로우 개요 튜토리얼 리소스 통합 개요 튜토리얼 리소스 보고서 및 대시보드 개요 튜토리얼 리소스 인사이트 개요 튜토리얼 리소스 권한 개요 튜토리얼 리소스 JQL 개요 튜토리얼 치트 시트 리소스 탐색 Overview Tutorials Resources 자동화 개요 튜토리얼 리소스 일정 개요 튜토리얼 리소스 Advanced Roadmaps 개요 튜토리얼 리소스 모바일용 Jira 개요 튜토리얼 리소스 Jira에 대한 자세한 정보 Jira 에디션 호스팅 옵션 Jira 타임라인 가이드 타임라인 보기란 무엇입니까? 타임라인 은 모든 Jira 플랜 에서 사용할 수 있는 계획 보기로, 단일 팀 및 프로젝트 내에서 작업을 계획하고 진행률을 추적하고 종속성을 매핑할 수 있습니다. 팀에서 관리하는 프로젝트 및 회사에서 관리하는 프로젝트 모두 타임라인 보기에서 지원됩니다. 에픽이란 무엇입니까? Jira에서 에픽 은 개별 작업으로 나눌 수 있는 대규모 작업을 말합니다. 이 작업은 에픽( 상위 이슈 라고도 함)의 하위 이슈가 됩니다. 이슈는 타임라인에서 색깔이 있는 막대로 표시됩니다. 타임라인에서 상위 이슈를 관리하는 방법에 대해 알아보세요. 하위 이슈란 무엇입니까? 하위 이슈 는 타임라인 보기에서 직접 만들 수 있으며 해당 이슈가 속한 에픽 내에 중첩됩니다. 가장 일반적인 하위 이슈는 스토리, 작업 및 버그이지만 새로운 이슈 유형을 만들어 팀의 다양한 작업을 나타낼 수 있습니다. 타임라인에서 직접 끌어다 놓는 방식으로 이슈를 다른 에픽으로 빠르게 옮기고 이슈 또는 에픽을 다시 정렬할 수 있습니다. 타임라인에서 하위 이슈를 예약하는 방법에 대해 자세히 알아보세요. 종속성이란 무엇입니까? 종속성 관리는 팀에 매우 중요합니다. 종속성을 시각화하고 올바르게 매핑하면 팀은 대체 경로에 적응하고 계획할 수 있습니다. Jira에서는 타임라인에서 직접 종속성을 매핑하여 에픽 및 하위 이슈 간의 관계를 쉽게 표시할 수 있습니다. 이슈 링크라고도 하는 종속성 을 사용하면 이슈를 해결해야 하는 순서를 표시할 수 있습니다. 예를 들어, 두 이슈 사이에 종속성이 있으면 팀에서 해결해야 할 잠재적 블로커가 있다는 뜻일 수 있습니다. 이 기능을 사용하려면 Jira 관리자가 이슈 링크를 사용 설정해야 합니다. Jira에서의 종속성 관리에 대해 자세히 알아보세요. 회사 구직 이벤트 블로그 투자자 관계 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:32 |
https://developer.wordpress.com/docs/developer-tools/ | Developer Tools - Build Powerful WordPress Sites Skip to content Search Search Menu Search Search At a glance WordPress and WordPress.com Tech stack Glossary Interface styles Support Get started Step 1: Create a site Step 2: Set up your local environment Step 3: Set up GitHub Step 4: Develop locally Step 5: Deploy to your production or staging site WordPress Studio Studio sites Blueprints Open in WordPress Studio button How to create custom Blueprints Preview Sites Studio Sync Studio Assistant Studio CLI Import & export SSL in Studio Frequently asked questions Changelog Roadmap Beta features MCP MCP tools reference MCP prompt examples Developer tools WP-CLI WP-CLI overview Platform-specific commands Common commands Troubleshooting REST API Getting started with the REST API REST API reference Namespaces & versions OAuth2 authentication WordPress.com Connect Using the REST API from JavaScript & the browser (CORS) Guidelines for responsible use of Automattic’s APIs Site Accelerator API Platform features Site performance Domain management User management Real time backup Storage Sitemaps Jetpack Scan Account security Guides Add HTTP headers Block patterns Manage user, file, and folder permissions Manually restore your site from a Jetpack Backup Symlinked files and folders WordPress.com oEmbed provider Troubleshooting Enabling WP_DEBUG Jetpack Activity Log At a glance WordPress and WordPress.com Tech stack Glossary Interface styles Support Get started Step 1: Create a site Step 2: Set up your local environment Step 3: Set up GitHub Step 4: Develop locally Step 5: Deploy to your production or staging site WordPress Studio Studio sites Blueprints Open in WordPress Studio button How to create custom Blueprints Preview Sites Studio Sync Studio Assistant Studio CLI Import & export SSL in Studio Frequently asked questions Changelog Roadmap Beta features MCP MCP tools reference MCP prompt examples Developer tools WP-CLI WP-CLI overview Platform-specific commands Common commands Troubleshooting REST API Getting started with the REST API REST API reference Namespaces & versions OAuth2 authentication WordPress.com Connect Using the REST API from JavaScript & the browser (CORS) Guidelines for responsible use of Automattic’s APIs Site Accelerator API Platform features Site performance Domain management User management Real time backup Storage Sitemaps Jetpack Scan Account security Guides Add HTTP headers Block patterns Manage user, file, and folder permissions Manually restore your site from a Jetpack Backup Symlinked files and folders WordPress.com oEmbed provider Troubleshooting Enabling WP_DEBUG Jetpack Activity Log Developer tools WordPress.com provides a powerful set of developer tools that make it easy to build and customize websites. These tools offer the flexibility and control needed to create robust, scalable sites. From local development with WordPress Studio to seamless GitHub deployments and access to the WordPress.com REST API, developers can streamline their workflows and deliver better user experiences. Whether you’re just getting started or have years of experience, WordPress.com’s developer tools are built to help you bring your ideas to life. You can learn more about each tool using the links below. WordPress Studio WordPress Studio is a free desktop app that simplifies local WordPress development. It lets you quickly build and manage local sites, sync with live production or staging sites, and share your work using site previews hosted on WordPress.com. Learn more Staging sites Staging sites allow you to clone your entire WordPress.com site. This is especially useful for troubleshooting issues, previewing major updates, or collaborating with others in a controlled environment. Learn more GitHub Deployments GitHub Deployments let you connect a GitHub repository to your WordPress.com site for reliable, automated code deployment. Changes pushed to the repo can be deployed to your site either automatically or on demand. Learn more Bulk plugin management Use our intuitive Plugin Management tool to efficiently manage and update the plugins across all of your WordPress.com sites, all in one centralized dashboard. Learn more Scheduled plugin updates Scheduled Plugin Updates let you choose exactly when your site checks for and installs plugin updates. This gives you full control over timing and helps minimize potential disruptions. Learn more Block patterns Create beautiful posts, pages, and templates using WordPress.com patterns. Designed to match your theme’s global styles, these patterns work out of the box—no plugins or coding needed. Think of them as a component library for the block editor. Learn more WP-CLI WP-CLI is a command-line interface for WordPress that you can access when connected via SSH. This guide covers the most commonly used commands and their associated sub-commands. Learn more SFTP Secure File Transfer Protocol (SFTP) is a secure way to upload and download files between your computer and your WordPress.com site. It helps you manage your site’s files safely over an encrypted connection. Learn more SSH SSH (Secure Shell) lets you access your site’s backend through a terminal app, allowing you to manage files and settings directly. It also gives you access to WP-CLI, a command-line tool for making changes and troubleshooting your site efficiently. Learn more Database access You can use phpMyAdmin to access your website’s database and run a wide range of operations. This guide will show you how to administer your site’s MySQL database. Learn more Web server settings In your website’s web server settings, you can configure options related to the PHP version and nonexistent assets on your site. This guide will explain each setting you can use to fine-tune how the web server runs your website. Learn more REST API Explore the WordPress.com REST API to learn how you can interact with your site programmatically. You’ll find detailed documentation and a complete list of available endpoints to help you build powerful integrations and workflows. Learn more Last updated: October 01, 2025 Ready to get started with WordPress.com? Get started Documentation is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License An Automattic Creation | 2026-01-13T09:29:32 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3AtoggleSwitch | 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/sharing-media#collapse6 | 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 |
https://aws.amazon.com/resources/analyst-reports/22-global-gartner-mq-cips/?trk=f70460f2-4ce1-473b-bf28-3e279852fb66&sc_channel=el | AWS Analyst Reports Skip to main content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account AWS › Getting started › Resources Featured | 2025 Gartner Report Magic Quadrant for Data Science and Machine Learning Platforms AWS in Analyst Research Read what Gartner, IDC, and other top analyst firms are saying about AWS. All privileges have been secured to include content on this site for all audiences. Get started with AWS Reports IDC MarketScape Cloud AI Developer Services Vendor Rating 2024 ISG SAP HANA Infrastructure Services Is Your Cloud Resilient Enough? IDC MarketScape: Worldwide Public Cloud Infrastructure as a Service 2025 Vendor Assessment “ AWS is a Leader in the public cloud IaaS market through service breadth and continuous innovation. Their extensive global infrastructure, combined with custom silicon initiatives like Graviton and significant AI investments, positions them uniquely to serve enterprise needs. Their proven track record in scalability, established developer community, and aggressive investments in AI infrastructure, make them the go-to choice for organizations requiring sophisticated cloud capabilities. ” states IDC analyst and report author Dave McCarthy. Read the IDC report 2024 Gartner Report Magic Quadrant for Cloud AI Developer Services In the 2024 Gartner Magic Quadrant, AWS is recognized as a Leader and has been placed highest on Ability to Execute Read the Gartner report Gartner | 2024 Vendor Rating: Amazon Gartner Recognizes Amazon for Receiving an overall Vendor Rating of Positive Read the Gartner report 2024 ISG Report Provider Lens Multi Public Cloud Services Quadrant - SAP HANA Infrastructure Services “AWS offers the most comprehensive services for migrating and hosting SAP workloads on public cloud infrastructure,” Shashank Rajmane, Principal Analyst said in the report. “It provides cost efficiencies and high performance while adhering to all security and compliance regulations.” Read the ISG report Frost and Sullivan | Is Your Cloud Resilient Enough? What to Look for in Cloud Infrastructure Design Did you know AWS delivered an industry leading uptime of 99.54% across APAC from January 2022 to June 2024, through 13 regions and 41 Availability zones? Read the Frost and Sullivan report Analyst Reports Loading Loading Loading Loading Loading Additional Resources AWS content Whitepapers | Explore documents written by independent analysts, the AWS team, and the AWS community on product introductions, framework overviews, and more. AWS in the News | Catch up on the latest AWS news announced by Forbes, TechCrunch, ZDNet, and other media outlets. What's New | Stay up to date on the latest AWS product and service announcements. AWS Podcast | Listen and learn about AWS with hosts Simon Elisha & Jeff Barr. Each episode includes AWS news, tech tips, and interviews with startups, AWS partners, and AWS employees. Peer reviews | With the rapid growth of review platforms for software vendors among individual developers, start-ups, and enterprises around the world, customers are asking for AWS ratings backed by other users. Peer review platforms like G2 Crowd and Gartner Peer Insights allow veteran and new AWS users to join a growing, dynamic community to answer questions, share ideas, and learn about new services and best practices. G2 Crowd | Compare AWS services and read reviews by customers based on satisfaction ratings and user experiences. Gartner Peer Insights | Read what enterprise customers and IT professionals think about AWS on this review platform hosted by Gartner Research. Create an AWS account Learn What Is AWS? What Is Cloud Computing? What Is Agentic AI? Cloud Computing Concepts Hub AWS Cloud Security What's New Blogs Press Releases Resources Getting Started Training AWS Trust Center AWS Solutions Library Architecture Center Product and Technical FAQs Analyst Reports AWS Partners Developers Builder Center SDKs & Tools .NET on AWS Python on AWS Java on AWS PHP on AWS JavaScript on AWS Help Contact Us File a Support Ticket AWS re:Post Knowledge Center AWS Support Overview Get Expert Help AWS Accessibility Legal English Back to top Amazon is an Equal Opportunity Employer: Minority / Women / Disability / Veteran / Gender Identity / Sexual Orientation / Age. x facebook linkedin instagram twitch youtube podcasts email Privacy Site terms Cookie Preferences © 2026, Amazon Web Services, Inc. or its affiliates. All rights reserved. | 2026-01-13T09:29:33 |
https://docs.aws.amazon.com/ko_kr/cost-management/latest/userguide/ce-exploring-data.html | Cost Explorer를 사용하여 데이터 탐색 - AWS 비용 관리 Cost Explorer를 사용하여 데이터 탐색 - AWS 비용 관리 설명서 AWS Billing and Cost Management 사용 설명서 Cost Explorer 탐색 내 Cost Explorer 비용 Cost Explorer 추세 일별 일반 요금 월별 일반 요금 순 일반 요금 최근 Cost Explorer 보고서 분할 상환 요금 분할 상환 요금 기계 번역으로 제공되는 번역입니다. 제공된 번역과 원본 영어의 내용이 상충하는 경우에는 영어 버전이 우선합니다. Cost Explorer를 사용하여 데이터 탐색 Cost Explorer 대시보드에는 Cost Explorer의 이번 달 현재까지 예상 비용, 월 예상 비용, 일별 비용 그래프, 상위 5개의 비용 추세, 최근에 본 보고서 목록이 표시됩니다. 모든 비용은 전날까지의 사용량을 반영합니다. 예를 들어 오늘이 12월 2일인 경우 데이터에는 12월 1일까지의 사용량이 포함됩니다. 참고 현재 결제 기간의 데이터는 결제 애플리케이션의 업스트림 데이터에 따라 다르며, 일부 데이터는 24시간 이후에 업데이트될 수 있습니다. 내 Cost Explorer 비용 Cost Explorer 추세 일별 일반 요금 월별 일반 요금 순 일반 요금 최근 Cost Explorer 보고서 분할 상환 요금 분할 상환 요금 Cost Explorer 탐색 왼쪽 창에 있는 아이콘을 사용하여 다음을 수행할 수 있습니다. 기본 Cost Explorer 대시보드로 이동 기본 Cost Explorer 보고서 목록 보기 저장된 보고서 목록 보기 예약 관련 정보 보기 예약 추천 보기 내 Cost Explorer 비용 Cost Explorer 페이지 상단에는 이번 달 현재까지 비용(Month-to-date costs) 및 이번 달 말까지 예상 비용(Forecasted month end costs) 이 있습니다. Month-to-date costs(이번 달 현재까지 비용) 는 이번 달의 현재까지 발생한 것으로 예상되는 비용을 표시하고, 지난 달과 비교합니다. 이번 달 말까지 예상 비용(Forecasted month end costs) 은 Cost Explorer에서 이번 달 말까지 예상되는 비용을 표시하고 예상 비용을 이전 달의 실제 비용과 비교합니다. Month-to-date costs(이번 달 현재까지 비용) 및 Forecasted month end costs(이번 달 말까지 예상 비용) 에는 환급금이 포함되지 않습니다. Cost Explorer 비용은 미국 달러로만 표시됩니다. Cost Explorer 추세 이번 달 추세(this month trends) 섹션에서 Cost Explorer가 상위 비용의 추세를 표시합니다. 예를 들어 특정 서비스 관련 비용이 증가했거나 특정 유형의 RI에서 비용이 증가했을 수 있습니다. 모든 비용 추세를 보려면 추세 섹션의 오른쪽 상단에 있는 View all trend(모든 추세 보기) 를 선택합니다. 추세를 더 심층적으로 이해하려면 이 항목을 선택합니다. 해당 추세 계산에 들어간 비용을 보여 주는 Cost Explorer 차트로 이동됩니다. 일별 일반 요금 Cost Explorer 대시보드 중앙에는 현재 일반 일별 요금 그래프가 표시됩니다. 오른쪽 상단에 있는 Explore costs(요금 탐색) 를 선택하여 그래프 생성에 사용된 필터 및 파라미터에 액세스할 수 있습니다. 이를 통해 Cost Explorer 보고서 페이지로 이동하고, 기본 Cost Explorer 보고서에 액세스하여 차트 생성에 사용된 파라미터를 수정할 수 있습니다. Cost Explorer 보고서는 데이터를 CSV 파일로 저장하고 특정 파라미터를 보고서로 저장하는 등의 추가 기능을 제공합니다. 자세한 정보는 Cost Explorer 보고서를 사용하여 비용 이해 단원을 참조하세요. 일별 일반 요금에는 환급금이 포함되지 않습니다. 월별 일반 요금 월별 세부 수준 월별 세부 수준에서 일반 요금을 볼 수 있으며 월별 청구서에 적용된 할인을 볼 수 있습니다. 비용을 예측할 때는 기본적으로 할인이 포함됩니다. 일반 요금을 보려면 Cost Explorer 페이지를 열고 탐색 창에서 Cost Explorer 를 선택합니다. 할인은 차트에 RI Volume Discount(RI 대량 구매 할인) 으로 나타납니다. 할인 금액은 Billing and Cost Management 콘솔에 표시된 할인 금액과 일치합니다. Billing and Cost Management 콘솔에서 세부 정보를 보려면 에서 과금 정보 및 비용 관리 콘솔을 엽니다 https://console.aws.amazon.com/costmanagement/ 탐색 창에서 청구서(Bills) 를 선택합니다. 할인을 표시하려면 크레딧, 총 할인 및 세금 계산서(Credits, Total Discounts and Tax Invoices) 에서 총 할인(Total Discounts) 옆에 있는 화살표를 선택합니다. 월별 총 요금 RI Volume Discount(RI 대량 구매 할인) 을 제외하여 총 월별 요금을 볼 수 있습니다. 월별 보기에서 RI 대량 구매 할인을 제외하려면 다음과 같이 하세요. 에서 과금 정보 및 비용 관리 콘솔을 엽니다 https://console.aws.amazon.com/costmanagement/ 왼쪽 창에서 Cost Explorer 를 선택합니다. Cost & Usage(비용 및 사용량) 를 선택합니다. Filters(필터) 창에서 Charge Type(요금 유형) 을 선택합니다. RI Volume Discount(RI 대량 구매 할인) 를 선택합니다. 드롭다운을 열려면 Include only(다음만 포함) 를 선택하고 Exclude only(다음만 제외) 를 선택합니다. Apply filters(필터 적용) 를 선택합니다. 순 일반 요금 이 항목을 사용하면 적용 가능한 모든 할인을 계산한 후 순 비용을 볼 수 있습니다. 모범 사례로 환급금 및 크레딧과 같은 수동 조정을 여전히 제외해야 합니다. RI Volume Discounts(RI 대량 구매 할인) 는 할인 후 금액이기 때문에 더 이상 표시되지 않습니다. 최근 Cost Explorer 보고서 보고서에 액세스하면 Cost Explorer 대시보드 하단에 최근 액세스한 보고서의 목록과 보고서로 다시 연결되는 링크가 있습니다. 이를 통해 보고서를 전환하거나 가장 유용한 보고서를 기억할 수 있습니다. Cost Explorer 보고서에 대한 자세한 내용은 Cost Explorer 보고서를 사용하여 비용 이해 단원을 참조하세요. 분할 상환 요금 이를 통해 Amazon EC2 예약형 인스턴스 또는 절감형 플랜과 같은 AWS약정 비용을 선택 기간 전체에 분산하여 확인할 수 있습니다. AWS은 일반 선결제 요금과 기본 예약 요금을 합산하여 분할 상환 비용을 추정하고, 선결제 또는 기본 요금이 적용되는 기간의 실질 요금을 계산합니다. Cost Explorer의 일별 보기에는 월초 또는 구매 날짜에 예약 요금의 미사용 부분이 표시됩니다. 분할 상환 요금 이렇게 하면 실제 비용이 시간 경과에 따라 어떻게 적용되는지를 보여주는 추가 로직을 통해 Amazon EC2 예약형 인스턴스 또는 절감형 플랜과 같은 AWS약정 비용의 할인 후 비용을 확인할 수 있습니다. 절감형 플랜과 예약형 인스턴스에는 일반적으로 월 선결제 요금 또는 월 기본 요금이 적용되므로 순 분할 상환 비용 데이터 세트는 선결제 금액이나 기본 요금이 적용되는 기간 동안 할인 후 수수료가 어떻게 분할되는지 보여줌으로써 실제 비용을 보여줍니다. javascript가 브라우저에서 비활성화되거나 사용이 불가합니다. AWS 설명서를 사용하려면 Javascript가 활성화되어야 합니다. 지침을 보려면 브라우저의 도움말 페이지를 참조하십시오. 문서 규칙 Cost Explorer 시작하기 Cost Explorer 차트 사용 이 페이지의 내용이 도움이 되었습니까? - 예 칭찬해 주셔서 감사합니다! 잠깐 시간을 내어 좋았던 부분을 알려 주시면 더 열심히 만들어 보겠습니다. 이 페이지의 내용이 도움이 되었습니까? - 아니요 이 페이지에 작업이 필요하다는 점을 알려 주셔서 감사합니다. 실망시켜 드려 죄송합니다. 잠깐 시간을 내어 설명서를 향상시킬 수 있는 방법에 대해 말씀해 주십시오. | 2026-01-13T09:29:33 |
https://pix.webm.ink/site/kb/sharing-media#collapse2 | 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 |
https://www.ecns.cn/hd/2026-01-13/detail-iheywhna5920684.shtml#2 | South Korea's ex-President Yoon Suk Yeol faces sentencing in insurrection trial --> 中文 Home News Ecns Wire Business Travel Photo Video Voices RIGHT BG LINE Text: A A A Print Photo South Korea's ex-President Yoon Suk Yeol faces sentencing in insurrection trial ( 1 /2) 2026-01-13 11:29:09 Ecns.cn Editor :Gong Weiwei A blue bus carrying South Korea's former President Yoon Suk Yeol arrives at the Seoul Central District Court on Jan. 13, 2026. (Photo provided to China News Service) Tuesday's hearing will conclude the legal proceedings against former President Yoon Suk Yeol, who faces criminal charges for imposing martial law late in the evening of Dec. 3, 2024. He stands accused of abusing his power and leading an insurrection. A blue bus carrying South Korea's former President Yoon Suk Yeol arrives at the Seoul Central District Court on Jan. 13, 2026. (Photo provided to China News Service) Previous Tuesday's hearing will conclude the legal proceedings against former President Yoon Suk Yeol, who faces criminal charges for imposing martial law late in the evening of Dec. 3, 2024. He stands accused of abusing his power and leading an insurrection.--> Next (1) (2) LINE More Photo 'Weepy horse' toy goes viral after sewing error New giant panda pair makes public debut in Malaysia Exploring world's largest island Greenland Venezuelan people call on U.S. to release Nicolás Maduro and his wife Heavey snow hits Paris 'Southern Snow Town' draws tourists to Guizhou Province ${visuals_2} ${visuals_3} More Video Comicomment: Wings clipped, Latin America left to suffer A surreal start of 2026: When one president seizes another, next target — Greenland Comicomment: No country has the right to act as the world's police What's it like doing business in China? Check what foreign friends say More than a business hub: check how global merchants thrive in Yiwu Comicomment: Save or Slave? Hegemony at play ${new_video_hd2} ${new_video_hd3} LINE Media partners: People's Daily | Xinhua | CGTN | China Daily Back to top About Us | Jobs | Contact Us | Privacy Policy Copyright ©1999-2026 Chinanews.com. All rights reserved. Reproduction in whole or in part without permission is prohibited. [ 网上传播视听节目许可证（0106168) ] [ 京ICP证040655号 ] [ 京公网安备 11010202009201号 ] [ 京ICP备05004340号-1 ] --> --> | 2026-01-13T09:29: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://www.tumblr.com/support?language=fr_FR | Centre d'aide | Tumblr Connexion Inscription © Tumblr, Inc. Aide À propos de Tumblr Applis Développeurs Thèmes Emplois Mentions légales CGU Copyright Confidentialité 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://pix.webm.ink/site/kb/sharing-media#collapse12 | 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 |
https://wiki.documentfoundation.org/Special:MyLanguage/Accessibility | Accessibility - 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 Accessibility 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 Start Multilingual Wiki Upload Special pages Organization TDF Other languages: Deutsch English Nederlands Taqbaylit Türkçe español français italiano português do Brasil shqip slovenščina čeština українська العربية سرائیکی فارسی नेपाली हिन्दी 中文（臺灣） 日本語 This page is the gateway to the LibreOffice Accessibility wiki: LIBREOFFICE RESOURCES for ACCESSIBILITY Accessibility Resources for Users Tools, Mailing Lists, and more WRITING ACCESSIBLE DOCUMENTS How to Create Accessible LibreOffice PDFs and documents Special topics Text Attributes for Accessibility Accessibility for Developers Accessibility Unit Testing with CPPUnit Chapter on Accessibility in the LibreOffice DevGuide Retrieved from " https://wiki.documentfoundation.org/index.php?title=Accessibility&oldid=675352 " Categories : Accessibility Linked from Help This page was last edited 19:54, 26 June 2023 by Stéphane Guillou . Based on work by Ilmari Lauhakangas and Adolfo Jayme Barrientos 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://issues.jenkins.io/secure/ConvertSubTask.jspa?id={0}&returnUrl=/secure/issues#main | Convert Sub-task to Issue: - 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 Errors Invalid issue id. Return to Dashboard 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.chinadaily.com.cn/a/202512/15/WS693fff6ea310d6866eb2ebd5.html | Mainland warns Taiwan leader against provoking conflict - 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 China News Society Innovation HK/Macao Cross-Strait Cover Story Photo Environment Health Military Video Home / China / Military Home China Military Mainland warns Taiwan leader against provoking conflict By Jiang Chenglong | chinadaily.com.cn | Updated: 2025-12-15 20:30 Share Share - WeChat --> CLOSE A mainland defense spokesperson on Monday accused the Lai Ching-te authorities in Taiwan of pursuing "independence" provocations, calling them the "most dangerous poison" harming and destroying the island. Defense Ministry spokesperson Jiang Bin made the remarks in response to recent comments by Lai, the Taiwan leader, who claimed that the Chinese mainland aims to take Taiwan by force by 2027. Lai also said in an interview that Taiwan must prepare for the worst while striving for the best. Jiang said Lai has repeatedly exaggerated the so-called "military threat" from the Chinese mainland and deliberately escalated tensions across the Taiwan Strait. Lai's talk of "preparations," Jiang said, is aimed at stirring war anxiety and creating excuses for pursuing "Taiwan independence" and provoking conflict. "The Lai authorities' provocations for 'independence' are the most dangerous poison harming and destroying Taiwan," Jiang said, adding that national reunification is the best choice to ensure lasting peace and stability for Taiwan. He urged Taiwan compatriots to clearly recognize the extreme danger and harm of the Lai authorities' push for war preparations in pursuit of "independence," firmly oppose "Taiwan independence" separatist activities, and jointly safeguard peace and stability across the Taiwan Strait, as well as their own security and well-being. --> --> Related Stories Beijing says Taiwan question brooks no foreign interference Beijing: Japanese fighter jets harassed pre-notified exercise zone Japanese scholar condemns Japan's risky defense spending Taiwan's Lai Ching-te slammed for selling war anxiety US urged to recalibrate its strategic perception of China Photo Chongqing hosts Silver Age fashion model competition Hengshan Mountain glistens with iconic winter rime scenery Workers build giant snowman in Heilongjiang Geminid meteor shower seen across China Beijing mobilizes for winter's first major snowfall Metasequoia avenue in Changsha showcases nature's splendor --> Latest Chongqing hosts Silver Age fashion model competition Hengshan Mountain glistens with iconic winter rime scenery Ningbo hospital staff disciplined following pediatric surgery death Mainland warns Taiwan leader against provoking conflict Former senior official of Shenzhen under investigation Beijing says Taiwan question brooks no foreign interference --> State Council News A look at China's economy in November, 2025 Xi stresses strategic importance of work to raise minors' moral standards Xi's article on expanding domestic demand to be published Exclusive The Olympic spirit: a guiding light in everyday life When the Olympics meets tai chi AI robots shine at Tianjin's smart zero-carbon terminal Newsmaker Victims of massacre remembered Renowned actress He Qing passes away at 61 Ten photos you don't wanna miss Ten photos from across China: Dec 5 - 11 Special Coverage Live: Hong Kong residential area fire 4th Plenary Session of the 20th CPC Central Committee 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/202511/13/WS69152d9aa310d6866eb29398.html | Charming Beijing TV Series promotion event in quotes (II) - 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 (II) chinadaily.com.cn | Updated: 2025-11-13 09:00 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 Shopping gala focuses on quality growth, AI dividends Building China into a strong sports country What? Clothes made from fish skin? Calls and conservation China's micro-dramas a screen saver for film 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.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://wordpress.com/ja/support/github-deployments/ | WordPress.com で GitHub デプロイメントを使用する – 日本語サポート 商品 機能 リソース プランと料金 ログイン 始めてみよう メニュー WordPress ホスティング WordPress パートナープログラム アフィリエイトに参加 ドメイン名 AI サイトビルダー サイトビルダー ブログを作成 ニュースレター ビジネス用メールアドレス サイトデザインサービス コマース WordPress Studio エンタープライズ WordPress 概要 WordPress テーマ WordPress プラグイン WordPress パターン Google Apps サポートセンター WordPress ニュース 会社名ジェネレータ ロゴメーカー 新しい投稿を見る 人気のタグ ブログ検索 ナビゲーションメニューを閉じる 始めてみよう 登録 ログイン 紹介 プランと料金 商品 WordPress ホスティング WordPress パートナープログラム アフィリエイトに参加 ドメイン名 AI サイトビルダー サイトビルダー ブログを作成 ニュースレター ビジネス用メールアドレス サイトデザインサービス コマース WordPress Studio エンタープライズ WordPress 機能 概要 WordPress テーマ WordPress プラグイン WordPress パターン Google Apps リソース サポートセンター WordPress ニュース 会社名ジェネレータ ロゴメーカー 新しい投稿を見る 人気のタグ ブログ検索 Jetpack アプリ さらに詳しく サポートセンター ガイド コース フォーラム お問い合わせ 検索 サポートセンター / ガイド サポートセンター ガイド コース フォーラム お問い合わせ ガイド / ツール / WordPress.com で GitHub デプロイメントを使用する WordPress.com で GitHub デプロイメントを使用する GitHub デプロイメントは GitHub リポジトリを WordPress.com サイトと直接統合し、プラグイン、テーマ、完成サイトの変更をデプロイするバージョン管理された自動化ワークフローを提供します。このガイドでは、設定プロセスと接続済みリポジトリの管理方法について説明します。 この機能は、WordPress.com ビジネスプランおよびコマースプラン をご利用のサイトで使用できます。ビジネスプランをご利用の場合は、必ず 有効化 してください。無料サイトの場合、およびパーソナルプランまたはプレミアムプランのサイトの場合、 プランをアップグレード してこの機能を利用してください。 このガイド内 動画チュートリアル リポジトリを接続する デプロイメント設定を管理する 高度なデプロイメント コードをデプロイする 既存の接続を管理する デプロイメントの実行ログ リポジトリから接続解除する WordPress.com の接続を GitHub から解除する 質問がある場合 AI アシスタントに尋ねる トップへ戻る 動画チュートリアル この動画の言語は英語です。 YouTube には、自分の言語で視聴できる自動翻訳機能があります。 自動翻訳字幕を表示するには： 動画を再生します。 動画右下の ⚙️ 設定 アイコンをクリックします。 字幕/CC を選択します。 自動翻訳 を選択します。 希望する言語を選びます。 自動吹き替え（実験機能）で視聴するには： ⚙️ 設定 アイコンをクリックします。 音声トラック を選択します。 視聴したい言語を選びます。 ℹ️ 翻訳と吹き替えは Google により自動生成されるため、正確でない場合があります。また、自動吹き替えは現在テスト中で、すべての言語で利用できるわけではありません。注: 字幕の文章は Google 翻訳で生成されるため、完全とはいえませんが、内容の把握に役立ちます。 リポジトリを接続する GitHub リポジトリを WordPress.com サイトにデプロイする前に、次の手順に従ってこの2つの間の接続を設定する必要があります。 「サイト」ページ ( https://wordpress.com/sites ) にアクセスします。 サイトの名前をクリックして、サイトの概要を表示します。 「デプロイメント」 タブをクリックします。 「ディレクトリを接続」 ボタンをクリックします。ここで、リポジトリが一覧表示されている場合は、すでに GitHub アカウントを接続しています。手順11に進みます。 「WordPress.com アプリをインストール」 ボタンをクリックします。 新しいウィンドウが開き、まだ GitHub アカウントにログインしていない場合はログインを促すメッセージが表示されます。次に、こちらの画面が表示されます。 「Authorize WordPress.com for Developers」 ボタンをクリックします。 リポジトリがある GitHub 組織またはアカウントを選択します。 接続するリポジトリを選択します。 All repositories： このオプションを選択すると、WordPress.com は選択した GitHub アカウントが所有する現在 および 将来のすべてのリポジトリにアクセスできます。これには、読み取り専用の公開リポジトリが含まれます。 Only select repositories： このオプションを選択すると、選択した GitHub アカウントで WordPress.com がアクセスできるリポジトリを選択できます。 オプションを選択したら、 「Install」 ボタンをクリックします。 新しいウィンドウが閉じ、WordPress.com に戻ります。選択したリポジトリが、そのリポジトリに関連付けられた GitHub アカウントとともに一覧表示されます。 接続するリポジトリの横にある 「選択」 をクリックします。 この時点で、 「WordPress.com for Developers」 は 「Authorized GitHub Apps」 と 「Installed GitHub Apps」 に表示されます。 デプロイメント設定を管理する リポジトリを選択したら、デプロイメント設定を調整する必要があります。 デプロイメントブランチ: デフォルトはリポジトリのデフォルトブランチ (通常は main )ですが、使用するブランチに変更できます。 移動先ディレクトリ: ファイルをデプロイするサーバーフォルダー。プラグインの場合、 /wp-content/plugins/my-plugin-name 。テーマの場合、 /wp-content/themes/my-theme-name 。部分的なサイトのデプロイ (複数のプラグインやテーマなど) には、 /wp-content オプションを使用できます。リポジトリのコンテンツは、指定されたディレクトリ内の WordPress サイトの既存コンテンツとマージされます。 自動デプロイメント: WordPress.com にデプロイする方法は2つあります。 自動: コードがコミットされると、WordPress.com サイトにデプロイされます。ステージングサイトには自動デプロイメントをお勧めします。 手動: デプロイメントをリクエスト すると、コードがデプロイされます。本番サイトでは手動デプロイメントをお勧めします。 デプロイメントモード: デプロイメントには2つのタイプがあります。 シンプル: このモードは、 すべて のファイルをリポジトリのブランチからサイトにコピーし、後処理なしでデプロイします。 高度: このモードでは、ワークフロースクリプトを使用して、Composer 依存関係のインストール、デプロイ前のコードテスト実施、ファイルデプロイメントの制御などのカスタムビルドステップが可能です。Composer または Node ソフトウェアを必要とするリポジトリに最適です。 詳細については、以下の「高度なデプロイメント」を参照してください 。 すべての設定が完了したら、 「接続」 ボタンをクリックします。リポジトリが追加されます。 最初のデプロイメントは、 自動または手動のいずれか でトリガーする必要があります。その後は、 「ディレクトリを接続」 ボタンをクリックすると、いつでも別のリポジトリを接続できます。 高度なデプロイメント 高度なデプロイメントでは、デプロイメントの前にリポジトリ内のファイルを処理するワークフロースクリプトを指定できます。これにより、コードがチームのコーディング基準を満たしていることを確認したり、単体テストを実行したり、デプロイメントからファイルを除外したり、依存関係をインストールしたりでき、さまざまな可能性が広がります。開始するには、 ワークフローのレシピ をご覧ください。 高度なデプロイメントを設定するには: デプロイメントを設定できるフォームが表示されます。 リポジトリの名前をクリックして、接続を管理します。 右側の 「デプロイメントモードを選択」 で 「高度」 を選択します。 リポジトリにすでにワークフローファイルがある場合は、ここで選択できます。システムはファイルにエラーがないかチェックします。エラーが見つからない場合は、手順7に進みます。 「新しいワークフローを作成」 オプションを選択して、事前設定されたワークフローファイルを追加することもできます。このオプションを選択すると、リポジトリに wpcom.yml ワークフローファイルがすでに存在する場合は上書きされます。 「ワークフローのインストールを依頼」 ボタンをクリックして、ワークフローファイルをリポジトリにコミットします。 ワークフローが追加されて検証されたら、 「更新」 をクリックします。リポジトリは高度なデプロイメントを使用するようになりました。 コードをデプロイする GitHub リポジトリをサイトに接続したら、次は実際にコードをデプロイします。利用できるデプロイメント方法には、 自動 と 手動 の2つがあります。 リポジトリでのあらゆるコード変更は GitHub からライブサイトに自動的にデプロイされるため、ライブ本番サイトでは 自動 デプロイメントは推奨されません。代わりに、 ステージングサイト への自動デプロイメントを設定し、準備ができたら本番環境に同期することを検討してください。 手動 デプロイメントでは、コードの変更をいつ公開するかを詳細に制御できます。デプロイメントごとに手動でトリガーする必要があるためです。ステージングサイトを使用しない場合は、手動デプロイメントをお勧めします。 デプロイメントを手動でトリガーするには: 「サイト」ページ ( https://wordpress.com/sites ) にアクセスします。 サイトの名前をクリックして、サイトの概要を表示します。 「デプロイメント」 タブをクリックします。 デプロイするリポジトリの省略記号メニュー (⋮) をクリックします。 「手動デプロイメントをトリガー」 を選択します。「デプロイメントの実行が作成されました」というバナー通知が表示され、デプロイメントのステータスが「待機中」に変わります。 デプロイメントが完了するまで待ちます (ステータスは「デプロイ済み」に変わります）。 省略記号メニュー (⋮) をもう一度クリックし、 「デプロイメントの実行を表示」 を選択します。 デプロイメントの実行ログ に、作成者とデプロイ済みのコミットが表示されます。デプロイメントの実行エントリーをクリックすると、詳細情報を表示できます。 既存の接続を管理する 既存の GitHub リポジトリ接続を管理するには: 「サイト」ページ ( https://wordpress.com/sites ) にアクセスします。 サイトの名前をクリックして、サイトの概要を表示します。 「デプロイメント」 タブをクリックします。 接続リストが表示されます。 GitHub リポジトリとサイトの間に少なくとも1つの接続がある場合は、接続リストが表示されます。リストには、リポジトリ名とブランチ、サイトに最後にデプロイされたコミット、そのタイミング、コードが配置された場所、デプロイメントの実行にかかった時間、そのステータスなど、各接続に関連する情報が含まれています。 省略記号メニュー (⋮) をクリックすると、追加のアクションを使用できます。 手動デプロイメントをトリガー: 設定済みブランチの最新のコミットで デプロイメントの実行を開始 します。 デプロイメントの実行を表示: 接続済みリポジトリの デプロイメントの実行ログ 表示を開きます。 接続の設定: リポジトリの 接続管理表示 を開きます。 ディレクトリから切断: リポジトリとサイト間の接続を削除します。 デプロイメントの実行ログ デプロイメントの実行ログは、自動でトリガーされたか手動でトリガーされたかに関係なく、各デプロイメントの詳細なステップバイステップのレコードを提供します。これらのログは、変更の追跡、デプロイメントのステータスの監視、発生した問題のトラブルシューティングに役立ちます。過去10回の実行で30日以内にログにアクセスできるため、各デプロイメント中に何が起きたかを簡単に確認し、すべてがスムーズに実行されていることを確認できます。 デプロイメントのログをチェックするには: 「サイト」ページ ( https://wordpress.com/sites ) にアクセスします。 サイトの名前をクリックして、サイトの概要を表示します。 「デプロイメント」 タブをクリックします。 ログを表示するリポジトリの横にある省略記号メニュー (⋮) をクリックします。 「デプロイメントの実行を表示」 を選択します。 「デプロイメントの実行」 リストビューには、サイトにデプロイされたコミット、デプロイメントのステータス、日付、期間が表示されます。 実行の任意の場所をクリックして展開し、デプロイメントに関する詳細情報を表示します。 ログには、GitHub からコードを取得して対象ディレクトリに配置するまでに実行された、すべてのコマンドのレコードが表示されます。 「さらに表示」 をクリックすると、ログ行を展開して詳細を表示できます。 リポジトリから接続解除する サイトから GitHub リポジトリの接続を解除すると、リポジトリに対する今後の変更はサイトに影響を与えなくなります。デフォルトでは、デプロイされたファイルはサイトに残りますが、接続解除プロセス中にそれらを削除するオプションがあります。 リポジトリを削除するには: 「サイト」ページ ( https://wordpress.com/sites ) にアクセスします。 サイトの名前をクリックして、サイトの概要を表示します。 「デプロイメント」 タブをクリックします。 リポジトリの省略記号メニュー (⋮) をクリックします。 「ディレクトリから切断」 を選択します。 ダイアログウィンドウが表示されます。切り替えをクリックして、サイトから関連ファイルを削除します。 「ディレクトリから切断」 をクリックしてダイアログを閉じ、リポジトリの接続を解除します。 なお、 「WordPress.com for Developers」 は 「Installed GitHub Apps」 と 「Authorized GitHub Apps」 にまだ表示されています。これは、WordPress.com がまだリポジトリにアクセスできるにもかかわらず、接続が削除されたためです。 WordPress.com の接続を GitHub から解除する また、WordPress.com の GitHub アカウントへのアクセスを取り消すこともできます。GitHub の 「Applications settings」 にアクセスすれば、いつでも取り消すことができます。 承認済みアプリの GitHub アカウントへのアクセスを取り消すには: 「Authorized GitHub Apps」 に移動します。 「WordPress.com for Developers」 の横にある 「Revoke」 をクリックします。 「I understand, revoke access」 ボタンをクリックします。 承認済みアプリのアクセスを取り消しても、選択したアカウントに 開発者用 WordPress.com アプリがインストールされたままであるため、コードをデプロイできます。 WordPress.com インストールへのアクセスを取り消し、WordPress.com サイトにコードをデプロイする機能を無効にするには: 「Installed GitHub Apps」 に移動します。 「WordPress.com for Developers」 の横にある 「Configure」 をクリックします。 「Danger zone」 領域で 「Uninstall」 をクリックし、プロンプトが表示されたら 「OK」 をクリックします。 WordPress.com を承認済みアプリのリストから削除しても、リポジトリが削除されたり機能しなくなったりするわけでは ありません 。WordPress.com のアクセスを取り消した後も、リポジトリは GitHub に残りますが、WordPress.com はコードをデプロイできなくなります。 関連するガイド SSH に接続する 防御モードを有効化する サイトのデータベースにアクセスする このガイド内 動画チュートリアル リポジトリを接続する デプロイメント設定を管理する 高度なデプロイメント コードをデプロイする 既存の接続を管理する デプロイメントの実行ログ リポジトリから接続解除する WordPress.com の接続を GitHub から解除する 質問がある場合 AI アシスタントに尋ねる トップへ戻る 必要なものが見つからなかった場合 お問い合わせ 有料プランでは、AI アシスタントから回答を得たり、人間のエキスパートによる24時間年中無休のサポートを受けたりできます。 フォーラムで質問する 質問を参照して、他の経験豊富なユーザーから回答を得ることができます。 Copied to clipboard! WordPress.com 商品 WordPress ホスティング WordPress パートナープログラム アフィリエイトに参加 ドメイン名 AI サイトビルダー サイトビルダー ブログを作成 ビジネス用メールアドレス サイトデザインサービス WordPress Studio エンタープライズ WordPress 機能 概要 WordPress テーマ WordPress プラグイン WordPress パターン Google Apps リソース WordPress.com ブログ 会社名ジェネレータ ロゴメーカー WordPress.com Reader アクセシビリティ サブスクリプションを削除 ヘルプ サポートセンター ガイド コース フォーラム お問い合わせ 開発者向けリソース 会社 紹介 プレス 利用規約 プライバシーポリシー 個人情報を販売または共有しないでください カリフォルニア州のユーザーへのプライバシー通知 Deutsch Español Français Bahasa Indonesia Italiano Nederlands Português do Brasil Svenska Türkçe Русский العربية עִבְרִית 日本語 한국어 简体中文 繁體中文 English Deutsch Español Français Bahasa Indonesia Italiano Nederlands Português do Brasil Svenska Türkçe Русский العربية עִבְרִית 日本語 한국어 简体中文 繁體中文 English モバイルアプリ ダウンロード場所 アプリストア 取得場所 Google Play ソーシャルメディア WordPress.com の Facebook WordPress.com X (Twitter) WordPress.com の Instagram WordPress.com の YouTube Automattic Automattic 求人情報 コメントを読み込み中… コメントを投稿するには ログイン してください。 日本語サポート 登録 ログイン 短縮リンクをコピー このコンテンツを報告 購読管理 | 2026-01-13T09:29:33 |
https://wiki.documentfoundation.org/Talk:Design | Talk:Design - 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 Talk : Design 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 To-Do blue box: merge "Guidelines" and "UX Principals"? blue box: sort pages so they match the big four topics with icons do we really want 5 starting items with icons on that intro wikipage? I find that 1 too much and overwhelming to new users, also it looks too crowded on small screens Done blue box: rename "IRC-Chat" to "Meetings" ✔ blue box: rename "Branding" to "Artwork Resources" to match the 4 icon items ✔ Retrieved from " https://wiki.documentfoundation.org/index.php?title=Talk:Design&oldid=66837 " This page was last edited 07:28, 8 April 2013 by The Document Foundation Wiki user Steve . 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.ecns.cn/hd/2026-01-08/detail-iheyrzrv3839176.shtml | Heavey snow hits Paris --> 中文 Home News Ecns Wire Business Travel Photo Video Voices RIGHT BG LINE Text: A A A Print Photo Heavey snow hits Paris ( 1 /3) 2026-01-08 13:29:58 Ecns.cn Editor :Gong Weiwei Photo taken on Jan. 7, 2026 shows Notre-Dame Cathedral in Paris amid heavy snow. Paris experiences successive large-scale snowstorms this year, prompting the French meteorological authorities to maintain an orange alert for snow and ice in Paris. (Photo: China News Service/Li Yang) Photo taken on Jan. 7, 2026 shows the Eiffel Tower in Paris amid heavy snow. Paris experiences successive large-scale snowstorms this year, prompting the French meteorological authorities to maintain an orange alert for snow and ice in Paris. (Photo: China News Service/Li Yang) Photo taken on Jan. 7, 2026 shows the scene in Paris center amid heavy snow. (Photo: China News Service/Li Yang) Previous Next (1) (2) (3) LINE More Photo 'Southern Snow Town' draws tourists to Guizhou Province Global mayors attend dialogue in NE China on developing ice, snow economy Indonesia welcomes its first locally born giant panda cub Chinese FM on Venezuela situation: China always opposes imposing one country's will on another Maduro pleads not guilty in N.Y. court UN Security Council holds emergency meeting on Venezuela ${visuals_2} ${visuals_3} More Video More than a business hub: check how global merchants thrive in Yiwu Insights | Sanae Takaichi's erroneous remarks a grave 'diplomatic failure': Japanese scholar Insights丨From energy cooperation to industrial co-building: New momentum in Europe-China ties Insights丨China’s economy in UN official’s eyes: Resilience, exports, and high-tech transition 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 ${new_video_hd2} ${new_video_hd3} LINE Media partners: People's Daily | Xinhua | CGTN | China Daily Back to top About Us | Jobs | Contact Us | Privacy Policy Copyright ©1999-2026 Chinanews.com. All rights reserved. Reproduction in whole or in part without permission is prohibited. [ 网上传播视听节目许可证（0106168) ] [ 京ICP证040655号 ] [ 京公网安备 11010202009201号 ] [ 京ICP备05004340号-1 ] --> --> | 2026-01-13T09:29:33 |
https://www.chinadaily.com.cn/a/202512/15/WS69400264a310d6866eb2ebda.html | Ningbo hospital staff disciplined following pediatric surgery death - 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 China News Society Innovation HK/Macao Cross-Strait Cover Story Photo Environment Health Military Video Home / China / Society Home China Society Ningbo hospital staff disciplined following pediatric surgery death By Chen Ye in Hangzhou | chinadaily.com.cn | Updated: 2025-12-15 20:43 Share Share - WeChat --> CLOSE Senior staff at the Women and Children's Hospital of Ningbo University in Zhejiang province received punishment for cited medical lapses and management failures after a child died following heart surgery, according to a report released on Sunday. The child, surnamed Xu, died on Nov 14 after undergoing cardiac surgery at the hospital. Ningbo's health commission formed an investigation team to examine medical records, conduct on-site inspections, and interview staff. The case has been filed for medical record violations. A formal medical accident appraisal was launched, including an autopsy carried out by a forensic institution chosen by the family. Both the police and courts have accepted the family's report and lawsuit. According to the commission, investigators found multiple violations. The medical team was found to have insufficiently assessed surgical risks, made errors in surgical operation, failed to inform the family of intraoperative emergencies in a timely manner, and showed deficiencies in postoperative monitoring and management. The precise extent of medical fault and individual responsibility will be determined after completion of the medical accident appraisal. At the management level, the hospital was found to have poor medical quality and safety rules enforcement, inadequate risk prevention, poor emergency response, and a lack of humanistic care for patients and families. The commission ordered the hospital to conduct a thorough internal review and announced that: the Party secretary received a warning, the hospital president was given a demerit, the vice-president in charge of the relevant work was dismissed, the chief surgeon and the anesthesiologist were both stripped of their department head posts and suspended from clinical practice, and the pediatric intensive care attending physician was also suspended. Further measures will follow based on the results of the appraisal. In response to public concern, the commission noted that the chief surgeon was qualified for such operations. It also clarified that the operating room had one real-time, non-recording wide-angle camera and one recording camera focusing on the anesthesia cart; no cameras are installed in intensive care wards. The surveillance setup was said to comply with current regulations. The commission extended its condolences and an apology to the family, pledged to support them in defending their rights through legal channels, and promised to draw lessons from the case by tightening citywide oversight of medical quality and safety. --> --> Related Stories Newly declassified archives add evidence to Japan's wartime crimes against China Foreign trade reaches 41.21 trillion yuan in Jan-Nov 2025 Yangtze plan shows path forward for delta's future Milestone for port's container throughput Former legislator of Fujian sentenced to death Photo Workers build giant snowman in Heilongjiang Geminid meteor shower seen across China Beijing mobilizes for winter's first major snowfall Metasequoia avenue in Changsha showcases nature's splendor Beijing welcomes its first snowfall this winter Yanshiping, Xizang's highest railway station, begins service --> Latest Ningbo hospital staff disciplined following pediatric surgery death Mainland warns Taiwan leader against provoking conflict Former senior official of Shenzhen under investigation Beijing says Taiwan question brooks no foreign interference Chinese surgeon reflects on two missions to heal and train in Madagascar Beijing: Japanese fighter jets harassed pre-notified exercise zone --> State Council News A look at China's economy in November, 2025 Xi stresses strategic importance of work to raise minors' moral standards Xi's article on expanding domestic demand to be published Exclusive The Olympic spirit: a guiding light in everyday life When the Olympics meets tai chi AI robots shine at Tianjin's smart zero-carbon terminal Newsmaker Victims of massacre remembered Renowned actress He Qing passes away at 61 Ten photos you don't wanna miss Ten photos from across China: Dec 5 - 11 Special Coverage Live: Hong Kong residential area fire 4th Plenary Session of the 20th CPC Central Committee 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.atlassian.com/hu/jira/solutions/planning | Planning Project Management Software | 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 Atlassian recognized as a Leader in the 2025 Gartner Magic Quadrant™ for Collaborative Work Management! Learn more JIRA FOR PLANNING Flexible planning for every team Keep teams & stakeholders in sync, async, and stay aligned to your goals. Get Jira free Join the 300,000+ customers that power team collaboration with Atlassian Why use Jira for planning? Visualize your work Break down complex projects into small, manageable pieces. Effortlessly add and adjust work to visualize timing and sequence of different tasks. Easy sharing Timelines update in real-time as work progresses, making it instantly ready to share with teams, leaders, and stakeholders. Your plan, your style Whether you're starting from scratch or using a template, you have the freedom to customize your plan on your terms and needs. See how your work rolls into company goals COMPARE PLANNING FEATURES Advanced Basic Plans , an advanced planning feature in Jira Premium, allows multiple teams to collaborate on shared programs or goals. The timeline , a project view available across all Jira editions, allows you to plan and track work within a single team. Drive cross-functional work with Jira Track the big picture COMPARE PLANNING FEATURES Advanced Basic Plans help you track work across multiple teams and projects . In the summary screen of a plan, get a holistic view of work progress, dependencies, and team capacity. The timeline view allows you to plan work and track dependencies for a single team . Get ahead of dependencies COMPARE PLANNING FEATURES Advanced Basic Map dependencies between teams, spaces, and work items to get ahead of potential resourcing or scheduling conflicts. Avoid bottlenecks, coordinate handoffs, and keep your timeline on track. Map dependencies between work items within your project to identify and account for potential blockers. 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. Plan with team capacity in mind Advanced only Keep your goals on track by ensuring your teams have bandwidth to complete the work they’ve scoped. Manage multiple teams' capacity, set the right expectations with stakeholders, and understand the tradeoffs when plans change. Envision different scenarios Advanced only Paint a more complete picture of potential outcomes by creating multiple versions of your plan based on different options or best and worst-case scenarios. 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 made for planning Explore Jira’s customizable templates for every type of plan. High-level planning Plan, track, and report on company-wide efforts, such as a program or initiative. Cross-team planning Schedule and assign work, manage capacity, and track progress across multiple scrum teams. Project management From organizing tasks to visualizing timelines, enable teams to have a 360 view of project progress. Explore more templates Planning resources How to use Jira for planning Tutorials on how to plan work, track progress, and map dependencies. View guide Strategic planning with Jira Learn the strategic planning framework and how it can help you achieve big goals. Learn more Sprint planning essentials The essentials to applying scrum methodology in your team's workflows. Explore now Transform the way you work Where organizations and teams can work as one. Get it free 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 |
http://www.chinadaily.com.cn/a/202601/13/WS696603baa310d6866eb33739.html | My Fair Princess legacy rebooted with short drama - 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 Culture Art Music&Theater Film&TV Books Heritage Events&Festivals People Cultural Exchange Video Photo Home / Culture / Film and TV Home Culture Film and TV My Fair Princess legacy rebooted with short drama By Xu Fan | chinadaily.com.cn | Updated: 2026-01-13 16:34 Share Share - WeChat --> CLOSE Returning Pearl is inspired by the late writer Chiung Yao's novel My Fair Princess . [Photo provided to chinadaily.com.cn] My Fair Princess , a legendary tale about a tomboyish girl mistakenly identified as the long-separated daughter of Emperor Qianlong in the 18th century, became a phenomenal hit in 1998. More than two decades later, Returning Pearl , the latest installment in the My Fair Princess franchise — which includes the late writer Chiung Yao's namesake novel and three seasons of the original TV drama — has also made a splash, gaining popularity in Thailand, according to the producers. The new drama consists of 30 episodes, each about 15 minutes long, and introduces a new protagonist, Lin Suisui, a 25-year-old woman who unexpectedly travels into the fictional world of Chiung's novel. For mysterious reasons, the story veers in a strange and unsettling direction. Lin finds herself becoming a palace maid for the queen, one of the antagonists in the original narrative. In her attempt to return to the real world, Lin discovers that the only way out is to make all the characters follow the original plotline exactly. A scene from Returning Pearl. [Photo provided to chinadaily.com.cn] Since its debut on the streaming platform Mango TV in early November, the drama has garnered nearly 1 billion views online, with its related topics amassing around 2 billion clicks on major social media platforms such as Sina Weibo. Lyu Haidang, a producer of Returning Pearl , revealed that the core creative team spent three months polishing the script. Their biggest challenge was finding a point of resonance between Xiao Yanzi — a free-spirited street girl in the novel's era, the Qing Dynasty (1644-1911), mistakenly believed to be Emperor Qianlong's daughter — and a modern young audience. Jessie Ho, chief producer of Returning Pearl and daughter-in-law of Chiung, the original author, said that she believes the decades-long popularity of My Fair Princess stems not from any specific character or iconic plotline, but from the genuine emotions at the heart of its romantic story. "This 'genuine' quality is reflected in many aspects, from the young characters' yearning for freedom and their loyalty in friendship, to the courage to break through rigid class constraints and love boldly, regardless of how vast those social divides may be," said Ho. --> --> Related Stories 2025 captivating Chinese screens Film tribute to novelist is a dream for theatergoers Carrying an epic spirit over centuries Epic tale remains a story worth telling Fighting to promote a martial art Photo Galloping toward the new Festive atmosphere, immersive cultural experience in North China ancient town Super idol rewrites the script Through the Seasons invites reflection and renewal China releases Year of the Horse stamps amid collector enthusiasm Dishing up dynasties Most Popular Editor's Picks Tracing China's origins Tales & Trails: Gansu Linxia — a vibrant civilization along the Yellow River Photo Gallery Galloping toward the new Festive atmosphere, immersive cultural experience in North China ancient town Super idol rewrites the script Video 2025 captivating Chinese screens Leaping into the dark Tracking Chinese cultural frontline in 2025 Special Coverage Global Mayors Dialogue · Dunhuang World Conference on China Studies Chinaculture.org Golf: China's ancient game? Xinjiang: A living tapestry of intangible cultural heritage 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.tumblr.com/login | Register - Login By clicking log in, or continuing with the other options below, you agree to Tumblr’s Terms of Service and have read the Privacy Policy Log in Forgot your password? or Continue with Google Continue with Apple New to Tumblr? Sign up! Terms Privacy Jobs Support Sign up | 2026-01-13T09:29:33 |
https://www.chinadaily.com.cn/a/202507/09/WS686e60e4a31000e9a573b1ca.html | Joined together: A taste of Tianjin at the SCO Mayors' Dialogue - World - 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 / Videos Home / World / Videos Joined together: A taste of Tianjin at the SCO Mayors' Dialogue By Yin Weihao and Zheng Chenxiao | chinadaily.com.cn | Updated: 2025-07-09 20:30 Share Share - WeChat --> CLOSE At the Global Mayors Dialogue–SCO Summit Cities event in Tianjin on Tuesday, a giant mahua (twisted fried dough) brought by China Daily's Yin Weihao delighted international guests. Symbolizing hospitality, unity, and cooperation, it reflected the growing spirit of regional partnership. Learn more in the video. --> Photos Horta Inta-A sworn in as transitional president of Guinea-Bissau E4 foreign ministers condemn surge in West Bank settler violence Canadian minister resigns from cabinet over oil pipeline deal Chancay Port becomes new trade gateway Sabrina Dallafior appointed as next OPCW director-general S. Korea's 4th rocket launch successful Most Viewed in 24 Hours World in Focus Harsh reality Across Asia + In the eye of storm QR code menus get both ayes and noes in Malaysia Special Coverage + 2025 A Date with China GMD SCO Summit Cities Tianjin --> Friends Afar + Dive into the old world of Chinese martial arts 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 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://reports.jenkins.io/jelly-taglib-ref.html#form.3AhelpLink | 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.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://www.ecns.cn/video/2026-01-08/detail-iheyrzrv3838890.shtml | What's it like doing business in China? Check what foreign friends say --> 中文 Home News Ecns Wire Business Travel Photo Video Voices RIGHT BG LINE Text: A A A Print Video What's it like doing business in China? Check what foreign friends say 2026-01-08 10:46:59 Ecns.cn Editor : Ren Shuai ECNS App Download Known as the "World Capital of Small Commodities," Yiwu in Zhejiang Province attracts many foreign merchants with its abundant business opportunities and open, inclusive atmosphere. Curious about what it's like for foreign merchants to do business in Yiwu? Let's check what they say! More Photo Heavey snow hits Paris 'Southern Snow Town' draws tourists to Guizhou Province Global mayors attend dialogue in NE China on developing ice, snow economy Indonesia welcomes its first locally born giant panda cub Chinese FM on Venezuela situation: China always opposes imposing one country's will on another Maduro pleads not guilty in N.Y. court UN Security Council holds emergency meeting on Venezuela Harbin opens its 42nd Ice and Snow Festival China's Yangtze River remains world's busiest inland waterway by cargo throughput Bosideng Protest held in New York against U.S. military strikes on Venezuela Venezuelan President Nicolás Maduro transported to Brooklyn detention center International ice sculpture competition heats up in Harbin Mourners pay tribute to Crans-Montana bar fire victims Venezuelan leader Maduro brought to New York Beijing-Tangshan intercity railway starts full-line operation Passenger trips of 3 major Hainan airports exceed 50 million in 2025 First 'Grassland curling' attracts 350 competitors China launches two new satellites for space target detection test People perform 'circle dance' to pray for a bountiful new year in Qingha In numbers: China's high-speed rail mileage exceeds 50,000 km First batch of China's emergency humanitarian aid arrives in Cambodia Central London illuminated to welcome 2026 Chinese Foreign Minister meets Cambodian Deputy PM in Yunnan In Numbers: China holds Central Economic Work Conference to plan for 2026 Exploring vivid sports competition throughout 2025 Exploring stunning winter scenery in Altay China's first L3 self-driving car debuts in Chongqin Grand bridge ready for traffic operation in Guizhou Harbin's celebrity snowman lights up winter night Southbound Travel for Guangdong Vehicles scheme implemented for entry into urban Hong Kong China's Feng/Huang claim mixed doubles title at BWF World Tour Finals Exploring overwintering migratory birds in Poyang Lake Xi presents orders to promote two military officers to rank of genera Inner Mongolia holds winter festival Memorial held for victims of Bondi Beach shooting in Sydney Most popular in 24h More Top news 'Southern Snow Town' draws tourists to Guizhou Province China-Venezuela oil industry cooperation protected by int'l law: FM From luxury to everyday fruit: Chilean cherries become more affordable in China China expects huge surge in winter tourism Mainland sanctions Taiwan officials, warns separatists More Video More than a business hub: check how global merchants thrive in Yiwu Comicomment: Save or Slave? Hegemony at play 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://issues.jenkins.io/secure/MyJiraHome.jspa#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 System Dashboard Tools View as wallboard To move an item, select with Space and move with Ctrl/Cmd + Arrow keys 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.atlassian.com/ko/software/jira/free?templateId=com.atlassian.jira-core-project-templates%3Ajira-core-simplified-project-management | Jira Free: 무료로 Jira Software 사용 | Atlassian Close 선택한 언어 로 이 페이지를 보고 계십니까? 모든 언어 언어를 선택합니다. 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski | 2026-01-13T09:29:33 |
https://docs.aws.amazon.com/id_id/cost-management/latest/userguide/ce-enable.html | Mengaktifkan Cost Explorer - AWS Manajemen Biaya Mengaktifkan Cost Explorer - AWS Manajemen Biaya Dokumentasi AWS Billing and Cost Management Panduan Pengguna Terjemahan disediakan oleh mesin penerjemah. Jika konten terjemahan yang diberikan bertentangan dengan versi bahasa Inggris aslinya, utamakan versi bahasa Inggris. Mengaktifkan Cost Explorer Anda dapat mengaktifkan Cost Explorer untuk akun Anda dengan membuka Cost Explorer untuk pertama kalinya di konsol Manajemen AWS Biaya. Anda tidak dapat mengaktifkan Cost Explorer menggunakan API. Setelah Anda mengaktifkan Cost Explorer, AWS siapkan data tentang biaya Anda untuk bulan berjalan dan 13 bulan sebelumnya, lalu hitung perkiraan untuk 12 bulan ke depan. Data bulan ini tersedia untuk dilihat dalam waktu 24 jam. Sisa data Anda memerlukan waktu beberapa hari lebih lama. Cost Explorer memperbarui data biaya Anda setidaknya sekali setiap 24 jam. Sebagai bagian dari proses mengaktifkan Cost Explorer, AWS secara otomatis mengonfigurasi Deteksi Anomali Biaya untuk akun Anda. Deteksi Anomali AWS Biaya adalah fitur Manajemen Biaya. Fitur ini menggunakan model pembelajaran mesin untuk mendeteksi dan memperingatkan pola pengeluaran anomali dalam penerapan Anda. Layanan AWS Untuk memulai Deteksi Anomali Biaya, siapkan AWS Layanan AWS monitor dan langganan peringatan ringkasan harian. Anda diberitahu tentang pengeluaran anomali yang melebihi $100 dan 40% dari pengeluaran yang Anda harapkan di sebagian besar akun Anda Layanan AWS . Untuk informasi selengkapnya, lihat batasan dan Mendeteksi pengeluaran yang tidak biasa dengan Deteksi Anomali AWS Biaya . catatan Anda dapat memilih keluar dari Deteksi Anomali Biaya kapan saja. Untuk informasi lebih lanjut, lihat Memilih keluar dari Deteksi Anomali Biaya . Anda dapat meluncurkan Cost Explorer jika akun Anda adalah akun anggota di organisasi tempat akun pengelolaannya mengaktifkan Cost Explorer. Ketahuilah bahwa akun manajemen organisasi Anda juga dapat menolak akses akun Anda. Untuk informasi selengkapnya, lihat Tagihan Gabungan untuk AWS Organizations . catatan Status akun dalam organisasi menentukan data biaya dan penggunaan apa yang terlihat: Akun mandiri bergabung dengan organisasi. Setelah ini, akun tidak dapat lagi mengakses data biaya dan penggunaan sejak akun tersebut merupakan akun mandiri. Akun anggota meninggalkan organisasi untuk menjadi akun mandiri. Setelah ini, akun tidak dapat lagi mengakses data biaya dan penggunaan sejak akun tersebut menjadi anggota organisasi. Akun hanya dapat mengakses data yang dihasilkan sebagai akun mandiri. Akun anggota meninggalkan organisasi A untuk bergabung dengan organisasi B. Setelah ini, akun tidak dapat lagi mengakses data biaya dan penggunaan sejak akun tersebut menjadi anggota organisasi A. Akun hanya dapat mengakses data yang dihasilkan sebagai anggota organisasi B. Akun bergabung kembali dengan organisasi tempat akun tersebut sebelumnya dimiliki. Setelah ini, akun mendapatkan kembali akses ke biaya historis dan data penggunaannya. Mendaftar untuk menerima Laporan AWS Biaya dan Penggunaan atau Laporan Penagihan Terperinci tidak secara otomatis mengaktifkan Cost Explorer. Untuk melakukannya, ikuti prosedur ini. Untuk mendaftar ke Cost Explorer Buka Konsol Manajemen Penagihan dan Biaya di https://console.aws.amazon.com/costmanagement/ . Di panel navigasi, pilih Cost Explorer . Pada halaman Selamat Datang di Cost Explorer , pilih Luncurkan Cost Explorer . Untuk informasi selengkapnya tentang mengendalikan akses ke Cost Explorer, lihat Mengontrol akses ke Cost Explorer . Javascript dinonaktifkan atau tidak tersedia di browser Anda. Untuk menggunakan Dokumentasi AWS, Javascript harus diaktifkan. Lihat halaman Bantuan browser Anda untuk petunjuk. Konvensi Dokumen Menganalisis biaya dan penggunaan Anda dengan AWS Cost Explorer Mengontrol akses ke Cost Explorer Apakah halaman ini membantu Anda? - Ya Terima kasih telah memberitahukan bahwa hasil pekerjaan kami sudah baik. Jika Anda memiliki waktu luang, beri tahu kami aspek apa saja yang sudah bagus, agar kami dapat menerapkannya secara lebih luas. Apakah halaman ini membantu Anda? - Tidak Terima kasih telah memberi tahu kami bahwa halaman ini perlu ditingkatkan. Maaf karena telah mengecewakan Anda. Jika Anda memiliki waktu luang, beri tahu kami bagaimana dokumentasi ini dapat ditingkatkan. | 2026-01-13T09:29:33 |
https://issues.jenkins.io/login.jsp?os_destination=%2Fsecure%2FMyJiraHome.jspa | Log into Atlassian - Jenkins Jira Log in Skip to main content Skip to sidebar Dashboards Projects Issues Give feedback to Atlassian Help Keyboard Shortcuts About Jira Jira Credits Log In 📢 Jenkins core issues have been migrated to GitHub , no new core issues can be created in Jira Atlassian Jira Project Management Software About Jira Report a problem Powered by a free Atlassian Jira open source license for The Linux Foundation. Try Jira - bug tracking software for your team. Atlassian | 2026-01-13T09:29:33 |
https://www.tumblr.com/support?language=hi_IN | सहायता केंद्र | 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/ko/jira/solutions/planning#tab-5bc36440-29ba-4ab6-9a42-719565edd5aa | 계획 프로젝트 관리 소프트웨어 | Atlassian Close 선택한 언어 로 이 페이지를 보고 계십니까? 모든 언어 언어를 선택합니다. 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 무료로 시작 기능 모든 기능 Jira의 Rovo Back 솔루션 팀 사용 사례 회사 규모 팀 마케팅 엔지니어링 디자인 운영팀 IT 사용 사례 시작하기 계획 캠페인 관리 애자일 프로젝트 관리 프로그램 관리 회사 규모 Enterprise Back 제품 가이드 템플릿 템플릿 모든 템플릿 소프트웨어 개발 마케팅 디자인 영업 운영팀 서비스 매니지먼트 HR 법무 IT 운영 재무 Jira Service Management 템플릿 Back 가격 자세한 내용 + 간략히 보기 - 무료로 시작 Back 무료로 시작 Atlassian이 2025년 Gartner Magic Quadrant™의 공동 작업 관리 부문에서 리더로 선정되었습니다! 자세히 알아보기 계획을 위한 Jira 모든 팀을 위한 유연한 계획 팀 및 이해 관계자가 동기화, 비동기화 및 목표에 정렬된 상태를 유지하세요. Jira Free 받기 Atlassian으로 팀 공동 작업을 강화하는 30만 명 이상의 고객과 함께하세요 계획에 Jira를 사용하는 이유는 무엇입니까? 작업 시각화 복잡한 프로젝트를 관리하기 쉬운 작은 작업으로 나누세요. 작업을 쉽게 추가하고 조정하여 다양한 작업의 시기 및 순서를 시각화하세요. 간편한 공유 작업이 진행되면서 타임라인이 실시간으로 업데이트되어 팀, 리더 및 이해 관계자와 즉시 공유할 준비가 됩니다. 원하는 스타일로 계획 처음부터 시작하든 템플릿을 사용하든 조건 및 요구 사항에 따라 자유롭게 계획을 사용자 지정할 수 있습니다. 작업이 회사 목표에 어떻게 기여하는지 확인하세요 계획 기능 비교 Advanced Basic Jira Premium의 고급 계획 기능인 계획 을 사용하면 여러 팀이 공동의 프로그램 또는 목표에 대해 공동 작업할 수 있습니다. 모든 Jira 에디션에서 사용할 수 있는 프로젝트 보기인 타임라인 을 사용하면 단일 팀 내에서 작업을 계획하고 추적할 수 있습니다. Jira로 교차 기능 작업을 추진하세요 큰 그림 추적 계획 기능 비교 Advanced Basic 계획을 통해 여러 팀 및 프로젝트에 걸쳐 작업을 추적할 수 있습니다. 계획 요약 화면에서 작업 진행률, 종속성 및 팀 작업 수용량을 총체적으로 확인할 수 있습니다. 타임라인 보기를 통해 단일 팀 의 작업을 계획하고 종속성을 추적할 수 있습니다. 종속성 미리 파악 계획 기능 비교 Advanced Basic 팀, 프로젝트 등 간 종속성을 매핑하여 잠재적인 리소싱 또는 일정 충돌을 미리 파악하세요. 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. 팀 역량을 염두에 두고 계획 Advanced 전용 팀이 범위가 지정된 작업을 완료하는 데 필요한 역량을 갖추도록 하여 목표에 맞게 진행하세요. 스프린트별로 여러 팀의 작업 수용량을 확인하세요. 서로 다른 시나리오 구상 Advanced 전용 다양한 옵션 또는 최고 및 최악의 시나리오에 따라 계획을 여러 버전으로 만들어 잠재적인 결과에 대해 더 완전한 그림을 그리세요. 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의 사용자 지정 가능한 템플릿을 살펴보세요. 개략적인 계획 프로그램 또는 이니셔티브와 같은 대규모 작업을 계획하고 추적하고 보고하세요. 교차 팀 계획 여러 스크럼 팀 간에 작업 일정을 수립 및 할당하고 작업 수용량을 관리하고 진행률을 추적합니다. 프로젝트 관리 작업 체계화부터 타임라인 시각화까지, 팀이 프로젝트 진행률을 360도로 볼 수 있도록 하세요. 더 많은 템플릿 탐색 계획 리소스 자세히 알아보려면 무료 자습서, 문서 및 가이드를 살펴보세요. 계획에 Jira를 사용하는 방법 작업 계획, 진행률 추적 및 종속성 매핑 방법에 대한 자습서입니다. 가이드 보기 Jira를 사용한 전략적 계획 전략적 계획 프레임워크 및 이것이 큰 목표를 달성하는 데 어떻게 도움이 되는지 알아보세요. 자세히 알아보기 스프린트 계획 필수 사항 팀의 워크플로에 스크럼 방법론을 적용하기 위한 필수 사항입니다. 지금 살펴보기 업무 수행 방식의 혁신 조직 및 팀이 하나가 되어 일할 수 있는 곳. 무료로 시작 회사 구직 이벤트 블로그 투자자 관계 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/detail/volume-master/top-charts/detail/volume-master/detail/grammarly-ai-writing-assi/kbfnbcaeplbcioakkpcpgfkobkghlhen | 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://giga.global/unicef-itu-partnership/our-collaboration/ | Our collaboration | UNICEF ITU Partnership | 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 Our Collaboration Home Who We Are Our Collaboration Home Who We Are Our Collaboration Our Collaboration What sets us apart Often referred to as a startup within the UN system, Giga draws on the expertise of two major organizations: ITU leads on telecommunications policy and regulation, while UNICEF focuses on leveraging its country presence, convening power, and expertise in education and child rights to implement and scale connectivity solutions. Global support, international recognition We work with support of the Governments of Switzerland and Spain together with other Governments, UN organizations, tech industry players, the international finance community and more. Giga’s impact was recognized in the Global Digital Compact as an important stepping stone to helping connect all schools and hospitals to the internet by 2030. Leaders driving the initiative Doreen Bogdan-Martin ITU Secretary-General Follow on Follow on Dr. Cosmas Luckyson Zavazava Director, Telecommunication Development Bureau (BDT), ITU Follow on Follow on Catherine Russell UNICEF Executive Director Follow on Follow on Giga Co-Leads Christopher Fabian Giga Co-Lead, UNICEF Follow on Follow on Christopher’s career has focused on how the intersection between new technology and global policy can solve the world’s most pressing problems and advance humanity. He has advised two UN Secretary-Generals on new technologies, founded and scaled UNICEF’s Innovation Unit, and worked with Heads of State and CEOs to invest in responsible, forward-looking technologies. Christopher has built, invested in, and mentored technology companies from startup through multiple financing rounds and exit. He has led teams that developed some of the largest implementations of open-source mobile phone applications in the world, the first public-sector drone/UAV corridors, the first crypto-currency denominated fund in the public sector, and the Digital Public Goods Alliance with the Government of Norway. He is a Commissioner for the Lancet-Financial Times, an Honorary Scholar at the Chinese Central Academy of Fine Arts, a Board Member of the European Parliaments STOA Centre for Artificial Intelligence, and was recognized by Time Magazine as one of the “World’s 100 Most Influential People” in 2013. Alex Wong Giga Co-lead, ITU Follow on Follow on Alex has over 30 years professional experience in leadership roles with a focus on building and implementing partnerships to address the world’s biggest development challenges. Alex currently serves in the Executive Office of the ITU, the UN agency for digital technology, where he oversees Giga, as well as Partner2Connect, an ITU-led initiative to achieve universal, meaningful connectivity and digital transformation. From 2019-2022, Alex served as Senior Strategy Advisor and Chief, Special Initiatives, in the Office of the Director of the Telecommunications Development Bureau (BDT). Prior to joining the ITU, Alex worked in both the private and not-for-profit sectors. He is a licensed professional engineer with a degree in mechanical engineering from the University of Toronto and a master’s in public administration from Harvard University. 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 |
http://groovy-lang.org/syntax.html#_string_concatenation | 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.tumblr.com/support?language=zh_HK | 幫助中心 | Tumblr 登入 註冊 © Tumblr, Inc. 說明 關於 Tumblr App 開發人員 佈景主題 工作 法律 條款 版權 私隱權 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 |
http://groovy-lang.org/syntax.html#_triple_single_quoted_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://wiki.documentfoundation.org/Special:RecentChanges | Recent changes - 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 Recent changes Help English Tools Tools move to sidebar hide Actions General RSS Atom Special pages Printable version Appearance move to sidebar hide Track the most recent changes to the wiki on this page. Recent changes options Show last 50 | 100 | 250 | 500 changes in last 1 | 3 | 7 | 14 | 30 days Hide registered users | Hide anonymous users | Hide my edits | Show bots | Hide minor edits Show new changes starting from 09:29, 13 January 2026 Namespace: all (Main) Talk User User talk Project Project talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Widget Widget talk Module Module talk Translations Translations talk Invert selection Associated namespace 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 Users (Sep: |): List of abbreviations: N This edit created a new page (also see list of new pages ) m This is a minor edit b This edit was performed by a bot (±123) The page size changed by this number of bytes 13 January 2026 09:27 User:Regina/Sandbox for new functions in Calc diff hist −82 Regina talk contribs ( → {{Documentation/Calc_Functions/Arguments}} : WIP) 12 January 2026 19:55 Development/VCL/widgets diff hist −94 Hossein talk contribs ( → Description of widgets : Widget and Container are not used in .ui files anyway) N 17:16 Releases/26.2.0/RC1 diff hist +5,780 X1sc0 talk contribs (create page) 17:14 Releases/25.8.0/RC1 diff hist 0 X1sc0 talk contribs (fix id)  16:43  ReleasePlan/26.2 2 changes history −1 [ X1sc0 (2×)]   16:43 (cur | prev ) 0 X1sc0 talk contribs (update RC2 as well)   16:17 ( cur | prev ) −1 X1sc0 talk contribs (update release weeks to avoid conflicts with FOSDEM) 12:54 Development/VCL diff hist +29 Hossein talk contribs ( → User interface design : Add a new section) N  05:15  Events/2026 3 changes history +1,919 [ Raniaamina ; Diahasy (2×)] m   05:15 (cur | prev ) −2 Diahasy talk contribs ( → India/APAC )   05:15 ( cur | prev ) +187 Diahasy talk contribs ( → India/APAC : Event information) N   01:53 ( cur | prev) +1,734 Raniaamina talk contribs (Created page with "{{TopMenu}} {{Menu}} {{Menu.Events}} This page lists '''2026 Events''' put on, attended by, or otherwise relevant-to TDF/LibreOffice. {{Infobox Events |title = Events By Year |dates = 2026 |location = everywhere |website = wiki.documentfoundation.org |previous = Events/2025 <!-- The navigation will loop around: [Events] -> 2011 -> 2012 -> 2013 -> 2014 -> 2015 -> 2016 -> 2017 ->[Events] --> |next = Events/2026 <!-- Will be changed to Events/2027 once that page exists -...") 11 January 2026  23:15  ReleaseNotes/26.2/it 9 changes history −781 [ Akurery (9×)]   23:15 (cur | prev ) −196 Akurery talk contribs (Created page with "dbm viene distribuito assieme alla versione incorporata di python.")   23:10 ( cur | prev ) −216 Akurery talk contribs (Created page with "Il motore grafico Skia ora è obbligatorio sia su Windows che su macOS.")   23:05 ( cur | prev ) −203 Akurery talk contribs (Created page with "Aggiunto il supporto per l'esportazione in formato Markdown ([https://vmiklos.hu/blog/sw-markdown-filter.html post sul blog]).")   23:00 ( cur | prev ) −37 Akurery talk contribs (Created page with "File:JSON Doc Mapped to Calc Sheet.png|documento JSON con un intervallo collegabile mappato in un foglio di Calc")   22:55 ( cur | prev ) −44 Akurery talk contribs (Created page with "quando viene aperto, viene mappato nel seguente intervallo di valori.")   22:55 ( cur | prev ) −45 Akurery talk contribs (Created page with "=== Mappatura di file XML e JSON generici in Calc ===")   22:50 ( cur | prev ) −44 Akurery talk contribs (Created page with "Una parte dell'infrastruttura che agisce sui connettori è stata portata da sd a svx. Questa modifica consente l'implementazione della funzionalità dei connettori in altri moduli (Calc, Writer).")   22:45 ( cur | prev ) +23 Akurery talk contribs (Created page with "Alcuni contenuti degli stili di grafico nel formato OOXML ora riescono a passare con successo un ciclo completo di importazione/esportazione attraverso LibreOffice (OOXML -> LO -> OOXML). Per ora questa funzionalità è incompleta e i dati dello stile non sono né disponibili, nè modificabili dall'interfaccia utente.")   22:40 ( cur | prev ) −19 Akurery talk contribs (Created page with "Tenendo fermo il cursore del mouse sugli elementi della tavolozza dei colori per l'intervallo dei dati del Grafico nella Barra laterale ora viene mostrata un'anteprima immediata nel grafico attivo.") 19:30 Faq/General/de diff hist +2 Bammbamm7 talk contribs  19:25  Faq/General/033/de 2 changes history +15 [ Bammbamm7 (2×)]   19:25 (cur | prev ) −1 Bammbamm7 talk contribs   19:20 ( cur | prev ) +16 Bammbamm7 talk contribs N 19:25 Faq/General/036/de diff hist +2,360 Bammbamm7 talk contribs (Created page with "FAQ/Allgemein/036") 19:20 Faq/General/010/de diff hist −2 Bammbamm7 talk contribs N  19:20  Faq/General/148/de 6 changes history +725 [ Bammbamm7 (6×)]   19:20 (cur | prev ) −68 Bammbamm7 talk contribs (Created page with "Wenn LibreOffice aktuell beim Windows-Start geladem wird und das geändert werden soll, können die folgenden Instruktionen helfen.")   19:15 ( cur | prev ) −65 Bammbamm7 talk contribs (Created page with "LibreOffice kann beim Windows-Start geladen werden. Das hilft, die Startzeit der Applikation zu reduzieren, wenn eine Datei erstellt oder geändert werden soll.")   19:10 ( cur | prev ) +134 Bammbamm7 talk contribs   19:05 ( cur | prev ) −197 Bammbamm7 talk contribs (Created page with "# Gehe zu {{bc|Extras|Optionen}} (Oder {{key|Alt|F12}})")   17:50 ( cur | prev ) +20 Bammbamm7 talk contribs (Created page with "==Wie kann ich LibreOffice schon beim Windows-Start laden?==") N   12:50 ( cur | prev) +901 Bammbamm7 talk contribs (Created page with "FAQ/Allgemein/148") N  17:50  Faq/General/a11y/Java/de 6 changes history +7,358 [ Bammbamm7 (6×)]   17:50 (cur | prev ) +24 Bammbamm7 talk contribs (Created page with "=== Oracle "Java Accessibility Bridge" and JRE Konfiguration ===")   17:45 ( cur | prev ) −38 Bammbamm7 talk contribs (Created page with "LibreOffice 3.6.4 reaktivierte die AT Tools Unterstützung für Java Accessibility Funktionen für JRE und JAB, die die UNO Accessability API Funktionen abbilden. Versionen 3.6.0, 3.6.1 und 3.6.3 unterstützen keine AT Tools. LibreOffice 3.5 Builds bis 3.5.7, 3.6.4 - 3.6.7 und jetzt die 4.0.4 Builds bieten fachlich AT mit einer korrekt konfigutrierten Java 6 Runtime Environementund die Java Access Bridge v2.0.2.</big>}}")   17:35 ( cur | prev ) +1 Bammbamm7 talk contribs   17:05 ( cur | prev ) −101 Bammbamm7 talk contribs   12:55 ( cur | prev ) −51 Bammbamm7 talk contribs (Created page with "Neuere Builds von LibreOffce (ab 4.2.0.0 dev, 4.1.0.4 und 4.0.5.0 dev) haben unterstützen bereits Oracle Java SE 7, Java Runtime Environement (JRE) 1.7u45 mit seiner eingebetteten Java Access Bridge (JAB) v2.0.3 (aktivierbar über das Kommando "jabswitch -enable"). Sie können aber auch auf Java SE 6 und JRE 1.6u45 mit einer Installation von JAB 2.0.2 umsteigen. -- 2013-07-24") N   12:50 ( cur | prev) +7,523 Bammbamm7 talk contribs (Created page with "Faq/Allgemein/a11y/Java") 13:35 User:MichaMuc diff hist +32 MichaMuc talk contribs  13:04  DE/Handbuch-Erstellung 2 changes history −24 [ MichaMuc (2×)] m   13:04 (cur | prev ) 0 MichaMuc talk contribs ( → Handbuch für Calc : Kap. 15 bgcolor)   13:02 ( cur | prev ) −24 MichaMuc talk contribs ( → Handbuch für Calc : Kapitel_15_Calc_als_Datenbank_25.8 zum Review) 12:58 Upload log MichaMuc talk contribs uploaded a new version of File:Calc Handbuch Kapitel 15 Calc als Datenbank 25.8.odt (Stand zum Review) 10 January 2026  22:23  User:Regina/Sandbox for new functions in Calc 3 changes history −3,700 [ Regina (3×)]   22:23 ( cur | prev ) +87 Regina talk contribs (WIP)   21:43 ( cur | prev ) +2 Regina talk contribs ( → Random selection : WIP)   21:39 ( cur | prev ) −3,789 Regina talk contribs (WIP) 22:10 User:Nobu/日本語訳 diff hist +163 Nobu talk contribs ( → Wiki 関数 )  21:05  ReleaseNotes/26.2/it 5 changes history −216 [ Akurery (5×)]   21:05 ( cur | prev ) +28 Akurery talk contribs (Created page with "Introdotte su Windows le API Microsoft Media Foundation API per supportare la riproduzione di Video e Audio con dei codecs comuni. Queste consentono di gestire la riproduzione di video con [https://learn.microsoft.com/en-us/windows/win32/medfound/getting-started-with-mfplay MFPlay]. Relativamente ai formati supportati dei file video e audio (senza alcuna installazione aggiuntiva di codec) è possibile trovare maggiori informazioni a questo [https://support.microsoft.com/...")   21:00 ( cur | prev ) −198 Akurery talk contribs (Created page with "È stata ottimizzata l'esportazione in formato SVG con molte bitmap.")   20:55 ( cur | prev ) −45 Akurery talk contribs (Created page with "Le impostazioni locali delle opzione della finestra di dialogo Ordina ora vengono scritte nel file e perciò mantenute. La modifica delle impostazioni locali agisce non solo sulla scelta di un algoritmo speciale di ordinamento, ma ora anche su altre proprietà di ordinamento dipendenti dalle impostazioni locali, ad esempio quale carattere è usato come separatore decimale nell'ordinamento naturale.")   20:50 ( cur | prev ) +41 Akurery talk contribs (Created page with "Quando l'ordinamento naturale è abilitato nelle opzioni della finestra di dialogo Ordina, c'è l'opzione aggiuntiva che consente di trattare i separatori decimali come caratteri normali. Questo permette di ordinare degli indirizzi IP, per esempio, anche se le impostazioni locali prevedono il punto come separatore decimale. Il fatto che l'ordinamento naturale è abilitato ora viene scritto nel file e quindi mantenuto alla sua riapertura.")   20:45 ( cur | prev ) −42 Akurery talk contribs 20:45 ReleasePlan/it diff hist −206 Akurery talk contribs (Created page with "12 giugno 2026") Retrieved from " https://wiki.documentfoundation.org/Special:RecentChanges " Privacy policy About The Document Foundation Wiki Imprint | 2026-01-13T09:29:33 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3AdropdownDescriptorSelector | 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/secure/EditLabels!default.jspa?id={0}&returnUrl=/secure/issues#main | Error - 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 Error The issue no longer exists. 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=zh_TW | 說明中心 | 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.tumblr.com/support?language=id_ID | Pusat Bantuan | Tumblr Masuk Daftar © Tumblr, Inc. Bantuan Tentang Tumblr Aplikasi Developer Tema Karier Legal Ketentuan Hak cipta Privasi 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://reports.jenkins.io/jelly-taglib-ref.html#form.3Aform | 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.mineo.app?trk=products_details_guest_secondary_call_to_action | Experiment. Build. Deploy. Any Python Framework | MINEO Platform Toggle Menu Platform Notebooks & Development Interactive Notebooks Python, SQL, Markdown & LaTeX Widgets & Layouts Build interactive data apps Version Control Track changes & history Sharing Notebooks Collaborate and share your work Data Apps & Deployment Live Apps Streamlit, Gradio, and more Streamlit Apps Deploy Streamlit applications Gradio Apps Machine learning interfaces FastAPI Apps High-performance APIs Data & Integrations Data Sources Connect any database ETL Pipelines Automate workflows File System Manage files & folders Git Integration Version control & CI/CD AI Assistant Hot MINEO Assistant AI-powered data analysis Data Interpretation Transform complex data into insights Instant App Creation From idea to app in seconds Code Acceleration Supercharge Python development Platform & Setup Organizations Manage teams & permissions Worker Images Custom environments Projects Organize your workspace Getting Started Setup & onboarding View Documentation | See Pricing Start free forever Solutions Financial Services Finance & Banking Risk analysis & trading insights Insurance Claims processing & risk assessment Commerce & Business Retail & E-commerce Customer analytics & inventory Marketing & Sales Campaign optimization & CRM Industrial Manufacturing Production analytics & quality control Energy & Utilities Grid optimization & consumption Transportation & Logistics Route optimization & fleet management Services Healthcare & Life Sciences Patient data & clinical research Education Student analytics & performance Media & Entertainment Content analytics & engagement See our customers | Talk to an expert Find your solution Showcase Pricing About About us Contact us Documentation Blog Log in Start free forever 🚀 Log in Start free forever 🚀 4.8 Experiment. Build. Deploy. Repeat. Any Python Framework. Your notebooks, your frameworks, our infrastructure. Prototype in Jupyter , build with MINEO's visual tools or code in Streamlit, Gradio, Dash, and 6+ more frameworks. Ship 10x faster . Dual Development Modes : Create apps with MINEO's drag-and-drop notebooks OR deploy native Streamlit/Gradio/FastAPI code. 9+ Python Frameworks : Native support for Streamlit, Gradio, Plotly Dash, Panel, Voilà, Mercury, Solara, Shiny for Python, and FastAPI. Powered by MINEO Assistant : An AI agent powered by OpenAI O3, seamlessly analyzing and explaining your data. From Notebook to App Instantly : Deploy interactive dashboards and data pipelines with ease. Universal Connectivity : Integrate with 10+ data sources or any Python package. Enterprise-Ready Platform : Secure, scalable, and built for collaboration. Get started for free 🚀 Request a demo Trusted by Experiment Build Deploy Repeat Your complete workflow in one platform. Experiment in notebooks, build with visual tools or code, deploy any Python framework instantly. No DevOps, no containers, just results. From Jupyter prototypes to production apps in minutes, not months. Choose your style: drag-and-drop or code in 9+ frameworks including Streamlit, Gradio, and Plotly Dash. More than 5,000 data apps and counting! 📓 MINEO Notebooks 📊 Plotly Dash Analytics 📝 Mercury Documents ⚡ FastAPI Services 📱 Data apps 🧐 Data Observability 🐍 Python tutorial 👀 Performance review 🔮 Forecast sales 🎯 Customer Segmentation 🚗 Autonomous Vehicles 🎬 Media Processing 🏭 Manufacturing Analytics 🎵 Music Analysis ✈️ Travel Planning ⚡ Energy Optimization 🎯 Marketing Attribution 💳 Fraud Detection 🎨 Design Automation 🖥️ Streamlit Dashboards 🎨 Panel Applications ⭐ Solara Apps 🎨 Drag & Drop Builder 🛤️ Data Pipelines 🧠 RAG 🚀 Gen AI MVP 👁️ Fine-Tune Yolo 💵 Personal expenses 💡 Innovation Labs 🏦 Financial Modeling 🛡️ Security Monitoring 🌐 Web Scraping 🍕 Food Delivery 💎 Recommendation Engine 🚴 Fitness Tracking 🔊 Voice Analysis 🎪 Event Analytics 🎛️ Gradio ML Apps 📈 Voilà Reports 📱 Shiny Python 📊 Visual SQL ⚙️ ETL ✍️ Image annotation 📈 Sales tracking 🛰️ IoT Asset Tracking 🦙 Llama3 Fine tuning 🎮 Game Analytics 🌱 Climate Analysis 📚 Education Tools 📱 Mobile Analytics 🏠 Real Estate 🧬 Genomics Research 📦 Supply Chain 🌍 Geographic Analysis 🚀 Space Data Get started for free 🚀 Everything You Need to Ship 10x Faster From experiment to production in minutes, not months. Visual tools for speed, 9+ frameworks for flexibility, enterprise features for scale. Stop configuring infrastructure, start shipping features. Experiment Build Deploy Scale 9+ Frameworks AI Powered AI-Powered Assistant (OpenAI O3) Get instant help with your Jupyter notebooks, automatic code fixes, and smart data analysis suggestions. Like having a data scientist on your team 24/7. Visual Notebook Builder Create data apps with MINEO's drag-and-drop widgets, visual SQL builder, and interactive charts - no coding required. 9+ Python Frameworks Native Support Deploy Streamlit, Gradio, Plotly Dash, Panel, Voilà, Mercury, Solara, Shiny for Python, and FastAPI apps directly. No containers needed. Enhanced Jupyter Environment Supercharged Python Jupyter notebooks with real-time collaboration, advanced autocomplete, and 90-day version history built-in. Universal Data Connectivity Connect to PostgreSQL, MySQL, ClickHouse, CSV files, and 10+ data sources. One platform for all your data science projects. Automated Data Pipelines Schedule your notebooks to run automatically. Build ETL processes and machine learning pipelines that work while you sleep. Visual SQL Workbench Build complex database queries visually with intelligent suggestions and performance optimization. No SQL expertise required. Enterprise Team Management Secure collaboration with SSO authentication, granular permissions, and unlimited users. Perfect for data science teams. White-Label Data Applications Customize themes, remove MINEO branding, and embed data visualizations anywhere. Make every dashboard professionally yours. Multi-Cloud Deployment Deploy data applications on AWS, Google Cloud, Azure, or on-premise. Enterprise-grade security with 99.9% SLA guarantee. Git Integration for Data Science Full version control for your data science projects. Seamless GitHub, GitLab integration with conflict resolution. Custom Python Environments Deploy with any Python packages, custom Docker images, and GPU acceleration. Scale from prototype to production instantly. SHOWCASE Real data apps built with MINEO Explore interactive dashboards and applications created by leading organizations to democratize data insights across their teams Nano Banana Transform your photos with AI using Gemini Image Generation Ads Analyzer Ads Analyzer is a tool that evaluates ad images by extracting key messages, audience insights, and persuasive techniques. It provides a rating, effectiveness summary, and prioritized improvement suggestions. Face recognition 2 This Face Recognition app demonstrates DeepFace's capabilities, including facial detection, verification, demographic estimation, and emotion analysis. It identifies faces in images or live feeds, comparing them to a reference database and displaying similarity scores and the best match. SVG Optimizer SVG Optimizer compresses any SVG file by reducing its size and optimizing both the structure and embedded images for maximum efficiency. Florence 2 Florence-2 is a versatile vision foundation model that uses text prompts to perform a wide range of computer vision and vision-language tasks, trained on a massive dataset of visual annotations to achieve strong zero-shot and fine-tuning capabilities. Phi-Vision 3 Microsoft Phi-3 Vision is a multimodal AI model that integrates language and vision capabilities, featuring 4.2 billion parameters and supporting a context length of 128K tokens, making it suitable for applications like OCR, image understanding, and interpreting charts and tables. Llama 3 Discover Meta's Llama3, a state-of-the-art large language model (LLM) for advanced natural language processing, with this data app that runs the model locally. Embeddings visualizer Visualize and interact with embeddings using this advanced data app. It enables you to explore and understand complex data patterns through interactive visual representations of embeddings, facilitating deeper insights and enhanced data analysis capabilities. Join leading organizations transforming their data workflows Explore All Applications 4.8 What our customers think about MINEO MINEO is trusted by data scientists, engineers, and organizations worldwide. It is super powerful. You can create all the BI you need using Python directly as if it were a Jupyter Notebook but with a much better presentation. You can create super visual and useful panels using Python and present them as production panels to display your data. Martin G. Tech Lead, Data Truth Great platform for working and collaborating with Python Notebooks Ismael M. Operations Director MINEO has the features of Power Bi and Google Colab, all in one. I have been working with MINEO for more than a year. I have been able to perfectly carry out both data analysis and visualisation projects, as well as more advanced data science projects. Juan Pedro P. Data Scientist, MIOTI Great platform to build dashboards and data apps over Python Notebooks. MINEO Assistant is a truly game changer! Miguel G. CTO, Perif.ai Excellent platform combining Google Colab with great data visualization and analytics Manuel M. Senior Deep Learning Scientist An alternative to PowerBI and Google Colab combined into one unique tool. Luis T. Software designer and developer GREAT Data Analytics and Data Visualization in an online collaborative platform! Alejandro M. Full Stack Engineer, Unlimiteck Your All-in-One Tool for Data Science Projects. I have now been using MINEO for almost a year, and I can confidently say it has transformed the way I approach data science projects. Edgar M. Data Scientist Easy interface to create a dashboard with Python code (Pandas, Matplotlib, etc.). The distribution of modules is seamless, without the limitations of libraries like Dash. Henar M Biomedical research engineer It is super powerful. You can create all the BI you need using Python directly as if it were a Jupyter Notebook but with a much better presentation. You can create super visual and useful panels using Python and present them as production panels to display your data. Martin G. Tech Lead, Data Truth Great platform for working and collaborating with Python Notebooks Ismael M. Operations Director MINEO has the features of Power Bi and Google Colab, all in one. I have been working with MINEO for more than a year. I have been able to perfectly carry out both data analysis and visualisation projects, as well as more advanced data science projects. Juan Pedro P. Data Scientist, MIOTI Great platform to build dashboards and data apps over Python Notebooks. MINEO Assistant is a truly game changer! Miguel G. CTO, Perif.ai Excellent platform combining Google Colab with great data visualization and analytics Manuel M. Senior Deep Learning Scientist An alternative to PowerBI and Google Colab combined into one unique tool. Luis T. Software designer and developer GREAT Data Analytics and Data Visualization in an online collaborative platform! Alejandro M. Full Stack Engineer, Unlimiteck Your All-in-One Tool for Data Science Projects. I have now been using MINEO for almost a year, and I can confidently say it has transformed the way I approach data science projects. Edgar M. Data Scientist Easy interface to create a dashboard with Python code (Pandas, Matplotlib, etc.). The distribution of modules is seamless, without the limitations of libraries like Dash. Henar M Biomedical research engineer Ready to Ship 10x Faster? Join 5,000+ data scientists who stopped configuring infrastructure and started shipping features. Any framework, zero DevOps. Get started for free 🚀 Request a demo Explore your data, build , deploy and share data apps powered by Code, No-code & AI. 4.8 LinkedIn Product Customers Pricing plans Documentation Meta Contact us Blog About us Legal Cookie policy Legal notice Privacy policy © 2025 MINEO Data Solutions S.L. All Rights Reserved Made with ❤️ in 🇪🇸 | 2026-01-13T09:29:33 |
https://community.atlassian.com/forums/Jira-Product-Discovery/ct-p/jpd#confluence-gradient-nav-menu-a | Jira Product Discovery | Atlassian Community Community Forums Learning Events Champions Sign up Log in Community Forums Home Q&A Discussion groups Articles Ask a question Search Learning Events Champions Sign up Log in Community Community Forums Home Q&A Discussion groups Articles Ask a question Search Learning Events Champions Sign up Log in Forums Home Q&A Discussion groups Articles Ask a question Search Learning Events Champions Sign up Log in Forums Q&A Discussion groups Articles Create Ask a question cancel Turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Did you mean: Q&A Jira Jira Confluence Confluence Jira Service Management Jira Service Management Bitbucket Bitbucket Rovo Atlassian Intelligence Rovo Trello Trello Jira Product Discovery Loom jira-align Jira Align See all Community resources Announcements FAQ Guidelines About Support Documentation and support Atlassian Community Events Atlassian Learning Top groups groups-icon Welcome Center groups-icon Featured Groups groups-icon Product Groups groups-icon Regional Groups groups-icon Industry Groups groups-icon Community Groups Explore all groups Community resources Announcements FAQ Guidelines About Support Documentation and support Atlassian Community Events Atlassian Learning Learn Learning Paths Certifications Courses by Product Community resources Announcements FAQ Guidelines About Support Documentation and support Atlassian Community Events Atlassian Learning Events Live learning Local meet ups Community led conferences Community resources Announcements FAQ Guidelines About Support Documentation and support Atlassian Community Events Atlassian Learning Community Q&A Jira Product Discovery Jira Product Discovery Announcements Welcome to the Jira Product Discovery community! Learn about our community or “ask the community” a question/start a discussion using the button above. All Articles Questions Discussions Sort by Most recent Most recent Trending Oldest Most views Most likes All community This category Knowledge base Users cancel Turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Did you mean: Featured Jira Product Discovery Resources Roundup! Check out all of these great resources from the Jira Product Discovery team! Below you’ll find resources organized by team: All teams Product Management teams Engineering teams ... 43,284 views 1 29 Chris Hall May 8, 2025 Article jpd Featured How-to guide: set up JPD for many teams with the Premium plan In the Premium plan we’re catering for the needs of larger companies looking for a prioritisation and roadmapping solution that works across many teams. The goal of this guide is to help you unders... 25,837 views 13 21 Tanguy Crusson May 2, 2025 Article jpd Featured What are we up to? Public roadmap for Jira Product Discovery Hi everyone! We want to thank you all for your trust, and for spending time to give us great feedback. It helps us make this product better every day. We do listen to your feedback - if you want to... 84,060 views 58 60 Tanguy Crusson November 26, 2024 Article jpd Featured Introducing the Atlassian Product Discovery handbook! 🙌 Jira Product Discovery reached more than 10,000 customers recently ❤️🔥 To celebrate this milestone we're launching the Atlassian Product Discovery handbook, full of the hard earned lessons we gai... 69,418 views 30 79 Tanguy Crusson October 10, 2024 Article jpd Featured Known limitations of Jira Product Discovery As we collect more and more feedback from you, we wanted to share the current functional limitations (and their eventual workarounds) in Jira Product Discovery: Importing ideas has limitations Yo... 62,580 views 68 72 Hermance NDounga July 4, 2022 Article active-directory Featured Frequently asked questions - about the product (how do I...?) Licensing questions What are the different types of users, and who needs to pay? Read this: Creators, Contributors and Stakeholders. How do I add contributors to a Jira ... 107,298 views 49 52 Tanguy Crusson April 14, 2022 Article faq jpd Jira Product Discovery - Idea multi structure Hi, I have recently obtained a Jira Product Discovery licence and experimenting with implementing a product roadmap for my Team (Crew) which has 15 squads owning different products. My Crew belongs t... 36 views 2 0 Simon Choy yesterday Question cloud idea jira jira-cloud jira-product-discovery +2 more tags... Can't login to any of my JPD spaces Hi everyone, I wonder why I can't log in into any of my JPD spaces - is this an Atlassian outage or there may be other reason? I'm in a free cloud plan and I'm the admin. Thank you! 55 views 2 0 oksana sudoma yesterday Question jpd Ability to Collapse Groups by Default on Published JPD Board View I have a number of Published Views (JPD Boards) that utilise the Group by functionality to segment items. A key area of feedback from the stakeholders consuming these views is that they would find t... 25 views 0 0 Jack Lawson Sunday Question jpd Jira Product Discovery Delivery Progress Ignores “To Do” Child Issues When Linked to Epic We have recently encountered a problem in Jira Product Discovery, specifically related to the Delivery process and Delivery status fields. We have noticed that when an idea is linked to an epic,... 85 views 5 0 Can Peskersoy Friday Question jpd Guide: Quarterly planning Quarterly planning is the strategic ritual where product teams translate high-level goals into actionable commitments. It is the moment to pause, assess what was learned in the previous quarter, and ... 140 views 0 5 Jet Friday Article jpd Guide: Lightweight Resource planning While Jira Product Discovery isn't a dedicated resource management tool, its flexibility allows for lightweight capacity planning. In this article I'm sharing an example which helps you compare estim... 117 views 2 7 Jet Friday Article jpd Guide: Creating a Leadership Roadmap Different stakeholders need different roadmaps. While your engineering team needs operational details, your leadership team cares about strategic alignment, investment areas, and capacity. This gui... 113 views 0 3 Jet Friday Article jpd Guide: Delivery Tracker The Delivery Tracker provides a real-time bird's-eye view of execution. It is designed to keep stakeholders informed on development status without overwhelming them with work item-level noise. No... 104 views 0 5 Jet Friday Article jpd Guide: Mastering prioritization with RICE Effective prioritization is a superpower of successful product teams. It enables you to move fast and focus on high-impact activities. However, prioritization isn't a solo task—it is a collaborative ... 161 views 2 4 Jet Friday Article jpd Any plans to enable wrapped text on timeline view Hi team, I've rolled out JPD in my company and would love to show value statements for each idea on the public facing roadmap. These statements are within the character limit set by JPD but don't di... 62 views 4 2 Peter Scobie Thursday Question jpd “Create” modal loses configured create form when opening Space dropdown and switching spaces. Hi — I’m seeing a issue in Jira Product Discovery with the Create ideas form configuration. Context In a JPD space, we configured Space settings → Create ideas: “Customize the create form f... 53 views 1 0 Thea Paar Thursday Question jpd Need advice for building out a process in JSM TL;DR what would be the best practice to building out a process/procedure for decommissioning hardware/servers in a JSM Space without over complicating and cluttering things up? Our Systems ... 44 views 1 0 John Izquierdo Thursday Question automation condition jira-automation jsm workflow Jira Product Discovery - Customer Insights & Dashboards Our team is building out our product ideas on Jira Product Discovery, and the application is extremely useful. For context we are focused on institutional customers. We are struggling to find a sm... 132 views 4 1 Edward McCluggage Wednesday Question cloud jira jira-cloud jira-product-discovery jpd Retain rich text format from a new idea in Product Discovery when creating a new page in Confluence I've been trying to setup an automation when a new Idea is created in JPD. What I want to do is create a new Confluence page in an existing folder that contains the name and description of the new id... 95 views 1 0 Jyll Rademacher Wednesday Question automation cloud confluence jira jira-cloud +2 more tags... Anyone migrate from ProductBoard to JIRA Product Discovery? We are currently using ProductBoard and this new boards thing is driving me absolutely insane - I am spending hours just trying to configure the new boards and I keep finding issues and gaps. I'm wo... 43 views 1 0 Ciara McDaniel Wednesday Question jpd migration productboard Automation to update field based on Delivered Story points I have it set on schedule, weekly if status is 'pending sign off' and if Custom Field is empty I want the total storypoints 'delivered' / 30 set to FieldX as a whole number. Rovo indicated:&n... 74 views 6 0 Tere Pile Tuesday Question jpd How do I get the most out of Jira How do I do this? 69 views 1 0 Taylor James Frey Tuesday Question jpd 📣 Planned maintenance on Sunday, January 18, 2026 Hello JPD community, We are scheduling another short maintenance window to make your experience smoother and more reliable. The maintenance will take place on Sunday, January 18th, 2026... 464 views 1 5 Rishabh Jha Tuesday Article jpd Cannot get JPD > 'Connection' Field to Enable I have watched the videos and read the SOP but I cannot get this feature to work on my account: https://community.atlassian.com/forums/Jira-Product-Discovery-articles/Product-hierarchies-Con... 101 views 2 0 Caleb Brunel January 5, 2026 Question jpd Why do users with the Contributor role have access to everything in JPD? We purchased a Premium license for our organization to give different parties access to a few views and the ability to comment, vote, and add ideas. However, the Contributor role allows users to edi... 267 views 5 0 Jarmo Valli December 29, 2025 Question jpd More Visibility into Delivery Tickets from *within* JPD Hi JPD Community. I want to be able to expand linked Jira work items (Stories, Epics, Bugs) that are Delivery Tickets for my JPD items directly within the JPD idea list or board view so that I can q... 2,183 views 2 0 Jena Miller December 24, 2025 Question jpd Is there a way to Tshirt size by squad and not just by idea? We have development teams or squads that specialize in certain skills An idea will be scoped and will often need engineering resources from multiple squads When we tshirt size, we need to do ... 185 views 3 0 Bob December 23, 2025 Question jpd how can I add new members to JPD project I manage? as an Administrator a creator of a JPD project, I would like to add new members to the project 160 views 2 0 IV10 Fredy Rabih December 21, 2025 Question jpd Is there any way to configure a list of fields to be shown in Structure by Tempo? We are using both JPD and Structure by Tempo. We have a Structure view that shows JPD items (we call them initiatives) that have under them epics, stories, and so on. This works great. However, whe... 147 views 2 0 Omer Meshar December 21, 2025 Question addon-com.almworks.jira.structure jpd How can I link Jira Software intake tickets to Jira Product Discovery ideas without skewing delivery We have an intake form and board in Jira Software. Many items are small bugs or tickets that bypass Jira Product Discovery, but for larger enhancement requests, I create Jira Product Discovery ideas.... 205 views 3 0 Mckenzi Gravesmill December 17, 2025 Question jpd « Previous 1 2 3 … 100 Next » 2,491 posts 666 watchers Watch Get updates by Email RSS Please log in to sign up for email updates about new posts Articles Copy Copied to clipboard Questions Copy Copied to clipboard Discussions Copy Copied to clipboard Copy the URL of any content type you'd like to watch. AUG Leaders Atlassian Community Events See all events Last 30 days User Count Tanguy Crusson 10 Kamila Czubaj 5 Bill Sheboy 1 Denis Paul 1 Nikola Perisic 1 Hari Krishna 1 See all Unanswered Topics Subject Author Posted Ability to Collapse Groups by Default on Published... Jira Product Discovery questions Jack Lawson Sunday PICK Chart - custom fields with if/then logic Jira Product Discovery questions Elise Edson September 26, 2025 10:43 AM PDT Jira product discovery new idea template not defau... Jira Product Discovery questions Fiona Lauchlan July 16, 2025 4:40 AM PDT Ability to Control the Group by Column Summary Dat... Jira Product Discovery questions Brandon Moberg July 11, 2025 5:28 PM PDT Is it possible to use different templates for diff... Jira Product Discovery questions Matt Hadfield July 11, 2025 2:38 AM PDT See all Community Forums FAQs Forums guidelines Learning About learning Resources Events Champions Copyright © 2026 Atlassian Privacy Policy Notice at Collection Terms Security | 2026-01-13T09:29:33 |
https://giga.global/unicef-itu-partnership/our-centres/ | Our Centres - giga.global 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 Our Centres Home Who We Are Our Centres Home Who We Are Our Centres Our Centres Who We Are Giga Connectivity Centre The Giga Connectivity Centre is located at Campus Biotech – the heart of international Geneva. It is a collaborative space for joint UNICEF/ITU teams to meet, co-create and collaborate as we seek to connect every school in the world to the Internet by 2030. Launched in June 2025, thanks to the support of the Government of Switzerland, the Connectivity Centre also serves as Giga’s headquarters and home to the Learning Hub, in collaboration with ITU Academy, the main arm of Giga’s capacity development activities. Through training and workshops, the Learning Hub provides the knowledge and skills needed for effective school connectivity planning, from data collection to procurement and financing. Giga’s annual flagship event, the Giga Connectivity Forum , is held at the Geneva centre, bringing together over 40 country delegations, UN and international finance agencies, academia and connectivity experts to advance universal school connectivity. With its open and bright setting, the centre is also offered to the Geneva community as the ideal location for learning engagements, partner meetings and showcase demonstrations to strengthen synergies or spark new ones in the field of digital development. To learn more, explore our Connectivity Centre brochure and if you’re interested in hosting your next event in this inspiring and welcoming space, please complete our form below. Event request form Who We Are Giga Technology Centre Located in Barcelona’s vibrant high-tech district, the Giga Technology Centre is a hub of expertise in developing cutting-edge open-source solutions for school connectivity. The centre is home to a team of over 25 engineers and data scientists who research and create new connectivity tools and services, including geolocation mapping of schools, infrastructure assessment and guidance on policy and regulatory strategies. The centre is home to the Government Technology Exchange Programme, which gathers technical delegations from governments to learn about Giga’s product suite while the hosts gain insights into each country’s school connectivity goals and challenges. Since opening in late 2023, the centre is also expanding its role as a meeting point for tech community events, inviting a range of people and organizations interested in technological development to come together and exchange ideas. Thanks to our supporters — the Government of Spain, the Regional Government of Catalonia and the Barcelona City Council — The Giga Tech Centre is housed in the historical Ca l’Alier, a former 19th-century textile factory converted into an innovation space. 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://aws.amazon.com/solutions/case-studies/expedia/ | Customer Success Stories: Case Studies, Videos, Podcasts, Innovator stories Skip to main content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account AWS › Solutions SOLUTIONS Customer Success Stories Discover how customers across industries increase agility, optimize costs, and accelerate innovation using AWS How Blue Origin Built the First AI Agent-Designed Hardware for the Moon in Days, Not Years At Blue Origin, the mission is existential: to build a road to space, enabling millions of people to live and work beyond Earth. And getting there is literal rocket science, and beyond. It's about moving faster than the speed traditional aerospace development allows. That means rethinking how engineering teams work — and teaming up with AWS to build tools that turn specialized expertise into scalable AI workflows. One recent breakthrough: TEAREx (Thermal Energy Advanced Regolith Extraction), the first AI agent-designed hardware, built to operate on the lunar surface, developed from concept to 3D-printed part in days, using AWS. Read the case study Play Pinterest pushes boundaries of AI-powered discovery using AWS Pinterest transformed from an idea-sharing startup into one of the world's most sophisticated AI-powered discovery engines, serving 600 million monthly users who explore, share, and shop. What makes this journey remarkable isn't just the evolution of scale—it's how Pinterest has reimagined what social media can be, proving that generative AI can be used responsibly to drive positive user experiences alongside massive growth and profitability. Read the case study Customer Stories Generative AI Leading Cloud Innovators Browse All Customer Stories Phagos is using generative AI to change the way infectious diseases are treated Phagos has a remarkable mission: to end bacterial disease. Today, Phagos is turning that vision into reality by harnessing bacteriophages, nature's bacteria-killing viruses, to cure infectious disease. Bacteriophages, or phages, are the natural regulators of bacteria. In an era of rising antibiotic resistance, there is an urgent need for this new antibacterial solution. AWS technologies allow Phagos to decode massive genomic datasets to develop these customized treatments in just two months, compared to the 10+ years that traditional antibiotic development requires. Read the case study Play Featured Case Studies across industries 1 / 5 TwelveLabs unlocks the full potential of video for the world Mercedes Benz is transforming global IT moving to AWS for RISE with SAP and Agentic AI Condé Nast transforms publishing legacy into data-driven digital media for AI innovation Cox Automotive launched AI agents at scale using Amazon Bedrock AgentCore AudioShake is teaching machines to hear like humans, with AI Benefits 1,000,000+ of active customers every month. 330,000+ startups have used AWS to bring their ideas to life. Browse customer stories Loading Loading Loading Loading Loading Did you find what you were looking for today? Let us know so we can improve the quality of the content on our pages Yes No Create an AWS account Learn What Is AWS? What Is Cloud Computing? What Is Agentic AI? Cloud Computing Concepts Hub AWS Cloud Security What's New Blogs Press Releases Resources Getting Started Training AWS Trust Center AWS Solutions Library Architecture Center Product and Technical FAQs Analyst Reports AWS Partners Developers Builder Center SDKs & Tools .NET on AWS Python on AWS Java on AWS PHP on AWS JavaScript on AWS Help Contact Us File a Support Ticket AWS re:Post Knowledge Center AWS Support Overview Get Expert Help AWS Accessibility Legal English Back to top Amazon is an Equal Opportunity Employer: Minority / Women / Disability / Veteran / Gender Identity / Sexual Orientation / Age. x facebook linkedin instagram twitch youtube podcasts email Privacy Site terms Cookie Preferences © 2026, Amazon Web Services, Inc. or its affiliates. All rights reserved. | 2026-01-13T09:29:33 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3ArepeatableDeleteButton | 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/support?language=zh_CN | 帮助中心 | Tumblr 登录 注册 © Tumblr, Inc. 帮助 关于我们 应用 开发者 主题 工作机会 法律 条款 版权 隐私 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://docs.aws.amazon.com/fr_fr/cost-management/latest/userguide/what-is-costmanagement.html | Qu'est-ce que c'est AWS Billing and Cost Management ? - AWS Gestion des coûts Qu'est-ce que c'est AWS Billing and Cost Management ? - AWS Gestion des coûts Documentation AWS Billing and Cost Management Guide de l’utilisateur Caractéristiques de AWS Billing and Cost Management Services connexes Les traductions sont fournies par des outils de traduction automatique. En cas de conflit entre le contenu d'une traduction et celui de la version originale en anglais, la version anglaise prévaudra. Qu'est-ce que c'est AWS Billing and Cost Management ? Bienvenue dans le guide de l'utilisateur de AWS Cost Management. AWS Billing and Cost Management fournit une suite de fonctionnalités pour vous aider à configurer votre facturation, à récupérer et à payer les factures, ainsi qu'à analyser, organiser, planifier et optimiser vos coûts. Pour commencer, configurez votre facturation en fonction de vos besoins. Pour les particuliers ou les petites organisations, le AWS débit sera automatiquement effectué sur la carte de crédit fournie. Pour les grandes entreprises, vous pouvez l'utiliser AWS Organizations pour regrouper vos frais sur plusieurs Comptes AWS. Vous pouvez ensuite configurer la facturation, les taxes, les bons de commande et les méthodes de paiement en fonction des processus d'approvisionnement de votre organisation. Si vous en avez plusieurs AWS Organizations, utilisez le transfert de facturation pour gérer et payer de manière centralisée toutes vos organisations à partir d'un seul compte. Vous pouvez répartir vos coûts aux équipes, aux applications ou aux environnements en utilisant des catégories de coûts ou des balises de répartition des coûts, ou en utilisant AWS Cost Explorer. Vous pouvez également exporter des données vers votre entrepôt de données ou votre outil d'intelligence d'entreprise préféré. Consultez la présentation suivante des fonctionnalités pour vous aider à gérer vos finances cloud. Caractéristiques de AWS Billing and Cost Management Rubriques Facturation et paiements Analyse de coût Organisation des coûts Budgétisation et planification Économies et engagements Facturation et paiements Comprenez vos frais mensuels, consultez et payez vos factures et gérez les préférences en matière de facturation, de taxes et de paiements. Page Factures : téléchargez les factures et consultez les données de facturation mensuelles détaillées pour comprendre comment vos frais ont été calculés. Bons de commande : créez et gérez vos bons de commande pour vous conformer aux processus d'approvisionnement uniques de votre organisation. Paiements : comprenez votre solde impayé ou en souffrance et l'historique de vos paiements. Profils de paiement — Configurez plusieurs méthodes de paiement pour différents Service AWS fournisseurs ou parties de votre organisation. Crédits : vérifiez les soldes créditeurs et choisissez où les crédits doivent être appliqués. Préférences de facturation : activez la livraison des factures par e-mail et vos préférences en matière de partage de crédit, d'alertes et de partage de remises. Transfert de facturation : sépare la gestion de la facturation et des finances de la gestion de la sécurité et de la gouvernance. Cela permet à une seule AWS organisation d'obtenir un accès centralisé aux données de coûts et aux AWS factures de plusieurs AWS organisations. Analyse de coût Analysez vos coûts, exportez des données détaillées sur les coûts et l'utilisation et prévoyez vos dépenses. AWS Cost Explorer : analysez vos données sur les coûts et l'utilisation à l'aide de visuels, de filtres et de regroupements. Vous pouvez prévoir vos coûts et créer des rapports personnalisés. Exportations de données : créez des exportations de données personnalisées à partir des jeux de données Billing and Cost Management. Détection des anomalies de coûts — Configurez des alertes automatisées en cas AWS de détection d'une anomalie de coût afin de réduire les coûts imprévus. Niveau gratuit d'AWS : surveillez l'utilisation actuelle et prévisionnelle des services gratuits pour éviter les coûts imprévus. Données de répartition des coûts fractionnés : activez des données détaillées sur les coûts et l'utilisation pour les ressources partagées d'Amazon Elastic Container Service (Amazon ECS). Préférences de gestion des coûts : gérez les données que les comptes membres peuvent consulter, modifiez la granularité des données du compte et configurez les préférences d'optimisation des coûts. Organisation des coûts Organisez vos coûts entre les équipes, les applications ou les clients finaux. Catégories de coûts : mappez les coûts aux équipes, aux applications ou aux environnements, puis visualisez les coûts selon ces dimensions dans Cost Explorer et dans les exportations de données. Définissez des règles de frais fractionnés pour répartir les coûts partagés. Balises de répartition des coûts : utilisez des balises de ressources pour organiser, puis affichez les coûts par balise de répartition des coûts dans Cost Explorer et dans les exportations de données. Budgétisation et planification Estimez le coût d'une charge de travail planifiée et créez des budgets pour suivre et contrôler les coûts. Budgets : définissez des budgets personnalisés pour les coûts et l'utilisation afin de contrôler les coûts dans l'ensemble de votre organisation et de recevoir des alertes lorsque les coûts dépassent les seuils définis. Calculateur de prix intégré à la console : utilisez cette fonctionnalité pour estimer vos coûts cloud prévus en fonction de vos engagements de réduction et d'achat. Site Web de calcul des prix publics — Créez des estimations de coûts pour l'utilisation de AWS services avec des tarifs à la demande. Économies et engagements Optimisez l'utilisation des ressources et utilisez des modèles de tarification flexibles pour réduire votre facture. Hub d'optimisation des coûts AWS : identifiez les opportunités d'économies grâce à des recommandations personnalisées, notamment la suppression des ressources inutilisées, le redimensionnement, les Savings Plans et les réservations. Savings Plans — Réduisez votre facture par rapport aux prix à la demande grâce à des modèles de tarification flexibles. Gérez l'inventaire de vos Savings Plans, passez en revue les recommandations d'achat, effectuez des analyses d'achat et analysez l'utilisation et la couverture des Savings Plans. Réservations — Réservez de la capacité à des tarifs réduits pour Amazon Elastic Compute Cloud (Amazon EC2), Amazon Relational Database Service (Amazon RDS), Amazon Redshift, Amazon DynamoDB, etc. Services connexes AWS Billing Conductor Billing Conductor est un service de facturation personnalisé qui prend en charge les flux de travail de rétrofacturation et de rétrofacturation des AWS partenaires revendeurs Services AWS, des solutions et des AWS clients qui achètent des services cloud directement par le biais de ce service. AWS Vous pouvez personnaliser une deuxième version alternative de vos données de facturation mensuelles. Le service modélise la relation de facturation entre vous et vos clients ou unités commerciales. Billing Conductor ne modifie pas la façon dont vous êtes facturé AWS chaque mois. Vous pouvez plutôt utiliser le service pour configurer, générer et afficher les tarifs pour des clients spécifiques au cours d'une période de facturation donnée. Vous pouvez également l'utiliser pour analyser la différence entre les taux que vous appliquez à vos groupements par rapport aux taux réels pour ces mêmes comptes. AWS Grâce à votre configuration de Billing Conductor, le compte de gestion peut également voir le taux personnalisé appliqué sur la page des informations de facturation de la AWS Billing and Cost Management console . Le compte de gestion peut également configurer des rapports de AWS coûts et d'utilisation par groupe de facturation. Lorsque les utilisateurs du transfert de factures se connectent au compte de transfert de factures, Billing Conductor permet au compte de gestion de l' AWS organisation qui transfère leurs factures (compte source des factures) de consulter uniquement leur consommation facturée avec les tarifs du compte de transfert de factures. Pour plus d'informations sur Billing Conductor, consultez le Guide de l'utilisateur AWS Billing Conductor . Pour plus d'informations sur le transfert de facturation, voir Transférer la gestion de la facturation vers des comptes externes . IAM Vous pouvez utiliser Gestion des identités et des accès AWS (IAM) pour contrôler les utilisateurs de votre compte ou de votre organisation qui ont accès à des pages spécifiques de la console Billing and Cost Management. Par exemple, vous pouvez contrôler l'accès aux factures et aux informations détaillées sur les frais et l'activité de votre compte, les budgets, les moyens de paiement et les crédits. L'IAM est une fonctionnalité de votre. Compte AWS Vous n'avez rien d'autre à faire pour vous inscrire à IAM et son utilisation est gratuite. Lorsque vous créez un compte, vous commencez avec une seule identité de connexion qui donne un accès complet à toutes Services AWS les ressources du compte. Cette identité est appelée Utilisateur racine d'un compte AWS et est accessible en vous connectant avec l'adresse e-mail et le mot de passe que vous avez utilisés pour créer le compte. Il est vivement recommandé de ne pas utiliser l’utilisateur racine pour vos tâches quotidiennes. Protégez vos informations d’identification d’utilisateur racine et utilisez-les pour effectuer les tâches que seul l’utilisateur racine peut effectuer. Pour obtenir la liste complète des tâches qui vous imposent de vous connecter en tant qu’utilisateur racine, consultez Tâches nécessitant des informations d’identification d’utilisateur racine dans le Guide de l’utilisateur IAM . Par défaut, les utilisateurs et les rôles IAM de votre compte ne peuvent pas accéder à la console Billing and Cost Management. Pour accorder l'accès, activez le paramètre Activer l'accès IAM . Pour plus d'informations, consultez À propos de l'Acces IAM . Si vous en avez plusieurs Comptes AWS dans votre organisation, vous pouvez gérer l'accès aux comptes associés aux données de Cost Explorer en utilisant la page des préférences de gestion des coûts . Pour plus d'informations, consultez la section Contrôle de l'accès à Cost Explorer . Pour de plus amples informations sur IAM, consultez le Guide de l’utilisateur IAM . AWS Organizations Vous pouvez utiliser la fonctionnalité de facturation consolidée dans les organisations pour consolider la facturation et le paiement pour plusieurs Comptes AWS. Chaque organisation dispose d’un compte de gestion qui paie les frais de tous les comptes membres . La facturation consolidée comporte les avantages suivants : Une seule facture : obtenir une seule facture pour plusieurs comptes. Suivi simplifié : suivre les frais sur plusieurs comptes et télécharger les données combinées de coût et d'utilisation. Utilisation combinée : combiner l'utilisation entre tous les comptes de l'organisation afin de partager les remises de tarification sur volume, les remises sur instances réservées et les Savings Plans. Cela peut entraîner des frais moins importants pour votre projet, service ou société qu'avec des comptes autonomes individuels. Pour plus d'informations, consultez Remises sur volume . Pas de frais supplémentaires – La facturation consolidée est proposée sans coût supplémentaire. Pour plus d'informations sur les organisations, consultez le Guide de l'utilisateur AWS Organizations . Transfert de facturation Vous pouvez utiliser le transfert de facturation pour gérer et payer plusieurs factures de manière centralisée AWS Organizations à partir d'un seul compte. Le transfert de facturation permet à un compte de gestion de désigner un compte de gestion externe pour gérer et payer sa facture consolidée. Cela centralise la facturation tout en préservant l'autonomie de gestion de la sécurité. Pour configurer le transfert de facturation, un compte externe (compte de transfert de facture) envoie une invitation de transfert de facturation à un compte de gestion (compte source de facturation). Si l'invitation est acceptée, le compte externe devient le compte de transfert de factures. Le compte de transfert de factures gère et paie ensuite la facture consolidée du compte source de factures, à compter de la date spécifiée dans l'invitation. Pour plus d'informations, voir Transférer la gestion de la facturation vers des comptes externes . AWS API de liste de prix AWS L'API Price List est un catalogue centralisé dans lequel vous pouvez demander par programmation des informations sur AWS les services, les produits et les prix. Vous pouvez utiliser l'API en bloc pour récupérer des informations de up-to-date AWS service en masse, disponibles aux formats JSON et CSV. Pour plus d'informations, consultez Qu'est-ce que l'API AWS Price List ? . JavaScript est désactivé ou n'est pas disponible dans votre navigateur. Pour que vous puissiez utiliser la documentation AWS, Javascript doit être activé. Vous trouverez des instructions sur les pages d'aide de votre navigateur. Conventions de rédaction Débuter avec la gestion des AWS coûts Cette page vous a-t-elle été utile ? - Oui Merci de nous avoir fait part de votre satisfaction. Si vous avez quelques minutes à nous consacrer, merci de nous indiquer ce qui vous a plu afin que nous puissions nous améliorer davantage. Cette page vous a-t-elle été utile ? - Non Merci de nous avoir avertis que cette page avait besoin d'être retravaillée. Nous sommes désolés de ne pas avoir répondu à vos attentes. Si vous avez quelques minutes à nous consacrer, merci de nous indiquer comment nous pourrions améliorer cette documentation. | 2026-01-13T09:29:33 |
http://www.chinadaily.com.cn/a/202601/13/WS6965f4cfa310d6866eb33702.html | Jinan, a City of Springs Jinan Today Transportation leap propels Jinan toward national hub Media Center HOME > Media Center > Jinan Today begin-->Transportation leap propels Jinan toward national hub end--> begin-->english.jinan.gov.cn end--> | Updated: 2026-01-12 L M S begin--> Jinan has made notable progress in modernizing its transportation infrastructure during the 14th Five-Year Plan period (2021–25), establishing itself as a national transportation hub. A major achievement is the development of a comprehensive expressway network, including two ring roads, a regional network connecting neighboring economic hubs, and 16 highways extending across Shandong province and beyond. By the end of 2025, Jinan's total highway mileage reached 915.6 kilometers, giving it the province's highest road density and largest share of two-way, six-lane expressways. The city has led the integration of travel and tourism with the S103 scenic highway, improving access to the southern mountainous area. In rural areas, over 16,000 km of roads have been upgraded, significantly boosting access to resources and industries while also encouraging tourism to rural destinations. Transportation across the Yellow River has also progressed. With eight new crossings, Jinan now has 21 Yellow River bridges and tunnels. Four bridges and two tunnels in the main urban area are operational, with the Huanggang Road and Hangtian Avenue tunnels under construction. These developments have reduced commuting time between the river's northern and southern banks. end--> Expand --> In Focus Projects in Motion: Insights into Jinan's Development in 2025 Targets set in 2025 government work report 2024 Chinese government achievements in numbers Investing Working Studying Living Produced By 大汉网络 大汉版通发布系统 | 2026-01-13T09:29:33 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3Asection | 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/support?language=it_IT | Centro di supporto | Tumblr Entra Registrati © Tumblr, Inc. Aiuto Su Tumblr App Sviluppatori Temi Opportunità Informazioni Legali Termini 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 |
http://groovy-lang.org/syntax.html#_number_type_suffixes | 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#collapse4 | 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://giantrabbit.com/our-work?client=usenix | Our Work | Giant Rabbit Skip to main content Menu Close Main navigation Our Services Our Work About Us Strategy Design Development CRM Selection & Data Migration Fundraising & User Analytics Drupal 7 Upgrades to Backdrop CMS Project Rescues Managed Hosting Support & Maintenance Security  All Arts & Culture Education Environment Health Human Rights Social Justice Technology & Privacy  About Giant Rabbit The Team Jobs Contact Us  Our Work Our clients are fighting for public health, access to abortion, and LGBTQ+ rights. They're going to court on behalf of asylum-seekers and promoting human rights around the world. We support organizations that fight climate change, work for environmental conservation, and warn people about the risks of avalanches. Our clients are also working theaters, performing arts organizations, museums, and cultural institutions. Defending human rights at home and abroad. Partner Since 2018 Center for Gender and Refugee Studies Partner Since 2022 Family Violence Appellate Project Partner Since 2013 Front Line Defenders Partner Since 2022 Human Rights First Partner Since 2022 Justice Action Center Partner Since 2016 National Network of Abortion Funds (NNAF) Partner Since 2020 Observatory for the Protection of Human Rights Defenders Partner Since 2022 Youth Law Center Working toward a healthier future. Partner Since 2019 American Academy of Pediatrics California Chapter 1 Partner Since 2022 Advancing New Standards in Reproductive Health (ANSIRH) Partner Since 2023 Beyond the Pill Partner Since 2015 Cutaneous Lymphoma Foundation Partner Since 2020 Farmers Market Coalition Partner Since 2021 HealthRIGHT 360 Partner Since 2019 Ibis Reproductive Health Services Partner Since 2020 Mandela Partners Protecting the environment and fighting climate change. Partner From 2022 To 2023 Audubon Canyon Ranch Partner Since 2017 Ecology Center Partner Since 2014 Edible Schoolyard Project Partner Since 2007 eLock Technologies Partner Since 2022 Environmental Grantmakers Association Partner Since 2019 Highstead Partner Since 2020 John Muir Land Trust Partner Since 2022 Just Zero Partner Since 2014 Leave No Trace Partner Since 2020 Northwest Avalanche Center (NWAC) Partner Since 2023 One Tree Planted Partner Since 2021 Payette Avalanche Center Partner Since 2022 Sempervirens Partner Since 2019 Sierra Avalanche Center Partner Since 2014 The Trust For Public Land Partner Since 2022 Utah Avalanche Center Working for social and economic justice for all. Partner Since 2021 A New Way of Life Partner Since 2022 Center for Constitutional Rights Partner Since 2021 Center for WorkLife Law Partner Since 2021 Common Cause Partner Since 2010 CompassPoint Partner Since 2021 Equality Action Center Partner Since 2018 Keshet Partner Since 2024 Labor Notes Partner Since 2022 Legal Link Partner Since 2022 Mirror Memoirs Partner Since 2013 Unbound Philanthropy Partner Since 2018 Migrant Justice Building connection through arts, culture, and food. Partner Since 2013 18 Reasons Partner Since 2021 Artists Communities Alliance Partner Since 2019 Authors Alliance Partner Since 2018 Company One Theatre Partner Since 2017 Howlround Theatre Commons Partner Since 2023 Lighthouse Writers Workshop Partner Since 2023 Museo de las Americas Partner Since 2013 Sacred Lands Film Project Improving the quality and accessibility of education. Partner Since 2022 Academy College Prep Partner From 2017 To 2022 Bellwether Education Partner Since 2020 California Community Colleges Transfer Guarantee Pathway to Historically Black Colleges and Universities Partner From 2019 To 2020 The College of Business at Oregon State University Partner Since 2011 Ignited Partner From 2018 To 2022 Maker Ed Partner Since 2014 myShakespeare Partner Since 2019 Umoja Community Education Foundation Using technology for good and defending digital rights and privacy. Partner Since 2014 Electronic Frontier Foundation Partner Since 2019 FreeBSD Foundation Partner From 2015 To 2016 Internet Archive Partner Since 2012 Society of Motion Picture & Television Engineers (SMPTE) Partner From 2013 To 2021 The TOR Project Partner Since 2014 USENIX Partner Since 2020 Women's Audio Mission Partner From 2013 To 2015 Wikimedia Foundation Non-profit Sectors Human Rights Health Environment Social Justice Arts & Culture Education Technology & Privacy ❮ How can we help? Get in touch Giant Rabbit LLC 415.355.4211 info@giantrabbit.com Copyright © 2018-2025 by Giant Rabbit LLC. Artwork by RBlack . | Read our privacy policy . | 2026-01-13T09:29:33 |
https://www.ecns.cn/hd/2026-01-12/detail-iheyrzrv3843506.shtml#3 | 'Weepy horse' toy goes viral after sewing error --> 中文 Home News Ecns Wire Business Travel Photo Video Voices RIGHT BG LINE Text: A A A Print Photo 'Weepy horse' toy goes viral after sewing error ( 1 /5) 2026-01-12 14:09:33 Ecns.cn Editor :Zhao Li “Weepy horse” plush toys in various sizes are lined up at a factory in Yiwu, Zhejiang Province, Jan. 11, 2026. (Photo: China News Service/Dong Yixin) The “weepy horse”, originally intended as a smiling Year of the Horse figurine, attracted widespread attention after a consumer in Hangzhou shared her purchase online.The unusual design resulted from a worker mistakenly sewing the upturned mouth into a downward curve during production.The unexpected popularity of the defective design has led to a sharp increase in purchase orders,keeping factories working around the clock to fulfill demand. Zhang Huoqing, a merchant in Yiwu, east China’s Zhejiang Province, displays a “smiling horse” plush toy and its viral counterpart, the “weepy horse,” Jan. 11, 2026. (Photo: China News Service/Dong Yixin) Zhang Huoqing, a merchant in Yiwu, Zhejiang Province, smiles as she displays the “smiling horse” and “weepy horse” plush toys, Jan. 11, 2026. (Photo: China News Service/Dong Yixin) A buyer measures the size of a “weepy horse” plush toy in Yiwu, Zhejiang Province, Jan. 11, 2026. (Photo: China News Service/Dong Yixin) A batch of newly produced “weepy horse” plush toy samples is seen at a workshop in Yiwu, Zhejiang Province, Jan. 11, 2026. (Photo: China News Service/Dong Yixin) Previous The “weepy horse”, originally intended as a smiling Year of the Horse figurine, attracted widespread attention after a consumer in Hangzhou shared her purchase online.The unusual design resulted from a worker mistakenly sewing the upturned mouth into a downward curve during production.The unexpected popularity of the defective design has led to a sharp increase in purchase orders,keeping factories working around the clock to fulfill demand.--> Next (1) (2) (3) (4) (5) LINE More Photo New giant panda pair makes public debut in Malaysia Exploring world's largest island Greenland Venezuelan people call on U.S. to release Nicolás Maduro and his wife Heavey snow hits Paris 'Southern Snow Town' draws tourists to Guizhou Province Global mayors attend dialogue in NE China on developing ice, snow economy ${visuals_2} ${visuals_3} More Video Comicomment: No country has the right to act as the world's police What's it like doing business in China? Check what foreign friends say More than a business hub: check how global merchants thrive in Yiwu Insights | Sanae Takaichi's erroneous remarks a grave 'diplomatic failure': Japanese scholar Insights丨From energy cooperation to industrial co-building: New momentum in Europe-China ties Insights丨China’s economy in UN official’s eyes: Resilience, exports, and high-tech transition ${new_video_hd2} ${new_video_hd3} LINE Media partners: People's Daily | Xinhua | CGTN | China Daily Back to top About Us | Jobs | Contact Us | Privacy Policy Copyright ©1999-2026 Chinanews.com. All rights reserved. Reproduction in whole or in part without permission is prohibited. [ 网上传播视听节目许可证（0106168) ] [ 京ICP证040655号 ] [ 京公网安备 11010202009201号 ] [ 京ICP备05004340号-1 ] --> --> | 2026-01-13T09:29: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 |
https://www.chinadaily.com.cn/a/202507/08/WS686cce27a31000e9a573acf4.html | From smart Tianjin Port to SCO story - 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 / Videos Home / World / Videos From smart Tianjin Port to SCO story By Xia Ji | chinadaily.com.cn | Updated: 2025-07-08 15:52 Share Share - WeChat --> CLOSE Anton Butov, a Russian actor, internet influencer, and foreign trader living in Qingdao, East China's Shandong province, joined the "Global Mayors Dialogue • SCO Summit Cities" event in North China's Tianjin on July 8. During a tour of Tianjin Port ahead of the event, he shared insights on trade and cultural ties among SCO countries with China Daily's Xia Ji, who is also from Qingdao. Discover how personal stories like Anton's reflect the SCO's vision. --> --> --> Photos 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 Texas floods raise doubts over US weather warnings 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://pix.webm.ink/site/kb/sharing-media#collapse13 | 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 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3Anumber | 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/202601/09/WS6960b868a310d6866eb32efd.html | 450-ton freight train brings Gansu seeds to Europe 中文 | Contact Us | search close Search nav close Home Charming Gansu + Overview Gansu & Silk Road Gallery Media Center + News Specials Business + Why Gansu Industries Policies Guide Industrial Parks Enterprises Visiting + Attractions Routes Heritage Transportation Dining Accommodation Shopping Leisure Life + Visas Health Care Education Marriage and Adoption Tips Contact Us 中文 Home > News 1153730 2026-01-08 17:43:56.0 By Hu Yumeng and Ma Jingna 450-ton freight train brings Gansu seeds to Europe 48 21999 News 2@gansuen /enpproperty--> 450-ton freight train brings Gansu seeds to Europe By Hu Yumeng and Ma Jingna | chinadaily.com.cn | Updated: 2026-01-08 On Dec 24, a freight train carrying seeds departs from Jiuquan for Italy via the new western land-sea corridor rail-sea linkage. [Photo provided to chinadaily.com.cn] 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. The train left the Jiuquan railway logistics hub on Dec 24, transporting 24 containers of vegetables and flower seeds bound for Italy and the Netherlands via China's western land-sea corridor. Officials said the corridor shortens transport time and reduces costs compared with traditional routes, boosting the competitiveness of Chinese seed exports and supporting agricultural cooperation with countries involved with the Belt and Road Initiative. 1 2 3 > Specials The Hexi Corridor: A legendary passage Gansu & Silk Road > Dunhuang is not just an ancient oasis in an arid land, but a spring of love for my family. View all stories Links > The State Council Jiuquan, Gansu Lanzhou, Gansu Qilihe district, Lanzhou Silk Road (Dunhuang) International Cultural Expo Zhangye, Gansu Charming Gansu Overview Gansu & Silk Road Gallery Media Center News Specials Business Why Gansu Industries Policies Guide Industrial Parks Enterprises Visiting Attractions Routes Heritage Transportation Dining Accommodation Shopping Leisure Life Visas Health Care Education Marriage & Adoption Tips Copyright © The Information Office of Gansu Provincial People's Government. All rights reserved. Presented by China Daily. 陇ICP备2020003841号-4 top | 2026-01-13T09:29:33 |
https://www.ecns.cn/hd/2026-01-12/detail-iheyrzrv3843506.shtml#4 | 'Weepy horse' toy goes viral after sewing error --> 中文 Home News Ecns Wire Business Travel Photo Video Voices RIGHT BG LINE Text: A A A Print Photo 'Weepy horse' toy goes viral after sewing error ( 1 /5) 2026-01-12 14:09:33 Ecns.cn Editor :Zhao Li “Weepy horse” plush toys in various sizes are lined up at a factory in Yiwu, Zhejiang Province, Jan. 11, 2026. (Photo: China News Service/Dong Yixin) The “weepy horse”, originally intended as a smiling Year of the Horse figurine, attracted widespread attention after a consumer in Hangzhou shared her purchase online.The unusual design resulted from a worker mistakenly sewing the upturned mouth into a downward curve during production.The unexpected popularity of the defective design has led to a sharp increase in purchase orders,keeping factories working around the clock to fulfill demand. Zhang Huoqing, a merchant in Yiwu, east China’s Zhejiang Province, displays a “smiling horse” plush toy and its viral counterpart, the “weepy horse,” Jan. 11, 2026. (Photo: China News Service/Dong Yixin) Zhang Huoqing, a merchant in Yiwu, Zhejiang Province, smiles as she displays the “smiling horse” and “weepy horse” plush toys, Jan. 11, 2026. (Photo: China News Service/Dong Yixin) A buyer measures the size of a “weepy horse” plush toy in Yiwu, Zhejiang Province, Jan. 11, 2026. (Photo: China News Service/Dong Yixin) A batch of newly produced “weepy horse” plush toy samples is seen at a workshop in Yiwu, Zhejiang Province, Jan. 11, 2026. (Photo: China News Service/Dong Yixin) Previous The “weepy horse”, originally intended as a smiling Year of the Horse figurine, attracted widespread attention after a consumer in Hangzhou shared her purchase online.The unusual design resulted from a worker mistakenly sewing the upturned mouth into a downward curve during production.The unexpected popularity of the defective design has led to a sharp increase in purchase orders,keeping factories working around the clock to fulfill demand.--> Next (1) (2) (3) (4) (5) LINE More Photo New giant panda pair makes public debut in Malaysia Exploring world's largest island Greenland Venezuelan people call on U.S. to release Nicolás Maduro and his wife Heavey snow hits Paris 'Southern Snow Town' draws tourists to Guizhou Province Global mayors attend dialogue in NE China on developing ice, snow economy ${visuals_2} ${visuals_3} More Video Comicomment: No country has the right to act as the world's police What's it like doing business in China? Check what foreign friends say More than a business hub: check how global merchants thrive in Yiwu Insights | Sanae Takaichi's erroneous remarks a grave 'diplomatic failure': Japanese scholar Insights丨From energy cooperation to industrial co-building: New momentum in Europe-China ties Insights丨China’s economy in UN official’s eyes: Resilience, exports, and high-tech transition ${new_video_hd2} ${new_video_hd3} LINE Media partners: People's Daily | Xinhua | CGTN | China Daily Back to top About Us | Jobs | Contact Us | Privacy Policy Copyright ©1999-2026 Chinanews.com. All rights reserved. Reproduction in whole or in part without permission is prohibited. [ 网上传播视听节目许可证（0106168) ] [ 京ICP证040655号 ] [ 京公网安备 11010202009201号 ] [ 京ICP备05004340号-1 ] --> --> | 2026-01-13T09:29:33 |
https://www.chinadaily.com.cn/a/202601/13/WS6965c95ba310d6866eb336ba.html | Japanese PM intends to dissolve lower house for snap election: Kyodo - World - 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 / Asia-Pacific Home / World / Asia-Pacific Japanese PM intends to dissolve lower house for snap election: Kyodo Xinhua | Updated: 2026-01-13 12:25 Share Share - WeChat --> CLOSE TOKYO - Japanese Prime Minister Sanae Takaichi told a senior ruling Liberal Democratic Party (LDP) official that she intends to dissolve the House of Representatives when its regular Diet session convenes on Jan 23 and call a snap election, Kyodo News reported on Tuesday, citing a source familiar with the matter. The report said the prime minister is poised to make an official announcement soon. If the lower house is dissolved, there are two possible schedules for a snap election: one with official campaigning starting on Jan 27 and voting on Feb 8, and another with campaigning beginning on Feb 3 and voting on Feb 15. Public support for the Takaichi cabinet has remained at a relatively high level in recent opinion polls conducted by major media outlets, fueling calls within the LDP for an early dissolution and general election, the report said. Since taking office, Takaichi has repeatedly stressed that livelihood-related issues, including measures to cope with high prices, should be given top priority. However, if the lower house is dissolved at the outset of the ordinary Diet session, passage of the fiscal 2026 budget could be delayed until April or later, many Japanese media outlets warned. In that case, the government may be forced to compile a provisional budget to maintain fiscal operations, a move expected to have a significant impact on people's livelihoods. Takaichi's decision has drawn sustained criticism from within the LDP and from opposition parties, who argue that she has gone back on her earlier pledges and prioritized party interests over those of the public. --> Photos Chinese EV makers steer global auto innovation US foreign policy shift threatens global order, stability: Experts Europe's farmers march against EU's deal with South American trade bloc Unrest under total control, claims Iran Hamas signals readiness to hand over Gaza governance EU commissioner reaffirms Greenland security, warning US takeover would end NATO 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 --> 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://pix.webm.ink/site/kb/getting-started#collapse2 | 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://pix.webm.ink/site/kb/sharing-media#collapse3 | 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 |
https://issues.jenkins.io/secure/EditLabels!default.jspa?id={0}&returnUrl=/secure/issues#sidebar | Error - 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 Error The issue no longer exists. 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://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://pix.webm.ink/site/kb/sharing-media#collapse14 | 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 |
https://www.ecns.cn/video/2026-01-07/detail-iheyrzrv3837338.shtml | Comicomment: Save or Slave? Hegemony at play --> 中文 Home News Ecns Wire Business Travel Photo Video Voices RIGHT BG LINE Text: A A A Print Video Comicomment: Save or Slave? Hegemony at play 2026-01-07 13:01:22 Ecns.cn Editor : Chen Shankun ECNS App Download Cloaked in the rhetoric of “rescue” and “responsibility,” the use of force reflects a familiar pattern of dominance. The U.S. military action has drawn concern far beyond the region, leading governments worldwide to question both its legality and the path it signals for global governance. Even more alarming is the precedent it sets: when force replaces authority, sovereignty becomes conditional, international law is sidelined, and the stability of the global order is put at risk. 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 Lithium-ion battery experiment conducted aboard Chinese space station Subsidies aid cross-Strait integration Chinese FM warns int'l community of Japan's accelerating remilitarization trend Global mayors attend dialogue in NE China on developing ice, snow economy Indonesia welcomes its first locally born giant panda cub 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://issues.jenkins.io/login.jsp?os_destination=%2Fsecure%2Fcredits%2FAroundTheWorld%21default.jspa | Log into Atlassian - Jenkins Jira Log in Skip to main content Skip to sidebar Dashboards Projects Issues Give feedback to Atlassian Help Keyboard Shortcuts About Jira Jira Credits Log In 📢 Jenkins core issues have been migrated to GitHub , no new core issues can be created in Jira Atlassian Jira Project Management Software About Jira Report a problem Powered by a free Atlassian Jira open source license for The Linux Foundation. Try Jira - bug tracking software for your team. Atlassian | 2026-01-13T09:29:33 |
https://www.tumblr.com/support?language=de_DE | Hilfecenter | Tumblr Einloggen Registrieren © Tumblr, Inc. Hilfe Über Tumblr Apps Entwickler Templates Jobs Rechtliches Allgemeine Geschäftsbedingungen Urheberrecht Datenschutz 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://reports.jenkins.io/jelly-taglib-ref.html#form.3ApossibleReadOnlyField | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:33 |
http://groovy-lang.org/syntax.html#_special_cases | 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://www.chinadaily.com.cn/world/world-in-photos | World in Focus - 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 Home / World / World in Focus Home / World / World in Focus Clean energy push Heart for art Cultural restoration Model lessons Clean energy push Heart for art Cultural restoration Model lessons On right track Harsh reality Engulfed by water ICE in hot water The big catch Fruitful friendship Poetry in motion A sanctuary of hope Seeds of friendship Getting a kick Nurturing nature Fruitful outcomes Sound of hope Showcasing heritage Tariff jolt 1 2 3 4 5 6 7 8 9 10 Next >>| 1/31 Next 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://issues.jenkins.io/secure/credits/AroundTheWorld!default.jspa#sidebar | 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://issues.jenkins.io/secure/MyJiraHome.jspa#sidebar | 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 System Dashboard Tools View as wallboard To move an item, select with Space and move with Ctrl/Cmd + Arrow keys 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.chinadaily.com.cn/china/211flash | China Photos - 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 Home / China / China Photos Home / China / China Photos Local farmers combat desertification in Moyu county of Xinjiang China tips scales toward healthier living trends Guangzhou's bald cypress trees turn red after cold snap University of Macao celebrates 45th anniversary Local farmers combat desertification in Moyu county of Xinjiang China tips scales toward healthier living trends Guangzhou's bald cypress trees turn red after cold snap University of Macao celebrates 45th anniversary Night view of Central Street in Harbin N China's Hohhot launches winter amusement programs to boost local economy Cornell students explore China's agricultural development Salute to everyday heroes Hunan students craft opera headpieces from recycled materials Xizang nursing home celebrates seniors on quake anniversary Century-old tunnel named after Taiwan's first governor reopens, revives historical memories Ten photos from across China: Jan 2 - 8 Chongqing's air-raid shelter-turned-bookstore becomes tourism touchstone Tsakhor village prepares for Losar New Year Global mayors learn to carve ice in Harbin Bringing care from afar Cold front coats Guizhou mountains in rime Tianmen grand bridge under construction in Guizhou International mayors attend ice and snow expo in Harbin 1 2 3 4 5 6 7 8 9 10 Next >>| 1/661 Next 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/world/special_coverage/68f1f858a310f735438b59db | Multi-lingual 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 / Multi-lingual News Home / World / Multi-lingual News 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://www.chinadaily.com.cn/world/special_coverage/6853d7e3a310a04af22c74c2 | SCO in Focus - 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 / SCO in Focus Home / World / SCO in Focus China's experience using tech for urban growth draws adulation 2025-07-09 09:24 Smart cities key to driving SCO's intl influence 2025-07-09 09:08 'Shanghai Spirit' reflects strength and resilience 2025-07-09 06:38 Smart SCO cities to intelligent urbanization 2025-07-08 06:51 2025 Media Cooperation Forum of SCO Countries held in Xinjiang 2025-05-24 10:40 Survey: Strong cohesion among SCO members 2025-05-24 08:13 Forum seeks to address global issue of poverty 2025-05-21 07:06 SCO forum on digital economy set for Tianjin 2025-05-20 19:24 SCO forum on poverty reduction, sustainable development opens 2025-05-20 15:24 China hosts SCO's trade union meeting 2025-05-16 09:27 SCO meeting pushes for shared goals 2025-05-14 09:13 Global experts pledge medical innovation ties 2025-04-30 09:18 SCO member countries urged to advance vital health sector 2025-04-30 09:02 Meeting participants in awe of TCM's potential 2025-04-30 08:56 SCO calls for stronger cooperation in TCM 2025-04-29 17:04 Chinese vice-premier calls on SCO to ramp-up cooperation 2025-04-29 14:16 SCO delegates marvel at modernization momentum of China's Xinjiang 2025-04-29 11:05 SCO meeting calls on political parties to jointly address global challenges 2025-04-25 21:47 Forum calls for political cooperation, solidarity 2025-04-25 09:47 CPC ready to work with SCO political parties, organizations on a new security framework 2025-04-24 15:24 1 2 Next >>| 1/2 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://www.ecns.cn/hd/2026-01-12/detail-iheyrzrv3843506.shtml#5 | 'Weepy horse' toy goes viral after sewing error --> 中文 Home News Ecns Wire Business Travel Photo Video Voices RIGHT BG LINE Text: A A A Print Photo 'Weepy horse' toy goes viral after sewing error ( 1 /5) 2026-01-12 14:09:33 Ecns.cn Editor :Zhao Li “Weepy horse” plush toys in various sizes are lined up at a factory in Yiwu, Zhejiang Province, Jan. 11, 2026. (Photo: China News Service/Dong Yixin) The “weepy horse”, originally intended as a smiling Year of the Horse figurine, attracted widespread attention after a consumer in Hangzhou shared her purchase online.The unusual design resulted from a worker mistakenly sewing the upturned mouth into a downward curve during production.The unexpected popularity of the defective design has led to a sharp increase in purchase orders,keeping factories working around the clock to fulfill demand. Zhang Huoqing, a merchant in Yiwu, east China’s Zhejiang Province, displays a “smiling horse” plush toy and its viral counterpart, the “weepy horse,” Jan. 11, 2026. (Photo: China News Service/Dong Yixin) Zhang Huoqing, a merchant in Yiwu, Zhejiang Province, smiles as she displays the “smiling horse” and “weepy horse” plush toys, Jan. 11, 2026. (Photo: China News Service/Dong Yixin) A buyer measures the size of a “weepy horse” plush toy in Yiwu, Zhejiang Province, Jan. 11, 2026. (Photo: China News Service/Dong Yixin) A batch of newly produced “weepy horse” plush toy samples is seen at a workshop in Yiwu, Zhejiang Province, Jan. 11, 2026. (Photo: China News Service/Dong Yixin) Previous The “weepy horse”, originally intended as a smiling Year of the Horse figurine, attracted widespread attention after a consumer in Hangzhou shared her purchase online.The unusual design resulted from a worker mistakenly sewing the upturned mouth into a downward curve during production.The unexpected popularity of the defective design has led to a sharp increase in purchase orders,keeping factories working around the clock to fulfill demand.--> Next (1) (2) (3) (4) (5) LINE More Photo New giant panda pair makes public debut in Malaysia Exploring world's largest island Greenland Venezuelan people call on U.S. to release Nicolás Maduro and his wife Heavey snow hits Paris 'Southern Snow Town' draws tourists to Guizhou Province Global mayors attend dialogue in NE China on developing ice, snow economy ${visuals_2} ${visuals_3} More Video Comicomment: No country has the right to act as the world's police What's it like doing business in China? Check what foreign friends say More than a business hub: check how global merchants thrive in Yiwu Insights | Sanae Takaichi's erroneous remarks a grave 'diplomatic failure': Japanese scholar Insights丨From energy cooperation to industrial co-building: New momentum in Europe-China ties Insights丨China’s economy in UN official’s eyes: Resilience, exports, and high-tech transition ${new_video_hd2} ${new_video_hd3} LINE Media partners: People's Daily | Xinhua | CGTN | China Daily Back to top About Us | Jobs | Contact Us | Privacy Policy Copyright ©1999-2026 Chinanews.com. All rights reserved. Reproduction in whole or in part without permission is prohibited. [ 网上传播视听节目许可证（0106168) ] [ 京ICP证040655号 ] [ 京公网安备 11010202009201号 ] [ 京ICP备05004340号-1 ] --> --> | 2026-01-13T09:29:33 |
https://issues.jenkins.io/secure/ConvertSubTask.jspa?id={0}&returnUrl=/secure/issues#sidebar | Convert Sub-task to Issue: - 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 Errors Invalid issue id. Return to Dashboard 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.chinadaily.com.cn/china/59b8d010a3108c54ed7dfc27 | Health - 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 China News Society Innovation HK/Macao Cross-Strait Cover Story Photo Environment Health Military Video Home / China / Health Home China Health Smart tech to unify healthcare and insurance data 2026-01-13 09:09 AI platform enables million-fold increase in drug screening speed 2026-01-12 08:52 Pediatric care cover expanded nationwide 2026-01-12 07:38 China makes it easier for families to tap employee healthcare insurance funds 2026-01-09 15:38 Novel pay systems to aid medical access 2026-01-09 09:16 Study shows more kids in China surviving cancer 2026-01-09 08:50 China CDC urges precaution amid surge in rhinovirus cases 2026-01-08 20:50 Bringing care from afar 2026-01-08 09:01 China set to establish early pregnancy clinics across 10k hospitals 2026-01-07 17:36 Non-invasive sound therapy boosts hope for Alzheimer's treatment 2026-01-07 16:36 China's health literacy rates trend upward, according to new data 2026-01-07 16:15 NHC unveils 4th catalog of branded drugs to boost generic alternatives 2026-01-05 16:30 Shanghai researchers develop breakthrough breast cancer therapy 2026-01-05 14:48 Sycume thyroid meds added to national drug reimbursement list 2026-01-05 14:24 Action plan targets youth health issues 2026-01-05 09:11 China sees continued improvement in women's health in 2024: statistical report 2025-12-31 11:28 More Chinese cities add artificial hearts to medical insurance coverage 2025-12-31 10:52 China records continued improvement in child health in 2024 2025-12-31 10:48 China launches action plan on children's health 2025-12-30 18:02 China rolls out plan to boost health of children, youth through 2030 2025-12-30 15:39 1 2 3 4 5 6 7 8 9 10 Next >>| 1/366 Next --> Latest China launches new AI model for agriculture China introduces national standard for valuing terrestrial ecosystems Government agencies announce regulations of online hiring information Ministry pledges to continue solid waste disposal crackdown Shandong upgrades ancient canal shipping with smart tech and cleaner ships Night view of Central Street in Harbin Exclusive Salute to everyday heroes A tech pro's lens on AI development Chinese AI company to showcase the warmth of technology at US exhibition Newsmaker Chinese couple turns 100,000 photos of Great Wall into a museum Beating the drum of heritage preservation Ten photos you don't wanna miss Ten photos from across China: Jan 2 - 8 Special Coverage Live: Hong Kong residential area fire 4th Plenary Session of the 20th CPC Central Committee From Qiushi Boosting High-Quality Belt and Road Cooperation Through Rigorous and Sustained Efforts China’s Hydropower: Empowering a Clean and Beautiful 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 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.ecns.cn/video/2026-01-12/detail-iheywhna5918970.shtml | Comicomment: Wings clipped, Latin America left to suffer --> 中文 Home News Ecns Wire Business Travel Photo Video Voices RIGHT BG LINE Text: A A A Print Video Comicomment: Wings clipped, Latin America left to suffer 2026-01-12 17:14:42 Ecns.cn Editor : Meng Xiangjun ECNS App Download As a left-leaning country, Venezuela has maintained an anti-U.S. stance from Chávez to Maduro, making it a constant target of Washington. In recent years, the United States has intensified pressure through aid cuts, tariffs and sanctions, seeking to reassert regional dominance. The latest military action is simply an escalation of unilateralism and power politics. By replaying old interventionist tactics, the U.S. has repeatedly hindered Latin America’s development, only deepening its own hegemonic dilemma. Its expansionist dream will ultimately be broken by regional resistance and global condemnation. More Photo 'Weepy horse' toy goes viral after sewing error New giant panda pair makes public debut in Malaysia Exploring world's largest island Greenland Venezuelan people call on U.S. to release Nicolás Maduro and his wife Heavey snow hits Paris 'Southern Snow Town' draws tourists to Guizhou Province Global mayors attend dialogue in NE China on developing ice, snow economy 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 Most popular in 24h More Top news China rebukes Trump's remarks on Greenland, stresses peaceful arctic role Paid app 'Dead Yet?' goes viral amid rising fees J-10CE fighter achieved first verified combat success: Chinese authorities Hainan posts $170 million in duty-free sales in first seven days of 2026 Hainan steps up efforts to attract investment and boost consumption after customs operation launch More Video A surreal start of 2026: When one president seizes another, next target — Greenland Comicomment: No country has the right to act as the world's police 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/hd/2026-01-13/detail-iheywhna5920684.shtml#1 | South Korea's ex-President Yoon Suk Yeol faces sentencing in insurrection trial --> 中文 Home News Ecns Wire Business Travel Photo Video Voices RIGHT BG LINE Text: A A A Print Photo South Korea's ex-President Yoon Suk Yeol faces sentencing in insurrection trial ( 1 /2) 2026-01-13 11:29:09 Ecns.cn Editor :Gong Weiwei A blue bus carrying South Korea's former President Yoon Suk Yeol arrives at the Seoul Central District Court on Jan. 13, 2026. (Photo provided to China News Service) Tuesday's hearing will conclude the legal proceedings against former President Yoon Suk Yeol, who faces criminal charges for imposing martial law late in the evening of Dec. 3, 2024. He stands accused of abusing his power and leading an insurrection. A blue bus carrying South Korea's former President Yoon Suk Yeol arrives at the Seoul Central District Court on Jan. 13, 2026. (Photo provided to China News Service) Previous Tuesday's hearing will conclude the legal proceedings against former President Yoon Suk Yeol, who faces criminal charges for imposing martial law late in the evening of Dec. 3, 2024. He stands accused of abusing his power and leading an insurrection.--> Next (1) (2) LINE More Photo 'Weepy horse' toy goes viral after sewing error New giant panda pair makes public debut in Malaysia Exploring world's largest island Greenland Venezuelan people call on U.S. to release Nicolás Maduro and his wife Heavey snow hits Paris 'Southern Snow Town' draws tourists to Guizhou Province ${visuals_2} ${visuals_3} More Video Comicomment: Wings clipped, Latin America left to suffer A surreal start of 2026: When one president seizes another, next target — Greenland Comicomment: No country has the right to act as the world's police What's it like doing business in China? Check what foreign friends say More than a business hub: check how global merchants thrive in Yiwu Comicomment: Save or Slave? Hegemony at play ${new_video_hd2} ${new_video_hd3} LINE Media partners: People's Daily | Xinhua | CGTN | China Daily Back to top About Us | Jobs | Contact Us | Privacy Policy Copyright ©1999-2026 Chinanews.com. All rights reserved. Reproduction in whole or in part without permission is prohibited. [ 网上传播视听节目许可证（0106168) ] [ 京ICP证040655号 ] [ 京公网安备 11010202009201号 ] [ 京ICP备05004340号-1 ] --> --> | 2026-01-13T09:29:33 |
https://www.ecns.cn/hd/2026-01-08/detail-iheyrzrv3839187.shtml | 'Southern Snow Town' draws tourists to Guizhou Province --> 中文 Home News Ecns Wire Business Travel Photo Video Voices RIGHT BG LINE Text: A A A Print Photo 'Southern Snow Town' draws tourists to Guizhou Province ( 1 /4) 2026-01-08 13:33:36 Ecns.cn Editor :Gong Weiwei Visitors enjoy themselves at the "Southern Snow Town" project in Liupanshui City, southwest China's Guizhou Province, Jan. 7, 2026. Leveraging the core strengths of the Meihuashan Ski Resort, the project aims to bring an authentic snow-town experience to tourists, creating an immersive cultural and tourism experience. (Photo: China News Service/Qu Honglun) Visitors enjoy themselves at the "Southern Snow Town" project in Liupanshui City, southwest China's Guizhou Province, Jan. 7, 2026. Leveraging the core strengths of the Meihuashan Ski Resort, the project aims to bring an authentic snow-town experience to tourists, creating an immersive cultural and tourism experience. (Photo: China News Service/Qu Honglun) Visitors enjoy themselves at the "Southern Snow Town" project in Liupanshui City, southwest China's Guizhou Province, Jan. 7, 2026. Leveraging the core strengths of the Meihuashan Ski Resort, the project aims to bring an authentic snow-town experience to tourists, creating an immersive cultural and tourism experience. (Photo: China News Service/Qu Honglun) Visitors enjoy themselves at the "Southern Snow Town" project in Liupanshui City, southwest China's Guizhou Province, Jan. 7, 2026. Leveraging the core strengths of the Meihuashan Ski Resort, the project aims to bring an authentic snow-town experience to tourists, creating an immersive cultural and tourism experience. (Photo: China News Service/Qu Honglun) Previous Next (1) (2) (3) (4) LINE 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 ${visuals_2} ${visuals_3} More Video More than a business hub: check how global merchants thrive in Yiwu Insights | Sanae Takaichi's erroneous remarks a grave 'diplomatic failure': Japanese scholar Insights丨From energy cooperation to industrial co-building: New momentum in Europe-China ties Insights丨China’s economy in UN official’s eyes: Resilience, exports, and high-tech transition 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 ${new_video_hd2} ${new_video_hd3} LINE Media partners: People's Daily | Xinhua | CGTN | China Daily Back to top About Us | Jobs | Contact Us | Privacy Policy Copyright ©1999-2026 Chinanews.com. All rights reserved. Reproduction in whole or in part without permission is prohibited. [ 网上传播视听节目许可证（0106168) ] [ 京ICP证040655号 ] [ 京公网安备 11010202009201号 ] [ 京ICP备05004340号-1 ] --> --> | 2026-01-13T09:29:33 |
http://www.chinadaily.com.cn/a/202508/22/WS68a7faa5a310851ffdb4f8fa.html | Shared wartime history unites nations - World - 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 / Americas Home / World / Americas Shared wartime history unites nations By Zhao Huanxin in Washington | chinadaily.com.cn | Updated: 2025-08-22 13:05 Share Share - WeChat --> CLOSE Chinese Ambassador to the US Xie Feng talks with a guest at the Chinese embassy in Washington on Wednesday at an art exhibition marking the 80th anniversary of the victory in the Chinese People's War of Resistance Against Japanese Aggression and the World Anti-Fascist War. [Photo by Zhao Huanxin/chinadaily.com.cn] Eighty years after China and the United States fought side by side in World War II, Beijing's top envoy in Washington said that the two countries must draw on their shared wartime history and recommit to peaceful coexistence and practical cooperation. Ambassador Xie Feng delivered the message on Wednesday at an art exhibition at the Chinese embassy marking the 80th anniversary of victory in the Chinese People's War of Resistance Against Japanese Aggression (1931-45) and the World Anti-Fascist War. Xie hailed the "heroes" who resisted fascism, from Chinese civilians to foreign volunteers, and recalled how, during what he described as a "decisive war between justice and evil," China and more than 50 nations formed an international anti-fascist front. "The Flying Tigers soared across the sky to intercept Japanese aggressors, and opened up the treacherous 'Hump Route' over the Roof of the World, writing an epic story in pursuit of peace with their lives," he said. In 1941, volunteer US pilots, known as the Flying Tigers, fought alongside the Chinese against the Japanese in China. The ambassador praised foreign artists and journalists, including US illustrator Martha Sawyers and photographer Robert Capa, for rallying support for China during the war. "Today, to safeguard the post-war international order and protect the Earth, our only home, we still need such heroes, and should act together for peace and for the future," he said. Xie also pointed to the Doolittle Raid of 1942, when US pilots, running low on fuel after completing their attack on Japan, crash-landed in China. "Chinese soldiers and civilians spared no effort to rescue the pilots they had never met before," he said, noting that some 250,000 Chinese civilians were killed in Japanese retaliation. That wartime experience left a lasting imprint on bilateral ties. "The friendship between the Chinese and American people was forged amid the trials of blood and fire," Xie said, "and has gained new life and injected fresh impetus into bilateral relations over the years." "It is a constant reminder that China and the US should see each other as a partner and friend, contribute to one another's success and benefit the whole world; that we should never forget what our two peoples went through together in the era of war, and should never waver in our commitment to peaceful coexistence and win-win cooperation," he added. The envoy's message was as much about today as yesterday. The lesson of history, he noted, is that "prejudice, hatred and war will bring nothing but disaster and pain," while cooperation offers the only path forward. "Eight decades ago, our two countries fought against fascism side by side and jointly defended peace and justice. Eight decades later, we have more extensive common interests, broader space for cooperation, and more important international obligations," he said. As the world's two largest economies and as permanent members of the United Nations Security Council, China and the US share a special and significant responsibility for upholding world peace and stability, and promoting global development and prosperity, Xie said. The two global powers with vast common interests should coexist peacefully and "get more good things done," he added. Jeffrey Green, chairman of the US-China Aviation Heritage Foundation, also emphasized the importance of remembering the wartime bond. Echoing Xie, Green described the sacrifices made by ordinary Chinese in aiding downed US pilots. "Families risked their lives to hide airmen, dress their wounds and guide them to safety," he said. "Never has one nation's people so consistently risked so much for those of another. This was not merely an alliance. It was humanity at its purest form." Green noted that the story of the Flying Tigers and the Chinese people's shared struggle and sacrifice is more than a bridge between China and the United States, but "a timeless testament to the power of solidarity". "May this legacy continue to inspire all of us to look beyond borders, to cherish our shared humanity and to walk together toward a future of mutual respect and lasting peace and a common destiny," he said. David Frazer, a professor at the Rhode Island School of Design, stressed the role of culture in bridging divides today. "Despite the political differences that exist today between our great countries, global appreciation for the arts transcends these differences," he said. Frazer called art a "diplomatic tool that promises hope for the future with peace and prosperity for all our people." He called for the legacy of solidarity to continue. "I'm sure that everyone here this evening hopes that our futures promise, dearly, truly … that our two countries will live in peaceful coexistence and will prosper together in healthy economic competition with friendship and, most importantly, respect," he said. More than 200 guests, including US dignitaries, attended the commemorative exhibition, jointly organized with State broadcaster China Central Television. huanxinzhao@chinadailyusa.com --> Photos World rings in 2026 with fireworks Concerns voiced over situation in Gaza Trump confirms US struck port facility in Venezuela Opening up New Horizons for Major-Country Diplomacy with Chinese Characteristics at a Crucial Historical Juncture Ukraine tried to attack Putin's home: Russia Continents' rhythms out of sync in 2025 Most Viewed in 24 Hours World in Focus Heart for art 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 --> 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://www.chinadaily.com.cn/a/202601/08/WS695f0814a310d6866eb329ac.html | China defends curbs on dual-use goods exports - World - 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 / Asia-Pacific Home / World / Asia-Pacific China defends curbs on dual-use goods exports Restrictions could deal heavy blow to key Japanese industries, experts say By HOU JUNJIE in Tokyo and ZHOU JIN in Beijing | China Daily | Updated: 2026-01-08 09:27 Share Share - WeChat --> CLOSE Sanae Takaichi, Japan's prime minister, leaves after a press conference at the prime minister's office in Tokyo, Japan Dec 17, 2025. [Photo/Agencies] China's Foreign Ministry defended its right to take measures to ban exports of dual-use goods on Japan, which experts believe will deal a heavy blow to key Japanese industries. It is completely legitimate and reasonable for China to take measures to ban exports of dual-use goods that can serve military purposes to Japan, the ministry's spokeswoman Mao Ning said on Wednesday. Mao stressed that Japanese Prime Minister Sanae Takaichi's erroneous remarks on China's Taiwan infringed on the country's sovereignty and territorial integrity, blatantly interfered in its internal affairs, and sent a military threat against China. During a parliament session in early November, Takaichi said that a "Taiwan contingency" could trigger a "survival-threatening situation" for Japan, implying military intervention in the Taiwan Strait. The Japanese Ministry of Foreign Affairs protested against China's latest measure, but Mao urged Japan to face up to the root of the issue, reflect upon and correct its wrongdoing, and retract Takaichi's erroneous remarks. China's Ministry of Commerce announced on Tuesday that Beijing has decided to strengthen export controls on dual-use items to Japan, effective from Tuesday, to safeguard national security interests and fulfill international nonproliferation obligations. "China prohibits the export of all dual-use items to Japanese military users, for Japan's military use, and for any other end-users and end-use purposes that help enhance Japan's military capabilities," the ministry said. Dual-use items refer to those that can be used for both civilian and military applications. Should rare earth elements be included in the restrictions, the potential impact on the Japanese economy could be even more significant, experts warned. Broader economic fallout Japanese economists have expressed concern over the broader economic fallout. Hidetoshi Tashiro, chief economist at Japan's Infinity LLC and CEO of Terra Nexus Project Management Services, said that due to a lack of a clear definition of dual-use goods to be exported to Japan, it is hard to know the exact scope of the controls." As a result, it is difficult to determine which products are subject to restrictions, discouraging firms from placing or accepting orders," he said, adding that the ban could lead to an overall contraction in trade. According to estimates by Takahide Kiuchi, executive economist at Nomura Research Institute, the dual-use items could cover semiconductors and electronic components, precision machinery, EV-related lithium compounds and rare earths, telecommunications equipment, and personal computers. Japanese trade figures show that in 2024, imports from China of electrical machinery and telecommunications equipment totaled 7.7 trillion yen ($49.2 billion), while personal computers and peripherals accounted for 2.4 trillion yen, precision optical instruments 0.4 trillion yen, and rare earths 0.2 trillion yen. Together, these imports amounted to about 10.7 trillion yen, representing roughly 42 percent of Japan's total imports from China that year. China is also considering tightening export permit reviews for certain rare earth-related items to Japan, a source familiar with the matter told China Daily on Tuesday. Tashiro noted that Japan's automotive industry could be forced to significantly cut production or even halt operations if rare earth supplies are disrupted. The impact would quickly spread to a wide range of parts manufacturers. Tashiro said the broader electronics industry would face similar challenges, especially the semiconductor manufacturing equipment sector. Nomura Research Institute estimates that if China's restrictions on rare earth exports to Japan were to last three months, Japan could suffer losses of about 660 billion yen, with both nominal and real GDP reduced by an annualized 0.11 percent. If the restrictions were extended to one year, losses could reach approximately 2.6 trillion yen, dragging down the GDP by 0.43 percent. Tashiro warned that prolonged or expanded export controls would significantly increase unpredictability in trade. Tokyo stocks ended lower on Wednesday, with the benchmark Nikkei stock index closing down 1.06 percent from Tuesday. --> Photos Highs and lows mark China-US ties in 2025 Europe airs concern over territorial ambitions Thousands protest in London against strikes Maduro pleads not guilty in US court Visa-free policy boosts China-ROK ties Venezuela move draws condemnation Most Viewed in 24 Hours World in Focus Heart for art 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 --> 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://issues.jenkins.io/login.jsp?os_destination=%2Fissues%2F | Log into Atlassian - Jenkins Jira Log in Skip to main content Skip to sidebar Dashboards Projects Issues Give feedback to Atlassian Help Keyboard Shortcuts About Jira Jira Credits Log In 📢 Jenkins core issues have been migrated to GitHub , no new core issues can be created in Jira Atlassian Jira Project Management Software About Jira Report a problem Powered by a free Atlassian Jira open source license for The Linux Foundation. Try Jira - bug tracking software for your team. Atlassian | 2026-01-13T09:29:33 |
https://www.tumblr.com/support?language=ja_JP | ヘルプセンター | 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.ecns.cn/video/2026-01-12/detail-iheywhna5918751.shtml | A surreal start of 2026: When one president seizes another, next target — Greenland --> 中文 Home News Ecns Wire Business Travel Photo Video Voices RIGHT BG LINE Text: A A A Print Video A surreal start of 2026: When one president seizes another, next target — Greenland 2026-01-12 15:58:28 Ecns.cn Editor : Huang Fang ECNS App Download Venezuela's acting president Delcy Rodriguez on Thursday expressed gratitude to China for condemning the U.S. aggression against Venezuela and the seizure of Venezuelan President Nicolas Maduro and his wife. At the very start of 2026, a president was seized by another president. Can anyone imagine such a surreal opening to the new year? The U.S. military launched a series of attacks against Venezuela on Jan. 3, seizing Venezuelan President Nicolas Maduro and his wife. Maduro made his first appearance Monday morning at a New York courthouse. In an apparent attempt to cloak its military action with a veneer of legality, Washington went to great lengths. Beyond that, the United States has issued threats against seven countries, including Cuba, Colombia and Mexico, asserting that “the Western Hemisphere belongs to the United States,” and has even hinted at the possibility of using “a range of options,” including military force, to take control of Greenland from Denmark, triggering an uproar across Europe. Under Washington’s policy of power politics and coercion, is the world being pushed back toward an era governed by the law of the jungle? The answer, it seems, is far from reassuring. More Photo 'Weepy horse' toy goes viral after sewing error New giant panda pair makes public debut in Malaysia Exploring world's largest island Greenland Venezuelan people call on U.S. to release Nicolás Maduro and his wife Heavey snow hits Paris 'Southern Snow Town' draws tourists to Guizhou Province Global mayors attend dialogue in NE China on developing ice, snow economy 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 Most popular in 24h More Top news Hainan posts $170 million in duty-free sales in first seven days of 2026 Hainan steps up efforts to attract investment and boost consumption after customs operation launch AI-driven demand boosts memory stocks: report 'Weepy horse' toy goes viral after sewing error Production mistake turns 'weepy horse' toy into viral hit in China More Video Comicomment: No country has the right to act as the world's police What's it like doing business in China? Check what foreign friends say LINE Media partners: People's Daily | Xinhua | CGTN | China Daily Back to top About Us | Jobs | Contact Us | Privacy Policy Copyright ©1999-2026 Chinanews.com. All rights reserved. Reproduction in whole or in part without permission is prohibited. [ 网上传播视听节目许可证（0106168) ] [ 京ICP证040655号 ] [ 京公网安备 11010202009201号 ] [ 京ICP备05004340号-1 ] --> --> | 2026-01-13T09:29: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://en.hainan.gov.cn/ | Hainan Free Trade Port International Services 中文 | 日本語 | 한국어 | --> DEUTSCH | FRANÇAIS | ESPAÑOL | PORTUGUÊS | РУССКИЙ | العربية Trending Words: Sign in Register --> Dynamic Hainan Overview Cities and Counties Free Trade Port Sisterhood Relations I Want To Travel in Hainan Work in Hainan Study in Hainan Shop in Hainan Live in Hainan Do Business Invest in Hainan Trade with Hainan Business Environment Online Services One-stop Services For Individuals For Companies News and Highlights Updates In Focus Videos Expat Stories Government Leadership Government Agencies Laws and Regulations Reports FAQs Do Business Travel in Hainan Work in Hainan Study in Hainan Shop in Hainan Live in Hainan 请先登录以查看内容 登录 --> MOFCOM pledges support for HK's national development integration, enhanced complementary collaboration with Hainan Beach Games to enhance Sanya's sports-tourism appeal Foreign Ministry spokesman: Hainan to become the gateway of China's high-standard opening-up Hainan FTP becoming brand name for country's institutional opening-up One-stop Policy Inquiry and Interpretation Platform for Hainan FTP I Want To In Focus "Flipped in Hainan": When a winter escaper meets a forever wanderer Haikou named among China's top 10 most livable cities Duty-free shopping further fuels Hainan's holiday travel boom Most Requested Accommodation Medical Appointment Enterprise Registration Visa-free Access Employment Consular Authentication Transportation Attractions Job Opportunities Accommodation Medical Appointment Enterprise Registration Visa-free Access Consular Authentication Employment Transportation Attractions Job Opportunities --> Hainan Govt Service Hotline 12345 Available 24/7 for inquiries, complaints, suggestions, and more intlservices@hainan.gov.cn Feel free to email us with any requests and suggestions. Updates Sun, thrills and roots 2026-01-13 Yingge dance brings vibrancy to Haikou's cultural landmark 2026-01-13 A journey comes full circle 2026-01-13 Hainan Tourism: Island sees booming cultural and tourism market following special customs operations launch 2026-01-13 Beach Games to enhance Sanya's sports-tourism appeal Expat Stories Pursuing opportunity to enjoy 'zero tariff' Hainan Embracing opportunities in China: A Russian ballet teacher's perspective Charlotte's China story American translator: Hainan FTP unlocks career opportunities FAQs Does the employer need to obtain approval when hiring foreign interns? Can nationals of the 59 visa-free countries travel to other regions within China before coming to Hainan? What are the eligibility requirements for purchasing offshore duty-free goods? How to apply for work permits in Hainan on this website? Links World Bank Group World Trade Organization United Nations Conference on Trade and Development United Nations Educational, Scientific and Cultural Organization United Nations Environment Programme World Tourism Organization International Union for Conservation of Nature Asia-Pacific Economic Cooperation Shanghai Cooperation Organization Belt and Road Portal Hainan International Communication Network Beijing Tianjin Hebei Shanxi Shanghai Jiangsu Zhejiang Anhui Fujian Jiangxi Henan Hubei Hunan Guangxi Sichuan Guizhou Shaanxi Hong Kong Macao Contact Us Dynamic Hainan I Want To Do Business Online Services News and Highlights Government FAQs Disclaimer | Copyright © 2025 Hainan Provincial People’s Government. All rights reserved. | Beta version. You are leaving this site and will be connected to a third-party website. Continue Back | 2026-01-13T09:29:33 |
https://reports.jenkins.io/jelly-taglib-ref.html#form.3Aoption | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:33 |
http://groovy-lang.org/syntax.html#_dollar_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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.