• Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Critical Critical
    • core
    • None

      I want to restrict my job to run on a windows machine which support x86 architecture. Following the example of the online context help ("windows->x64") I am typing "windows->x86".

      But Jenkins tells me that this is an invalid expression, as > is an unexpected character. So either the parser or the online context help is wrong.

          [JENKINS-16728] "windows->x86" is an invalid expression

          evernat added a comment -

          reproduced using Jenkins 1.549: "windows->x64", without space, is still an example in the context help for the label of any type of job, but "windows->x64" does not work.

          evernat added a comment - reproduced using Jenkins 1.549: "windows->x64", without space, is still an example in the context help for the label of any type of job, but "windows->x64" does not work.

          Daniel Beck added a comment -

          This has been in the build output forever, possibly related:

          [INFO] Using Antlr grammar: /home/jenkins/slave/workspace/jenkins_main_trunk/core/src/main/grammar/labelExpr.g
          ANTLR Parser Generator   Version 2.7.6 (2005-12-22)   1989-2005
          /home/jenkins/slave/workspace/jenkins_main_trunk/core/src/main/grammar/labelExpr.g: warning:lexical nondeterminism between rules IMPLIES and ATOM upon
          /home/jenkins/slave/workspace/jenkins_main_trunk/core/src/main/grammar/labelExpr.g:     k==1:'-'

          Daniel Beck added a comment - This has been in the build output forever, possibly related: [INFO] Using Antlr grammar: /home/jenkins/slave/workspace/jenkins_main_trunk/core/src/main/grammar/labelExpr.g ANTLR Parser Generator Version 2.7.6 (2005-12-22) 1989-2005 /home/jenkins/slave/workspace/jenkins_main_trunk/core/src/main/grammar/labelExpr.g: warning:lexical nondeterminism between rules IMPLIES and ATOM upon /home/jenkins/slave/workspace/jenkins_main_trunk/core/src/main/grammar/labelExpr.g: k==1: '-'

          Daniel Beck added a comment -

          Daniel Beck added a comment - Probably caused by this commit: https://github.com/jenkinsci/jenkins/commit/3b8eea6ccc6a16caa7e901658f4798090d398c40

          Daniel Beck added a comment -

          Duplicates JENKINS-22975 (The newer issue has nicer code demonstrating the issue in more detail, so resolving this one instead)

          Daniel Beck added a comment - Duplicates JENKINS-22975 (The newer issue has nicer code demonstrating the issue in more detail, so resolving this one instead)

          Wadeck Follonier added a comment - https://github.com/jenkinsci/jenkins/pull/5722 should correct this behavior

            Unassigned Unassigned
            mkarg Markus KARG
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: