Warnings plugin doesn't allow environment variables in file names

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      When configuring file names to be scanned for compiler warnings, it would be good to be able to use build environment variables (similar to other fields e.g. the Command field in an Execute Shell box).

      I'd like to be able to enter "${CLEARCASE_VIEWPATH}/vobs/somePath/build_output" into the File Pattern field of Scan Workspace Files. But it doesn't expand the ${CLEARCASE_VIEWPATH}.

      I can work around it by using "*/vobs/somePath/build_output" as that filename is unique. But I shouldn't have to.

            Assignee:
            Ulli Hafner
            Reporter:
            Graham Menhennitt
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: