microsoft / component-detection

Scans your project to determine what components you use
MIT License
438 stars 90 forks source link

Add support to persist pip reports #1224

Closed pauld-msft closed 3 months ago

pauld-msft commented 3 months ago

The primary use case here is when the same build stage has both Component Detection and SBOM (where CD runs again). This will allow whichever comes second to be able to just use the previous runs' reports, rather than regenerating them.

codecov[bot] commented 3 months ago

Codecov Report

Attention: Patch coverage is 42.85714% with 4 lines in your changes missing coverage. Please review.

Project coverage is 76.4%. Comparing base (924c4ea) to head (6fec1cf).

Files Patch % Lines
...ection.Detectors/pip/PipReportComponentDetector.cs 33.3% 3 Missing and 1 partial :warning:
Additional details and impacted files ```diff @@ Coverage Diff @@ ## main #1224 +/- ## ======================================= + Coverage 75.8% 76.4% +0.6% ======================================= Files 258 258 Lines 11668 11671 +3 Branches 1179 1180 +1 ======================================= + Hits 8847 8925 +78 + Misses 2479 2406 -73 + Partials 342 340 -2 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

github-actions[bot] commented 3 months ago

👋 Hi! It looks like you modified some files in the Detectors folder. You may need to bump the detector versions if any of the following scenarios apply:

If none of the above scenarios apply, feel free to ignore this comment 🙂