launchpad development|
Size: 1237
Comment: Initial dump of second use-case.
|
Size: 2468
Comment: Moved daily build questions to separate dailybuilds use-case page.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| = A typical daily build use-case = | |
| Line 4: | Line 3: |
| Yong-Shik works on the ereader project and has a number of PPAs including 'ereader_daily' and 'ereader_beta'. He now wants to automate his daily builds. |
= Typical daily build use-cases = |
| Line 7: | Line 5: |
| == Setting up the daily build == | == Build my branch daily - existing recipe == |
| Line 9: | Line 7: |
| REDO: This could be achieved by adding scheduling options to the previous mockups: [[http://people.canonical.com/~michaeln/bfb/build_now_overlay_with_scheduling.png.png|{{http://people.canonical.com/~michaeln/bfb/build_now_overlay_with_scheduling.png.png|Build now overlay with scheduling|width=800}}]] (or simply a checkbox - no need for extra dropdowns). |
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. |
| Line 12: | Line 10: |
| Yong-Shik opens the Launchpad page for his devel branch and then 1. clicks on the "Build now" button, (MOCKUP-REQUIRED) 1. He selects his PPA, checks multiple distroseries, checks the dev-version template, selects the 'Build this branch daily' option, and hits build (MOCKUP-REQUIRED) 1. The branch page updates displaying (some-what prominently) 'This branch is built daily by Yong-Shik to the PPA EReader daily builds.' (Note question about multiple daily builds, official/unofficial etc.) |
While viewing his branch, Guilherme: 1. Clicks on the "Build this branch" link, (MOCKUP REQUIRED) 1. 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". [[http://people.canonical.com/~michaeln/bfb/build_now_overlay_v2.png|{{http://people.canonical.com/~michaeln/bfb/build_now_overlay_v2.png|Build now overlay}}]] 1.#3 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 [[BuildBranchToArchiveUI/UseCaseManualBuild|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 = * [[BuildBranchToArchiveUI/UseCaseManualBuild]] = 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?'' |
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:
- Clicks on the "Build this branch" link, (MOCKUP REQUIRED)
- 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".
- 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?
