Query parse errors are hidden from the user

XMLWordPrintable

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major
    • Component/s: metadata-plugin
    • None

      Using the plug-in with some metadata fields, and looking for something like

      LOCATION=

      Will raise an exception in Jenkins log similar to this one:

      line 0:-1 mismatched input '<EOF>' expecting NAME
      com/sonyericsson/hudson/plugins/metadata/search/antlr/QueryWalker.g: node from line 0:0 no viable alternative at input 'LOCATION='

      But in the user interface, all that the user gets is a "No jobs found" search result. It would be better if users received a feedback that their query is not valid.

            Assignee:
            rsandell
            Reporter:
            Bruno P. Kinoshita
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: