Merge lp:~facundo/tanuki-agent/tutorial-first-boot into lp:tanuki-agent

Proposed by Facundo Batista on 2015-12-22
Status: Merged
Approved by: Roberto Alsina on 2015-12-22
Approved revision: 196
Merged at revision: 196
Proposed branch: lp:~facundo/tanuki-agent/tutorial-first-boot
Merge into: lp:tanuki-agent
Diff against target: 47 lines (+24/-2)
1 file modified
docs/tutorial-products.md (+24/-2)
To merge this branch: bzr merge lp:~facundo/tanuki-agent/tutorial-first-boot
Reviewer Review Type Date Requested Status
Roberto Alsina (community) 2015-12-22 Approve on 2015-12-22
Review via email: mp+281252@code.launchpad.net

Commit message

Added a section regarding first boot tests.

Description of the change

Added a section regarding first boot tests.

To post a comment you must log in.
Roberto Alsina (ralsina) :
review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'docs/tutorial-products.md'
2--- docs/tutorial-products.md 2015-12-15 20:34:26 +0000
3+++ docs/tutorial-products.md 2015-12-22 20:08:11 +0000
4@@ -579,7 +579,7 @@
5
6 If all went well, you should now see both versions 1 and 2 of test-snap listed. If you don't see version 2 listed under the Edge channel, try refreshing the page.
7
8-You now have an updated applicaiton snap published to the ```edge``` channel.
9+You now have an updated application snap published to the ```edge``` channel.
10
11 ## Running the Update Test
12
13@@ -598,7 +598,7 @@
14
15 ## Promote to Stable
16
17-Assuming the test has passed and you are ready to release this version of the applicaiton to your customers, it is now time to Promote the package via the MyApps site:
18+Assuming the test has passed and you are ready to release this version of the application to your customers, it is now time to Promote the package via the MyApps site:
19
20 - visit: https://myapps.developer.ubuntu.com/dev/click-apps/?format=snap
21 - click on the test-snap package name to get to the package details page
22@@ -620,3 +620,25 @@
23 </div>
24 </div>
25
26+
27+## First-boot tests
28+
29+When you promote images, as said above, the system will generate new Gold Master candidate tests, creating Product Base Images that are the base for when testing Updates.
30+
31+Update tests will be created always using the latest Product Base Image, but if you release images you'll need the Update tests to also be created using those released images. This is handled automatically by the system, all you need is to mark the Product Base Image as released, and the Update tests will be generated using not only the latest Product Base Image, but also all those that were ever released (until you deactivate them).
32+
33+This way you can list all the Product Base Images for a given product.
34+
35+ ./api_example.py -X GET config.ini https://spi.canonical.com/products/$PRODUCT_ID/baseimages
36+
37+To mark any of those as released, just do:
38+
39+ ./api_example.py -X PUT config.ini https://spi.canonical.com/products/$PRODUCT_ID/baseimages/<baseimage_id> --data '{
40+ "released": true
41+ }'
42+
43+After this step, that Product Base Image will be used in the Update tests. The moment you decide that any Product Base Image shouldn't be used for Update tests, you can deactivate it, by doing:
44+
45+ ./api_example.py -X PUT config.ini https://spi.canonical.com/products/$PRODUCT_ID/baseimages/<baseimage_id> --data '{
46+ "active": false
47+ }'

Subscribers

People subscribed via source and target branches

to all changes: