From 3ceab6843db1ff54d5f2db125d6da60b3b9a2f6c Mon Sep 17 00:00:00 2001 From: ulfl Date: Sat, 24 Mar 2007 23:50:15 +0000 Subject: add a section about the buildbot some other minor editing git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@21170 f5534014-38df-0310-8fa8-9805f1628bb7 --- docbook/wsdg_src/WSDG_chapter_env_intro.xml | 172 +++++++++++++++++++++------- 1 file changed, 131 insertions(+), 41 deletions(-) (limited to 'docbook') diff --git a/docbook/wsdg_src/WSDG_chapter_env_intro.xml b/docbook/wsdg_src/WSDG_chapter_env_intro.xml index 10290652e6..bba040b98e 100644 --- a/docbook/wsdg_src/WSDG_chapter_env_intro.xml +++ b/docbook/wsdg_src/WSDG_chapter_env_intro.xml @@ -238,6 +238,11 @@ + + Win32 U3 (.u3 file). Special distribution for U3 capable USB memory sticks. + + + Debian (.deb file). A user of a Debian Package Manager (DPKG) based system is used to get a .deb file from which the package manager checks the @@ -293,6 +298,91 @@ +
+ Automated Builds (Buildbot) + + The Wireshark Buildbot automatically rebuilds Wireshark on every + change of the source code repository and indicates problematic changes. + This frees the developers from repeating (and annoying) work, so time can + be spend on more interesting tasks. + +
+ Advantages + + + Recognizing (cross platform) build problems - early. Compilation problems + can be narrowed down to a few commits, making a fix much easier. + + + "Health status" overview of the sources. A quick look at: gives a good "feeling" if + the sources are currently "well". + On the other hand, if all is "red", an update of a personal source tree + might better be done later ... + + + "Up to date" binary packages are available. + After a change was committed to the repository, a binary package / + installer is usually available within a few hours at: . + This can be quite helpful, e.g. a bug reporter can easily verify a bugfix + by installing a recent build. + + + Automated regression tests. Especially the fuzz tests often indicate + "real life" problems that are otherwise hard to find. + + +
+
+ What does the Buildbot do? + + The Buildbot will do the following (to a different degree on the different + platforms): + + + checkout from the source repository + + + build + + + create binary package(s) / installer + + + create source package (and check completeness) + + + run regression tests + + + Each step is represented at the status page by a rectangle, green if it + succeeded or red if it failed. Most steps provide a link to the corresponding + console logfile, to get additional information. + + + The Buildbot runs on a patform collection that represents the different + "platform specialties" pretty good: + + + Windows XP x86 (Win32, little endian, MSVC) + + + Ubuntu x86 (Linux, little endian, gcc) + + + Solaris SPARC (Solaris, big endian, gcc) + + + Mac OS-X PPC (BSD, big endian, gcc) + + + Each platform is represented at the status page by a single column, the + most recent entries are at the top. + +
+
+
Reporting problems and getting help @@ -346,7 +436,45 @@ format is easier to use.
- + +
Other sources + + + If you don't find the information you need inside this book, there are + various other sources of information: + + + + see the file doc/README.developer and + all the other README.xxx files in the source code - these are various + documentation files on different topics + + + + + have a look at the Wireshark source code + + + + + tool documentation of the various tools used + (e.g. manpages of sed, gcc, ...) + + + + + the different mailing lists + + + + + ... + + + + +
+
Mailing Lists There are several mailing lists of specific Wireshark topics available: @@ -415,9 +543,9 @@
-
Bug database +
Bug database (Bugzilla) - The Wireshark community started collecting bug reports in a Bugzilla database at + The Wireshark community collects bug reports in a Bugzilla database at &WiresharkBugsSite;. This database is filled with manually filed bug reports, usually after some discussion on wireshark-dev, and bug reports from the QA build tooling. @@ -547,43 +675,5 @@ $
-
Other sources of developer information - - - If you don't find the information you need inside this book, there are - various other sources of information: - - - - see the file doc/README.developer and - all the other README.xxx files in the source code - these are various - documentation files on different topics - - - - - have a look at the Wireshark source code - - - - - tool documentation of the various tools used - (e.g. manpages of sed, gcc, ...) - - - - - the different mailing lists - - - - - ... - - - - -
- -- cgit v1.2.3