build/buildbot/config/example.xml

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