Jump to: navigation, search

Difference between revisions of "CDT/ScannerDiscovery61"

< CDT
(Design and Development)
m (Add API)
Line 19: Line 19:
  
 
=== Design and Development ===
 
=== Design and Development ===
 
 
# [[CDT/ScannerDiscovery61/UseCases | What is it supposed to do anyway?]]
 
# [[CDT/ScannerDiscovery61/UseCases | What is it supposed to do anyway?]]
 
# [[CDT/ScannerDiscovery61/ExistingArch | Existing Architecture]]
 
# [[CDT/ScannerDiscovery61/ExistingArch | Existing Architecture]]
 
# [[CDT/ScannerDiscovery61/Design | Possible design]]
 
# [[CDT/ScannerDiscovery61/Design | Possible design]]
 +
# [[CDT/ScannerDiscovery61/API | Public API for new Scanner Discovery]]
 
# [[CDT/ScannerDiscovery61/Stories | The Stories and Alpha Version]]
 
# [[CDT/ScannerDiscovery61/Stories | The Stories and Alpha Version]]
  

Revision as of 17:07, 18 November 2010

The Issues

  • Difficult to create new scanner discovery profiles. Related bug: 219940
  • Too gnu centric. Related bug: 226419
  • Unable to easily refresh the discovered data when the environment changes Related bugs: 206372,142619,190902,264841
  • The UI for setting the scanner discovery profile is very confusing. Related bugs: 250166,255694,256374,262219
  • Scanner Discovery data is not tied to configurations
  • Unable to support multiple discover providers
  • Difficult to integrate built-in discovery with Managed Build.
  • No consistent API for integrators to contribute Path and Macros.
  • No one knows the architecture of scanner discovery
  • Build environment needs to integrate with scanner discovery.

The Plan

  1. Discover scanner discovery - document the existing architecture
  2. From that figure out what we need to do, follow bug 290631

Design and Development

  1. What is it supposed to do anyway?
  2. Existing Architecture
  3. Possible design
  4. Public API for new Scanner Discovery
  5. The Stories and Alpha Version

Thoughts