DESIGN: how does backend need to modify to always make reports
Problem to solve
rails backend likely needs to change to support always making a report
Proposal
Figure out the work involved and the side effect of ALWAYS making a reporting artifact and share that with the entire secure and protect team (slide deck? link to issue and AMA?) then we will create an epic with all the the correct steps (issues) some of which may be POC or other discussions about identified side effects.
User experience goal
more information available, consistency, possibly enable us to add more exit codes so people can get more granular in their pipeline rules
Is this a cross-stage feature?
Category:SAST Category:DAST Category:Fuzz Testing Category:Container Scanning
would we want Category:Code Quality included?
and CC groupthreat insights groupvulnerability research
The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.