| Summary: | Isolate CBI platform build from uncontrolled software sources | ||
|---|---|---|---|
| Product: | [Technology] CBI | Reporter: | Andrea Ross <andrea.ross> |
| Component: | prototype | Assignee: | CBI Dummy user <cbi.prototype-inbox> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P2 | CC: | andrea.ross, denis.roy, gunnar, mikael.barbero, milesparker, pwebster |
| Version: | 2.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 376112 | ||
|
Description
Andrea Ross
Upping the priority on this ticket. Using the Eclipse platform for reference the build currently pulls from the following: 1) maven & tycho plugins 195 components 2) prereqs from downloads.eclipse.org 179 - mostly emf, ecf, ajdt, orbit You may be interested in how Fedora solved that problem: https://bugzilla.redhat.com/show_bug.cgi?id=809575 While this resonates very much with recent awareness of supply chain security issues, I doubt we will implement anything specific to Eclipse Platform or Eclipse projects. Let's rather provide best practices around SBOM generation and how to use it to analyze dependencies' provenance. See https://github.com/eclipse-cbi/best-practices/issues/1 |