sarif/json ingest on CI Run step
pending feedback
J
Jambalaya Echidna
Similar to how CI can pull JUnit.xml from both the Test-specific steps as well as any arbitrary Run step in CI stages, it would be awesome for Run steps to have an option to pass the location of a SARIF or STO-formatted JSON, as well as the Target/Variant information, to effectively remove the requirement for a downstream Custom Ingest step and save on overall build time and maintenance.
Log In
S
Serious Mockingbird
Another variant to this suggestion is to give guidance on how to build or run the Custom Stage (maybe have Custom Stage container as a base container) and extend it so that it can pull from a sarif/json created while the plugin runs.
Pritesh Chandaliya
pending feedback