Scan pipeline code/file

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

XMLWordPrintable

      We find this tool very useful for all the common known conditions.  But often the known issue is a bit buried in the code and we can't see an easy mark in the logs.

      If the same pattern scan could also be run against a file (if exists) in the workspace it would help.

      Can something like this be added?

            Assignee:
            Tomas Westling
            Reporter:
            Michael Carter
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: