Diff for "BuildBranchToArchiveUI/UseCaseDailyBuild"

Not logged in - Log In / Register
Differences between revisions 5 and 7 (spanning 2 versions)
⇤ ← Revision 5 as of 2010-02-15 11:33:32 →
Size: 1816
Editor: michael.nelson
Comment: Updated daily build with new mockup.
← Revision 7 as of 2010-02-15 11:39:59 → ⇥
Size: 2468
Editor: michael.nelson
Comment: Moved daily build questions to separate dailybuilds use-case page.
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
= A typical daily build use-case = = Typical daily build use-cases =
Line 30: Line 30:
 * What actually happens when I click 'Build daily'? Obviously it'll be scheduled to run daily, but will the first build happen straight away? How do I know?
 * Would we want to ensure that users can actually choose the daily build time for a daily build? (ie. it may be desired that the build happens at 3am local time for a group so the next morning they all get the update?).
 * Initially we may not even want the 'Build daily' option to be available to general users (due to resources), instead enabling daily builds via a separate interface?
   * ''We could ensure on this interface that it is only present/valid for certain groups etc. too?''

Contents

  1. Typical daily build use-cases
    1. Build my branch daily - existing recipe
    2. Build my branch daily - new recipe
    3. Editing the daily build
  2. Notes for graceful degradation - non-js version
  3. See also
  4. Unresolved questions

Typical daily build use-cases

Build my branch daily - existing recipe

Guilherme works on the toggle project and has a number of PPAs including 'toggle_daily' and 'toggle_beta'. He now wants to automate his daily builds.

While viewing his branch, Guilherme:

  1. Clicks on the "Build this branch" link, (MOCKUP REQUIRED)
  2. A "Build this branch to a PPA" overlay appears displaying a selection for his target PPA and a recipe. Guilherme selects his target PPA where he wants the package to be published. By default, the recipe selector is displaying "toggle_std_pkging by Toggle Dev Team" and the displayed recipe description states "This is the default recipe for building Toggle. It merges the official packaging branch only." The description also informs him that the recipe targets Lucid and 9.10. Guilherme realises that it's exactly what he wants and simply clicks "Build daily".

Build now overlay

  1. The overlay disappears and the branch page is updated with a "Recent builds" portlet listing the new build and its status (MOCKUP REQUIRED), linking to (somewhere appropriate within) the PPA.

Build my branch daily - new recipe

Please refer to the manual build use-cases, as the only difference is clicking 'Build daily' rather than 'Build now'.

Editing the daily build

TBD

Notes for graceful degradation - non-js version

See also

Unresolved questions

  • What actually happens when I click 'Build daily'? Obviously it'll be scheduled to run daily, but will the first build happen straight away? How do I know?
  • Would we want to ensure that users can actually choose the daily build time for a daily build? (ie. it may be desired that the build happens at 3am local time for a group so the next morning they all get the update?).
  • Initially we may not even want the 'Build daily' option to be available to general users (due to resources), instead enabling daily builds via a separate interface?

    • We could ensure on this interface that it is only present/valid for certain groups etc. too?

BuildBranchToArchiveUI/UseCaseDailyBuild (last edited 2010-03-02 16:05:09 by michael.nelson)