||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>||

== Purpose ==

The /builders/+builds/<BUILD_ID> page should enable users to easily view the information they are looking for:

 * Which source ? Which context ?
 * When ? and How long ?
 * What state ? Any results ?

Also, people who have rights to act (retry, rescore, cancel) on builds should see pointer to those actions easily.

Target user audience:

 * Release-managers/Buildd-admins;
 * Uploaders;
 * Users in general.

All categories of users probably fit in the same set of use cases. They ought spot, at a glance, as much information we store according to the build state and they also ought to be able to navigate to the corresponding building source and resulting binaries when it's the case.

Mockup templates applied over real data at https://dogfood.launchpad.net/ubuntu/+builds

== Mockups ==

=== Successfully built ===
{{attachment:built-build.png}}

 * Willian, as an uploader/user, wants to:
   * view and navigate to source and the build context (distroarchseries, archive, component)
   * view in which context the source was built.
   * view when the build was requested.
   * view which builder built the source.
   * view when the source was built.
   * view how long the source took to build.
   * view if any resulted binary package is waiting acceptance.
   * view and navigate to the resulted binary packages.
   * be able to directly download build logs (build and upload).
   * be able to directly download any produced deb/udeb/ddeb files.

=== PPA build ===
{{attachment:ppa-build.png}}

 * Willian, as an uploader/user, wants to:
   * ''same uses cases than builds in primary archive''.


=== Failed to build ===
{{attachment:failed-build.png}}

 * Willian, as an uploader/user, wants to:
   * view and navigate to source and the build context (distroarchseries, archive, component)
   * view in which context the source was built.
   * view when the build was requested.
   * view which builder built the source.
   * view when the source was built.
   * view how long the source took to build.
   * be able to directly download build logs (build and upload).
   * retry (and probably rescore) the failed build inline.

=== Pending build ===

{{attachment:pending-build.png}}

 * Willian, as an uploader/user, wants to:
   * view and navigate to source and the build context (distroarchseries, archive, component)
   * view when the build was requested.
   * view in which context the source will be built.
   * view when it is going to be dispatched.
 * Sarah as a buildd-admin, wants to:
   * be able to rescore inline, so it will get dispatched sooner.


=== Build in progress ===
{{attachment:building-build.png}}

 * Willian, as an uploader/user, wants to:
   * view and navigate to source and the build context (distroarchseries, archive, component)
   * view when the build was requested.
   * view which builder is building the source.
   * view the ongoing build log.
   * view an estimation of how long it is going to take.
 * Sarah, as a buildd-admin, wants to:
   * cancel the job in progress and free the builder to do something more important.


== Feedback ==

AdamConrad: I find the previous way of presenting build details more readable and miss a 2-column table listing key/values. The sentences are 'pretty' but not as easy to read/parse. [fixed]

AdamConrad: buildlog.txt and uploadlog.txt should not be treated as ordinary build files, despite of being listed first, it doesn't seem correct to mix them with the resulting debs. [fixed]

Max: The word 'Dispatch' doesn't reads well for people not familiar with the terms we use, maybe 'Start'. [fixed]