Tracking Juju CI's devel and stable branches

[Curtis Hovey-Canonical]

The best way to get an over view and details of the versions juju CI
tests is to visit
     http://reports.vapour.ws/releases
You can see the details of what was tested for each revision

The results for each version tested for a proposed version number are
lists. Since Jenkins doesn't understand that Juju has multiple
branches, and that some tests are not used to bless a revision, the
report site is place the QA team watches.

The repoting site is incomplete. We ran out of time to complete this report.

1.  http://reports.vapour.ws/releases needs to state the last version
tested for stable and devel so that you don't need to scroll. There is
also an ordering problem on the page.

2. The Status column can have "Not Set", that is a failure where
Jenkins could not run every test because one or more essential tests
failed. For example, when the tarball is broken or streams cannot be
published to the CPCs, most tests are blocked. The "Not Set" error is
more sever then curse, it is a "damning" of the revision because an
attempt to release it will fail. This is a bug in CI-Director. It knew
the revision failed so moved on to test the next revision.

3. The details of each test run is missing the artefacts. The page
must provide links to release tarball, windows installer, test logs,
and test packages. All the date from the test jobs were saved to a
private s3 container. We want to provide links to the public data.

When these three issues are solved, you wont need to visit Jenkins.

-- 
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui