launchpad development|
Size: 2930
Comment:
|
Size: 3497
Comment: Updated the recipe creation step.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 9: | Line 9: |
| [[http://people.canonical.com/~michaeln/bfb/build_now_overlay.png|{{http://people.canonical.com/~michaeln/bfb/build_now_overlay.png|Build now overlay|width=1000}}]] 1. clicks on the "Build now" button (or "Create a build" or "Build this"), 1. An overlay appears displaying a template recipe to be used as there are not yet any recipes associated with this branch (image on the right). If there were already recipes available for this branch, Guilherme would have the option of simply selecting one (image on the left) or clicking on 'Create new recipe' which would expand the Recipe details and make the relevant fields editable as shown (image on the right). After checking the packaging branch and selecting the appropriate PPA and clicking 'Start build', 1. The branch page is updated with a "Recent builds" portlet listing the new build and its status, linking to (somewhere appropriate within) the PPA. At this point, Launchpad will have created both a new recipe for Guilherme and the first build of that recipe. |
1. clicks on the "Build now" button (or "Create a build" or "Build this") (NEED MOCKUP), 1. A "Build this branch to a PPA" overlay appears displaying a selection for his target PPA and someone elses recipe that has been created to build toggle branches (shown below). Guilherme selects his target PPA where he wants the packages to be published, and then reads the recipe description and realises straight away that it's not what he wants. He clicks on the recipe selector and selects the only other option. He reads the description of this second recipe, realises it's also not something he can re-user, and so clicks on the "Create a new recipe" link. [[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 transitions (fade in/out) to a "Create a build recipe for Toggle" overlay (shown below). Guilherme enters a useful name and description for his new recipe, selects his packaging branch and clicks save. [[http://people.canonical.com/~michaeln/bfb/create_recipe_v2-collapsed.png|{{http://people.canonical.com/~michaeln/bfb/create_recipe_v2-collapsed.png|Create recipe}}]] 1.#4 The overlay transitions back to the previous "Build this branch to a PPA" dialog, with his new recipe already selected. Guilherme clicks 'Build now'. 1. The overlay disappears and the branch page is updated with a "Recent builds" portlet listing the new build and its status, linking to (somewhere appropriate within) the PPA. |
| Line 25: | Line 26: |
| NOTE: the following non-js mockups are out of date. |
A typical manual branch build use-case
Guilherme has his own branch of the Toggle project and would like to build and publish the resulting package in his PPA, using his own version of the official packaging branch.
Initiating the build for the first time
While viewing his branch page, Guilherme:
- clicks on the "Build now" button (or "Create a build" or "Build this") (NEED MOCKUP),
- A "Build this branch to a PPA" overlay appears displaying a selection for his target PPA and someone elses recipe that has been created to build toggle branches (shown below). Guilherme selects his target PPA where he wants the packages to be published, and then reads the recipe description and realises straight away that it's not what he wants. He clicks on the recipe selector and selects the only other option. He reads the description of this second recipe, realises it's also not something he can re-user, and so clicks on the "Create a new recipe" link.
- The overlay transitions (fade in/out) to a "Create a build recipe for Toggle" overlay (shown below). Guilherme enters a useful name and description for his new recipe, selects his packaging branch and clicks save.
- The overlay transitions back to the previous "Build this branch to a PPA" dialog, with his new recipe already selected. Guilherme clicks 'Build now'.
- The overlay disappears and the branch page is updated with a "Recent builds" portlet listing the new build and its status, linking to (somewhere appropriate within) the PPA.
Determining the state of the current build
A few minutes later, Guilherme decides to check on how his build of his branch is progressing...
Re-using the recipe for a subsequent build
A week later, Guilherme needs to create and publish a specific version of his branch into a separate PPA...
Notes for graceful degradation - Non-JS version
NOTE: the following non-js mockups are out of date. Without JavaScript, the "Build now" link would go to a "/+buildbranch" page for the branch:
allowing Guilherme to select a recipe and indicate the ppa. If there weren't any recipes, or he wanted to create a new one, he can click on 'create a new recipe' which takes him to:
Once Guilherme successfully creates a new recipe he is redirected back to the +build page above.
Actually, an alternative here (given that it is all for the non-JS version) would be to combine the two pages into one (nope, that ui is getting too complicated, and it's just for the non-js version, better to keep it as two simpler pages).
