<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Buildbot on To Linux and beyond !</title>
    <link>https://home.regit.org/tags/buildbot/</link>
    <description>Recent content in Buildbot on To Linux and beyond !</description>
    <generator>Hugo</generator>
    <language>fr</language>
    <lastBuildDate>Fri, 20 Sep 2013 10:56:26 +0000</lastBuildDate>
    <atom:link href="https://home.regit.org/feed/tags/buildbot/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Adding a force build to all builders</title>
      <link>https://home.regit.org/2013/09/adding-a-force-build-to-all-builders/</link>
      <pubDate>Fri, 20 Sep 2013 10:56:26 +0000</pubDate>
      <guid>https://home.regit.org/2013/09/adding-a-force-build-to-all-builders/</guid>
      <description>&lt;p&gt;Recent versions of &lt;a href=&#34;http://buildbot.net/&#34;&gt;buildbot&lt;/a&gt;, the continuous integration framework don’t allow by default the force build feature.&lt;br&gt;
This feature can be used to start a build on demand. It is really useful when you’ve updated the build procedure or when you want to test new branches.&lt;/p&gt;
&lt;p&gt;It was a little tricky to add it, so I decided to share it. If &lt;em&gt;c&lt;/em&gt; is the name of the configuration you build in your master.cfg, you can add after all builders declarations:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
