No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
The Build Pipeline Overview (BPO) component is a read-only user interface (UI) that will provide information about any module. | The Build Pipeline Overview (BPO) component is a read-only user interface (UI) that will provide information about any module. | ||
The main three functions | The main three functions could be something like this: | ||
* Browsing and searching modules | * Browsing and searching for modules | ||
* Showing build state of a module | * Showing build state of a module | ||
* Showing content of a module and relationships between modules | * Showing content of a module and relationships between modules | ||
Line 8: | Line 8: | ||
== Browsing modules == | == Browsing modules == | ||
Every module can be uniquely identified by the name of the module, version, and release (NVR). The interface should allow you to find a module based on NVR, show last version of a module, etc. | Every module can be uniquely identified by the name of the module, version, and release (NVR). The interface should allow you to find a module based on NVR, show last version of a module, etc. | ||
== Build states == | == Build states == | ||
The build pipeline and corresponding build sates are shown on the picture below. The interface should show | The build pipeline and corresponding build sates are shown on the picture below. The interface should show the state of a module in this pipeline. | ||
[[File:BPO- | |||
[[File:BPO-build-states.png|600px]] | |||
== Relationships == | == Relationships == | ||
A module has the following relationships. The UI should allow to see the build | A module has the following relationships. The UI should allow to navigate trough these relationships to see details of other modules. It should also show the build states of all of these. | ||
[[File:BPO- | |||
[[File:BPO-relationships.png|600px]] |
Revision as of 16:09, 1 July 2016
The Build Pipeline Overview (BPO) component is a read-only user interface (UI) that will provide information about any module.
The main three functions could be something like this:
- Browsing and searching for modules
- Showing build state of a module
- Showing content of a module and relationships between modules
Browsing modules
Every module can be uniquely identified by the name of the module, version, and release (NVR). The interface should allow you to find a module based on NVR, show last version of a module, etc.
Build states
The build pipeline and corresponding build sates are shown on the picture below. The interface should show the state of a module in this pipeline.
Relationships
A module has the following relationships. The UI should allow to navigate trough these relationships to see details of other modules. It should also show the build states of all of these.