launchpad development|
⇤ ← Revision 1 as of 2010-02-09 12:05:58
Size: 2902
Comment:
|
Size: 2898
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| = A typical manual build of the a branch = | = A typical manual build of a branch = |
A typical manual build of a branch
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"),
- 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',
- 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.
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
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).
