Build:Release Automation: Difference between revisions

Build:Release Automation (view source)

Revision as of 18:36, 5 October 2007

2 bytes added , 5 October 2007

put bootstrap section back together

Rhelmer

canmove, Confirmed users

1,511

edits

@@ Line 19: / Line 19: @@
 <b>Stage</b> - create a staging area and rename files for release<br>
 <b>Sign</b> - not implemented<br>
+==Bootstrap Steps==
+A Bootstrap "step" must implement 2 required methods:
+<b>Execute</b> - carry out the actual function of the step, e.g. Build<br>
+<b>Verify</b> - run an automated test<br>
+Additionally, there are 2 optional methods:
+<b>Push</b> - upload the appropriate changes for testing, e.g. upload build to FTP<br>
+<b>Announce</b> - send an email announcing that the step has finished.<br>
+==Using Bootstrap==
+If the "release" command is invoked with no parameters, it will attempt to start at the first step and call the methods in this order:
+# Execute
+# Verify
+# Push
+# Announce
+As each step completes successfully, the next will be invoked.
+There are several command-line options, shown by calling "release -h":
+ Usage: release [-l] [-s Step] [-o Step] [-e | -v | -p | -a] [-h]
+     -l list all Steps
+     -s start at Step
+     -o only run one Step
+     -e only run Execute
+     -v only run Verify
+     -p only run Push
+     -a only run Announce
+     -h this usage message
+For example, to only run the Push method on the Build step:
+ ./release -o Build -p
 =Buildbot=
@@ Line 86: / Line 127: @@
 ** created "latest" and "latest-2.0" symlinks manually after final release
 ** created bouncer links manually {{Bug|372746}}
-==Bootstrap Steps==
-A Bootstrap "step" must implement 2 required methods:
-<b>Execute</b> - carry out the actual function of the step, e.g. Build<br>
-<b>Verify</b> - run an automated test<br>
-Additionally, there are 2 optional methods:
-<b>Push</b> - upload the appropriate changes for testing, e.g. upload build to FTP<br>
-<b>Announce</b> - send an email announcing that the step has finished.<br>
-==Using Bootstrap==
-If the "release" command is invoked with no parameters, it will attempt to start at the first step and call the methods in this order:
-# Execute
-# Verify
-# Push
-# Announce
-As each step completes successfully, the next will be invoked.
-There are several command-line options, shown by calling "release -h":
- Usage: release [-l] [-s Step] [-o Step] [-e | -v | -p | -a] [-h]
-     -l list all Steps
-     -s start at Step
-     -o only run one Step
-     -e only run Execute
-     -v only run Verify
-     -p only run Push
-     -a only run Announce
-     -h this usage message
-For example, to only run the Push method on the Build step:
- ./release -o Build -p
 =Roles and resource requirements=