search

fortify-ps / FortifyBugTrackerUtility

Automated submission of FoD and SSC vulnerabilities to external systems
MIT License
25 stars 14 forks source link

Display application release/version name being processed #71

Closed rsenden closed 1 year ago

rsenden commented 1 year ago

Sample output:

[main] [FoD] Release ZDT:dev excluded; doesn't match configured filter expression
[main] [FoD] Release ZDT:release excluded; doesn't match configured filter expression
[main] [Process] Error during process run: ERROR: Required option -ArcherApplicationName not set
java.lang.IllegalStateException: ERROR: Required option -ArcherApplicationName not set
    at com.fortify.processrunner.RunProcessRunnerFromSpringConfig.checkContext(RunProcessRunnerFromSpringConfig.java:179) ~[FortifyBugTrackerUtility-4.10.jar:?]
    at com.fortify.processrunner.RunProcessRunnerFromSpringConfig.run(RunProcessRunnerFromSpringConfig.java:84) ~[FortifyBugTrackerUtility-4.10.jar:?]
    at com.fortify.processrunner.RunProcessRunnerFromCLI.run(RunProcessRunnerFromCLI.java:167) ~[FortifyBugTrackerUtility-4.10.jar:?]
    at com.fortify.processrunner.RunProcessRunnerFromCLI.main(RunProcessRunnerFromCLI.java:361) ~[FortifyBugTrackerUtility-4.10.jar:?]
[main] [Process] Error during process run: ERROR: Required option -ArcherApplicationName not set
java.lang.IllegalStateException: ERROR: Required option -ArcherApplicationName not set
    at com.fortify.processrunner.RunProcessRunnerFromSpringConfig.checkContext(RunProcessRunnerFromSpringConfig.java:179) ~[FortifyBugTrackerUtility-4.10.jar:?]
    at com.fortify.processrunner.RunProcessRunnerFromSpringConfig.run(RunProcessRunnerFromSpringConfig.java:84) ~[FortifyBugTrackerUtility-4.10.jar:?]
    at com.fortify.processrunner.RunProcessRunnerFromCLI.run(RunProcessRunnerFromCLI.java:167) ~[FortifyBugTrackerUtility-4.10.jar:?]
    at com.fortify.processrunner.RunProcessRunnerFromCLI.main(RunProcessRunnerFromCLI.java:361) ~[FortifyBugTrackerUtility-4.10.jar:?]

The output shows releases that have been excluded, but when the utility starts processing included versions/releases, it doesn't display what version/release is being processed (at least not when an error occurs during the early phases of processing, as shown above).

Either the error message should include the release/version name that caused this error, or the output should show a message like Processing app:release before errors like these can occur.