|
1 |
|
2 From the Buildbot project page: |
|
3 |
|
4 > The BuildBot is a system to automate the compile/test cycle required by most |
|
5 > software projects to validate code changes. By automatically rebuilding and |
|
6 > testing the tree each time something has changed, build problems are |
|
7 > pinpointed quickly, before other developers are inconvenienced by the failure. |
|
8 > The guilty developer can be identified and harassed without human |
|
9 > intervention. By running the builds on a variety of platforms, developers who |
|
10 > do not have the facilities to test their changes everywhere before checkin |
|
11 > will at least know shortly afterwards whether they have broken the build or |
|
12 > not. Warning counts, lint checks, image size, compile time, and other build |
|
13 > parameters can be tracked over time, are more visible, and are therefore |
|
14 > easier to improve. |
|
15 > |
|
16 > The overall goal is to reduce tree breakage and provide a platform to run |
|
17 > tests or code-quality checks that are too annoying or pedantic for any human |
|
18 > to waste their time with. Developers get immediate (and potentially public) |
|
19 > feedback about their changes, encouraging them to be more careful about |
|
20 > testing before checkin. |
|
21 |
|
22 The webstatus display of mcabber buildbot is available at |
|
23 <http://wodka.lubin.pl:8010> there are several views accessible on the page |
|
24 showing information about current and past builds. Command output is logged so |
|
25 if there is a build problem You will be able to see the log files directly via |
|
26 the web interface. |
|
27 |
|
28 Anyone can join the buildbot farm. If You are interested in commiting Your |
|
29 resources to make sure that mcabber compiles across a wider range of platforms |
|
30 then please contact me via email at <netprobe@gmail.com> or jabber |
|
31 [mulander@uaznia.net](xmpp:mulander@uaznia.net). |
|
32 |
|
33 Contact mulander if You notice any problems with the Buildbot or the appropriate |
|
34 administrator if the problem relates to a specific Build slave. |
|
35 |
|
36 For now mcabber doesn't have any tests that the bot could automatically run but |
|
37 it's planned to add some in the long run. |
|
38 |
|
39 The mcabber-lm repository was setup first as it is supposed to be merged soon |
|
40 into the official repository. If time allows more build slaves will be setup for |
|
41 other forks of the project. |
|
42 |
|
43 This page will be constantly updated with more specific details. |
|
44 |