/usr/share/doc/wireshark-doc/wsdg_html_chunked/ChIntroAutomated.html is in wireshark-doc 1.10.6-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 | <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>1.6. Automated Builds (Buildbot)</title><link rel="stylesheet" type="text/css" href="ws.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="Wireshark Developer's Guide"><link rel="up" href="ChapterIntroduction.html" title="Chapter 1. Introduction"><link rel="prev" href="ChIntroReleases.html" title="1.5. Releases and distributions"><link rel="next" href="ChIntroHelp.html" title="1.7. Reporting problems and getting help"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.6. Automated Builds (Buildbot)</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ChIntroReleases.html">Prev</a> </td><th width="60%" align="center">Chapter 1. Introduction</th><td width="20%" align="right"> <a accesskey="n" href="ChIntroHelp.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ChIntroAutomated"></a>1.6. Automated Builds (Buildbot)</h2></div></div></div><p>
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 spent on more interesting tasks.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp21440972"></a>1.6.1. Advantages</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Recognizing (cross platform) build problems - early. Compilation problems
can be narrowed down to a few commits, making a fix much easier.
</p></li><li class="listitem"><p>
"Health status" overview of the sources. A quick look at: <a class="ulink" href="http://buildbot.wireshark.org/trunk/" target="_top">http://buildbot.wireshark.org/trunk/</a> 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 ...
</p></li><li class="listitem"><p>
"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: <a class="ulink" href="http://www.wireshark.org/download/automated/" target="_top">http://www.wireshark.org/download/automated/</a>.
This can be quite helpful, e.g. a bug reporter can easily verify a bugfix
by installing a recent build.
</p></li><li class="listitem"><p>
Automated regression tests. In particular, the fuzz tests often indicate
"real life" problems that are otherwise hard to find.
</p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp21444028"></a>1.6.2. What does the Buildbot do?</h3></div></div></div><p>
The Buildbot will do the following (to a different degree on the different
platforms):
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
checkout from the source repository
</p></li><li class="listitem"><p>
build
</p></li><li class="listitem"><p>
create binary package(s) / installer
</p></li><li class="listitem"><p>
create source package (and check completeness)
</p></li><li class="listitem"><p>
run regression tests
</p></li></ul></div><p>
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.
</p><p>
The Buildbot runs on a platform collection that represents the different
"platform specialties" quite well:
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Windows XP x86 (Win32, little endian, VS 9)
</p></li><li class="listitem"><p>
Windows XP x86-64 (Win64, little endian, VS 9)
</p></li><li class="listitem"><p>
Ubuntu x86-64 (Linux, little endian, gcc)
</p></li><li class="listitem"><p>
Solaris SPARC (Solaris, big endian, gcc)
</p></li><li class="listitem"><p>
Mac OS-X PPC (BSD, big endian, gcc)
</p></li><li class="listitem"><p>
Mac OS-X x86 (BSD, little endian, gcc)
</p></li></ul></div><p>
Each platform is represented at the status page by a single column, the
most recent entries are at the top.
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ChIntroReleases.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ChapterIntroduction.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ChIntroHelp.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.5. Releases and distributions </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.7. Reporting problems and getting help</td></tr></table></div></body></html>
|