27 ================== |
27 ================== |
28 |
28 |
29 At the start of preparation a new directory is created for the build and subst'ed to ``build.drive``. If a directory with this name already exists, it is renamed to have a current timestamp on the end. |
29 At the start of preparation a new directory is created for the build and subst'ed to ``build.drive``. If a directory with this name already exists, it is renamed to have a current timestamp on the end. |
30 |
30 |
31 .. index:: |
31 .. index:: |
32 single: How to prepare the build area? |
32 single: How to prepare the build area |
33 |
33 |
34 How to prepare the build area? |
34 How to prepare the build area |
35 ------------------------------ |
35 ----------------------------- |
36 |
36 |
37 TODO |
37 Helium supports the creation of an environment based on a release store in a network drive. The main requirement from that release is to publish release metadata with the content. |
|
38 |
|
39 .. csv-table:: Ant properties to modify |
|
40 :header: "Property", "Description", "Values" |
|
41 |
|
42 ":hlm-p:`s60.grace.server`", "UNC path to network drive.", "" |
|
43 ":hlm-p:`s60.grace.service`", "Service name.", "" |
|
44 ":hlm-p:`s60.grace.product`", "Product name.", "" |
|
45 ":hlm-p:`s60.grace.release`", "Regular expression to match release under the product directory.", "" |
|
46 ":hlm-p:`s60.grace.revision`", "Regular expresion to match a new build revision", "e.g: (_\d+)?" |
|
47 ":hlm-p:`s60.grace.cache`", |
|
48 ":hlm-p:`s60.grace.checkmd5.enabled`", |
|
49 ":hlm-p:`s60.grace.usetickler`", "Validate the release based on the tickler.", "true, false(default)" |
|
50 |
|
51 Once configured you can invoke Helium: |
|
52 |
|
53 > hlm -Dbuild.number=1 -Dbuild.drive=X: ido-update-build-area-grace |
|
54 |
|
55 > dir X: |
|
56 ... |
|
57 ... |
|
58 |
|
59 You should then have the latest/mentioned release un-archived under the X: drive. |