Mercurial > bitten > bitten-test
changeset 393:e3ab7698dae7
Updates to the docs.
| author | cmlenz |
|---|---|
| date | Fri, 03 Aug 2007 08:54:56 +0000 |
| parents | 026d9aa41b85 |
| children | 932d4d3ac790 |
| files | ChangeLog README.txt doc/orchestration.dtd setup.cfg setup.py |
| diffstat | 5 files changed, 22 insertions(+), 108 deletions(-) [+] |
line wrap: on
line diff
--- a/ChangeLog +++ b/ChangeLog @@ -1,8 +1,16 @@ -Version 0.5.4 -(?, from 0.5.x branch) -http://bitten.cmlenz.net/repos/bitten/tags/0.5.4 +Version 0.6 +(?, from 0.6.x branch) +http://bitten.cmlenz.net/repos/bitten/tags/0.6.0 - * Fix incompatibility with Trac 0.10.3. + * Switch to using HTTP for communication between the build master and build + slaves. This means the `build-master` executable is no longer needed or + installed, the build simply runs in the scope of the Trac site. + * Build recipes now need to include instructions for performing the checkout + from the version control repository. The slave no longer receives a snapshot + archive of the code, but performs the checkout itself based on the + instructions in the build recipe. + * Many fixes for compatibility with more recent versions of Trac. + Version 0.5.3 (18 April 2006, from 0.5.x branch) @@ -11,12 +19,14 @@ * Fix double-escaping of report summaries. * Fix build master error when build log contains no messages. + Version 0.5.2 (17 January 2006, from 0.5.x branch) http://bitten.cmlenz.net/repos/bitten/tags/0.5.2 * Fixes the main navigation tab that was broken in 0.5.1. + Version 0.5.1 (10 January 2006, from 0.5.x branch) http://bitten.cmlenz.net/repos/bitten/tags/0.5.1 @@ -28,6 +38,7 @@ * Fixes encoding of non-ASCII characters in command output. * Fix for missing log output when using <java:ant> on Windows. + Version 0.5 (6 October 2005, from 0.5.x branch) http://bitten.cmlenz.net/repos/bitten/tags/0.5
--- a/README.txt +++ b/README.txt @@ -82,6 +82,7 @@ to manage build configurations, and allow anonymous users to view the status and results of builds: + $ trac-admin /path/to/projenv permission add anonymous BUILD_EXEC $ trac-admin /path/to/projenv permission add anonymous BUILD_VIEW $ trac-admin /path/to/projenv permission add [yourname] BUILD_ADMIN @@ -117,19 +118,19 @@ ----------------------- The build slave can be run on any machine that can connect to the machine -on which the build master is running. Just as with the build master, you -should find the build slave executable on your path after the installation. -The executable file is called `bitten-slave`. +on which the build master is running. The installation of Bitten should have put +a `bitten-slave` executable on your path. If the script is not on your path, +look for it in the `bin` or `scripts` subdirectory of your Python installation. To get a list of options for the build slave, execute it with the `--help` option: $ bitten-slave --help -To run the build slave against a master installed on myproject.example.org, -you'd run: +To run the build slave against a Bitten-enabled Trac site installed at +http://myproject.example.org/trac, you'd run: - $ bitten-slave myproject.example.org + $ bitten-slave http://myproject.example.org/trac/builds More Information
deleted file mode 100644 --- a/doc/orchestration.dtd +++ /dev/null @@ -1,94 +0,0 @@ -<!-- -DTD for the Bitten build orchestration BEEP profile. - -This schema is informative and should not be used to actually validate -messages. Due to the limitations of DTDs, it does not completely capture -the schema for messages exchanged using the Bitten BEEP orchestration -profile. ---> - -<!-- -Slave registration. ---> -<!ELEMENT register (platform, os, package*)> -<!ATTLIST register - name CDATA #REQUIRED - maintainer CDATA #IMPLIED> -<!ELEMENT platform #PCDATA> -<!ATTLIST platform - processor CDATA #IMPLIED> -<!ELEMENT os #PCDATA> -<!ATTLIST os - family CDATA #REQUIRED - version CDATA #IMPLIED> -<!ELEMENT package EMPTY> -<!ATTLIST package - name CDATA #REQUIRED> - -<!-- -Reply message from the master when registration of a slave was successful ---> -<!ELEMENT ok EMPTY> - -<!-- -Generic error message. Can be received in response to registration or build -initiation. ---> -<!ELEMENT error #PCDATA> -<!ATTLIST error - code CDATA #REQUIRED> - -<!-- -Build initiation request sent by the master to a slave. Contains the build -recipe. ---> -<!ELEMENT build (step+)> -<!ELEMENT step ANY> -<!ATTLIST step - id ID #REQUIRED - title CDATA #IMPLIED - onerror (fail|ignore) #IMPLIED> - -<!-- -Build request acknowledgement. ---> -<!ELEMENT started EMPTY> -<!ATTLIST started - time CDATA> - -<!-- -Build status reporting: ANS payload sent by the slave for every build step -processed. ---> -<!ELEMENT step (error|log|report)*> -<!ATTLIST step - id ID #REQUIRED - result (success|failure) #REQUIRED - description CDATA #IMPLIED - time CDATA #REQUIRED - duration CDATA #REQUIRED> - -<!ELEMENT log (message+)> -<!ATTLIST log - generator CDATA #IMPLIED> -<!ELEMENT message #PCDATA> -<!ATTLIST message - level (debug|info|warning|error) #IMPLIED> - -<!ELEMENT report ANY> -<!ATTLIST report - category CDATA #REQUIRED - generator CDATA #IMPLIED> - -<!-- -Completion of a build by the slave, independent of outcome. ---> -<!ELEMENT completed #PCDATA> -<!ATTLIST completed - result (success|failure) #REQUIRED - time CDATA> - -<!-- -Cancellation of a build by the slave. ---> -<!ELEMENT aborted #PCDATA>