tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

formatting 

[Imported from Trac: page BuildbotPolicy, version 5]
zooko 2009-12-02 19:02:33 +00:00
parent 2a35bb9e65
commit 900c5ca9a8
1 changed files with 1 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
BuildbotPolicy.md

@ -1,6 +1,7 @@
There are two classes of builder for the [Tahoe Buildbot](http://allmydata.org/buildbot/): *Supported* and *Unsupported*. The buildbot policy has two parts: There are two classes of builder for the [Tahoe Buildbot](http://allmydata.org/buildbot/): *Supported* and *Unsupported*. The buildbot policy has two parts:
1. Packages are produced for *any* platform only when *all* of the supported platforms pass tests. This means that if, for example, the Windows platform starts failing unit tests, then we stop producing new .deb packages for Debian or Ubuntu. Also vice versa: if one of the Supported debian platforms fails its unit tests, then we won't produce a new Windows package from that version of the source code. 1. Packages are produced for *any* platform only when *all* of the supported platforms pass tests. This means that if, for example, the Windows platform starts failing unit tests, then we stop producing new .deb packages for Debian or Ubuntu. Also vice versa: if one of the Supported debian platforms fails its unit tests, then we won't produce a new Windows package from that version of the source code.
2. If a supported builder goes red then we fix it right away. 2. If a supported builder goes red then we fix it right away.
1. It could be we just committed a patch that breaks Tahoe in a way that makes a test fail on that builder. In this case we either: 1. It could be we just committed a patch that breaks Tahoe in a way that makes a test fail on that builder. In this case we either: