jenkinsci/fortify-on-demand-uploader-plugin

Add ability to submit a scan note

Opened this issue · 0 comments

There are cases where development teams need to know which commit exactly was scanned.

This suggestion is to allow a note to be tacked on to a scan to relate the scan back to a commit hash (see suggested approach here: bars0um@191e17a)

The main issue with this approach is that it would break pipelines/builds because definitions made before the change would not include the scan note parameter...

Edit:
Overloading the modified methods instead of replacing them would allow older builds to continue working fine.

** Edit 2: **
Scan note on the fork is now an optional parm (using @DataBoundSetter), this should fix the backwards compatibility issue described above.