EPIC: Create a Release Dashboard view

[smlambert]

A "release dashboard" ideally would have the following features:

• Given a set of tags (Given an aqa-tests release branch, use the set of tags in the testenv.properties files), gather all of the test results from the database that relate to those tags (even if they come from multiple pipelines)
  • Amalgamate multiple pipelines when they are split up or need respins (ie. win32 run separately, or a platform fails to build in first run and its run in a later pipeline (ideally it discovers this on its own, but may also want to manually override this)
• Summarize the status of the test runs (both private jck and public aqavit)
• Separating the "full view of all results" from the "results that require next actions" to simplify for those in the release (answer "what are the next actions I need to take in order to complete this release?"). Default to less noisy view.
• Indicate if platforms are ready to publish (if all automation ran green first time)
• Have a 'scorecard/metrics' section to show how smoothly the release went (gather stats on how much manual intervention required, aborted/failed jobs, etc), possibly comparing to last release run.
• Push updates to github issues (perhaps updating a status issue in github instead of having to manually update it).
• Make this the default view (showing the dashboard of the latest EA or GA tags for the set of versions being built)
  • Separate GA and EA dashboards (in tabs or some other way, to keep a clear differentiation between the 2)

Things to consider:

• include some items listed in EPIC: Improve the contents and organization of release summary report #649
• is this epic is the same or similar enough to the "By Version" view we prototyped previously Creation of new "By Version" tab by JumpStart team #549 and pull out key features of that initiative for this dashboard
• consider if such a dashboard can be leveraged for Trestle initiative