[JENKINS-28380] Give expression examples for restricting where builds can run · jenkinsci/jenkins#21113

2015-05-13T16:19:36.000Z

For the check-box "Restrict where this project can be run," there is nothing in the help that mentions what kind of expressions you can write. From trial and error, I deduced that "a || b" means "use either a or b as build nodes." I expected a comma, like other fields (eg. projects that can access archives, projects to run after this build, etc.) I'm sure there are other valid expressions, such as using "*". Can you please update the help for this field to include some examples? I ended up looking at the source on GitHub and guessed this from the use of Antlr. --- Originally reported by ashes999 , imported from: Give expression examples for restricting where builds can run status : Open priority : Minor component(s) : core label(s) : jenkins, newbie-friendly, user-experience resolution : Unresolved votes : 0 watchers : 2 imported : 2025-11-24 Raw content of original issue For the check-box "Restrict where this project can be run," there is nothing in the help that mentions what kind of expressions you can write. From trial and error, I deduced that "a || b" means "use either a or b as build nodes." I expected a comma, like other fields (eg. projects that can access archives, projects to run after this build, etc.) I'm sure there are other valid expressions, such as using "*". Can you please update the help for this field to include some examples? I ended up looking at the source on GitHub and guessed this from the use of Antlr. environment : Jenkins ver. 1.609. I don't know the JRE or OS, sorry (my guess in Windows OS) because I don't manage these machines.

(2 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)Java (9.474 Forks)batch import

component:coregood first issueimported-jira-issuejira-type:taskpriority:minorresolution:unresolvedux

Repository-Metriken

Stars: (25.266 Stars)
PR-Merge-Metriken: (Durchschn. Merge 10T 9h) (93 gemergte PRs in 30 T)

Beschreibung

Contributor Guide

Research-Richtung: Untersuche den Jenkins Quellcode für den Label Ausdrucksparser (ANTLR Grammatik) und füge praktische Beispiele zum Hilfetext für das Feld 'Einschränken, wo dieses Projekt ausgeführt werden kann' hinzu.
Tech Stack: java
Domain: ci cddocumentation
Issue Type: Dokumentation
Schwierigkeit: 2
Geschätzte Zeit: 1-3 Stunden
Aktivitätsstatus: Frisch
Klarheit: Klar
Voraussetzungen: Jenkins
Einsteigerfreundlichkeit: 85

Repository-Metriken

Beschreibung

Contributor Guide

Erhalte frische Easy Issues per E-Mail.