build/buildbot/config/Linux_GTK_STL_trunk.xml

   1 <?xml version="1.0" encoding="utf-8"?>
   2
   3 <!--
   4     Name:       ravnsgaard.xml
   5     RCS-ID:     $Id$
   6     Licence:    wxWidgets licence
   7
   8     There is one xml file such as this per build slave containing a <build>
   9     element for each build the slave runs. Each <build> corresponds to a
  10     column in the waterfall display.
  11
  12     For full documentation see:
  13     http://www.wxwidgets.org/wiki/index.php/Development:_Buildbot
  14 -->
  15
  16 <bot xmlns:xi="http://www.w3.org/2001/XInclude">
  17
  18 <!--
  19     Common declarations.
  20 -->
  21 <xi:include href="include/defs.xml"/>
  22
  23 <!--
  24     Notes:
  25
  26     The elements marked 'Unique' below must be unique across all builds on
  27     all slaves.
  28
  29     If a build is currently failing because of something other than a bug in
  30     wxWidgets, e.g. out of space or missing libs, then comment it out, or
  31     add '** Ignore **' to the beginning of the <name>, so that wxWidgets
  32     developers know not to waste time investigating.
  33 -->
  34 <build>
  35     <!--
  36         Unique. Appears as the title in the waterfall display.
  37     -->
  38     <name>Linux i386 wxGTK trunk STL debug</name>
  39
  40     <!--
  41         Unique. The name of a directory for the bulid.
  42     -->
  43     <builddir>ravnsgaard_wxgtk_debug</builddir>
  44
  45     <!--
  46         The name of a scheduler that will trigger this build. common.xml
  47         currently defines:
  48
  49         * 'trunk_quick' and 'stable_quick'. These trigger a build after
  50           every source change on the trunk and stable branches respectively.
  51
  52         * Weekly schedulers that fire once a week. There is one of these
  53           for every half hour of the week, e.g. you have monday_0600,
  54           monday_0630, etc..
  55
  56         * Daily schedulers that fire once a day. There is also one of these
  57           for every half hour, e.g. daily_0600, daily_0630, etc..
  58
  59         An empty <scheduler/> element takes its value from the previous build
  60         incremented in the following way:
  61
  62         * Weekly schedulers are incremented by a day, monday_0600 becomes
  63           tuesday_0600, and at the end of the week the time is also bumped by
  64           an hour, saturday_0600 becomes sunday_0700.
  65
  66         * Daily scheduler are incremented by an hour.
  67
  68         The <scheduler> element can be omitted, in which case the build
  69         never runs automatically, but can still be triggered manually.
  70         Or you can use several, e.g. you could use two weekly schedulers
  71         that fire on different days to have a build run twice a week.
  72     -->
  73     <scheduler>daily_0600</scheduler>
  74
  75     <!--
  76         The meaning of <sandbox> is specific to the build slave. There
  77         should be a comment in the slave's configuration file saying if they
  78         are allowed or required. On the testdrive it specifies the remote
  79         machine that will run the bulid.
  80     -->
  81     <sandbox>debug</sandbox>
  82
  83     <!--
  84         You can override the make command the compile steps will use using
  85         this <make> element, if omitted defaults to 'make'. For Windows
  86         builds this becomes the place to put build options as there is no
  87         configure step.
  88     -->
  89     <!-- <make>nmake -f makefile.vc SHARED=1 CPPUNIT_CFLAGS=-I\cppunit\include CPPUNIT_LIBS=cppunit.lib</make> -->
  90
  91     <!--
  92         The build steps.
  93     -->
  94     <steps>
  95         <!--
  96             Check out the sources, by default the trunk branch. Or for a
  97             particular branch or tag, e.g.:
  98                 <checkout branch="{$STABLE_BRANCH}"/>
  99                 <checkout branch="branches/WX_2_6_BRANCH"/>
 100         -->
 101         <checkout/>
 102
 103         <!--
 104             A <shellcommand> build step can be used anywhere you need to run
 105             arbitrary commands not covered by the standard build steps.
 106             <haltOnFailure/> specifies that the whole build fails if this
 107             step fails, without it it continues with the next step anyway.
 108         -->
 109         <shellcommand>
 110             <description>setting up</description>
 111             <descriptionDone>set up</descriptionDone>
 112             <haltOnFailure/>
 113             <command>setup-script</command>
 114         </shellcommand>
 115
 116         <!--
 117             Configure. Options and environment variables can be added with
 118             the 'options' attribute:
 119                 <configure options="-with-foobar CC=cc CXX=CC"/>
 120             Omitted for Windows builds.
 121         -->
 122         <configure options="--with-gtk --enable-debug --enable-stl --enable-std_iostreams --enable-std_string --disable-compat28">
 123
 124         <!--
 125             Compile the wxWidgets library, subdirectories and tests.
 126
 127             Takes the following attributes which can all be either 'true' or
 128             'false':
 129                 wx          - build the library
 130                 samples     - build the samples
 131                 utils       - build the utils
 132                 demos       - build the demos
 133                 contrib     - build the contrib
 134                 tests       - build the tests
 135                 msw         - the library makefile is under build\msw
 136                 gui         - if 'false' builds only a subset of the above
 137
 138             The attributes usually default to the right values.
 139         -->
 140         <compile-all/>
 141
 142         <!--
 143             Run the test suites.
 144         -->
 145         <run-tests/>
 146     </steps>
 147 </build>
 148
 149 <build>
 150     <name>Linux i386 wxGTK trunk stl std::string std::iostream release</name>
 151
 152     <builddir>ravnsgaard_wxgtk_release</builddir>
 153
 154     <scheduler>daily_1800</scheduler>
 155
 156     <sandbox>release</sandbox>
 157
 158     <steps>
 159         <checkout/>
 160
 161         <shellcommand>
 162             <description>setting up</description>
 163             <descriptionDone>set up</descriptionDone>
 164             <haltOnFailure/>
 165             <command>setup-script</command>
 166         </shellcommand>
 167
 168         <configure options="--with-gtk --disable-debug --enable-stl --enable-std_iostreams --enable-std_string --disable-compat28">
 169
 170         <compile-all/>
 171
 172         <run-tests/>
 173     </steps>
 174 </build>
 175
 176 </bot>
 177