Cleanup ACE_HAS_PTHREAD_SIGMASK_PROTOTYPE, all platforms support it so far as I can...
[ACE_TAO.git] / ACE / docs / bczar / privileges.html
blob6738dd29f7b8c83838aac8f3ef32202b4ce1a6a6
1 <!-- -->
3 <html>
4 <head>
5 <title> Build Czar powers </title>
6 </head>
7 <center><h1>Powers with the Build Czar</h1></center>
8 <P>
9 This document grants extensive privileges and powers to the Czar,
10 but those privileges impose several responsibilities that must be fulfilled,
11 failure to do so may result in some form of revolution
12 (picture a firing squad).
13 </P>
15 <P>
16 Previous generations of the honorable royal family have automated
17 the build process as much as possible, but all machines require attention:
18 the build Czar must keep a constant vigil, lest some runaway process
19 stops working and a critical bug escapes into the wild.
20 </P>
22 <P>Typically a runaway build is detected because on its next
23 execution an email indicating that the build is
24 <CODE>DISABLED</CODE>
25 is received.
26 The same email is also sent when a build is abruptly terminated (for
27 example because the machine running the build crashed).
28 Most of the time,
29 a test is not making progress and must be terminated,
30 the build then runs to completion.
31 If the machine crashed then it is necessary to go into the build
32 directory and remove the
33 <CODE>auto_compile/.disable</CODE>
34 file, so the next execution can complete successfully.
35 Occasionally the build fails because there is a CVS conflict,
36 there is not enough disk space or some similar problem,
37 in these cases the build Czar is encouraged to request advised
38 from previous generations in the royal family they will
39 be happy to come back from retirement to provide advice and help
40 if needed.
41 </P>
42 <P>The build Czar should also investigate the errors and warnings
43 reported by a build,
44 contact the person or persons responsible for the failed build and
45 prompt them to fix the situation. If that process above fails the
46 build Czar should request help from a volunteer or proceed to fix
47 the problem himself/herself. If there is no available
48 backup/volunteer and the build Czar is busy, he/she will be
49 forced to excomunicate the original developer and report him or
50 her to the highest court of the land for whatever punishment is
51 deemed appropriate (lashing or bone breaking where not prohibited
52 by law).
53 </P>
54 <P>It is extremely important to fix broken builds within the day,
55 otherwise the errors tend to accumulate and once the process
56 breaks down it is extremely hard to recover,
57 in other words,
58 the term as a build Czar can extend beyond your expectations if
59 the builds are not clean again.
60 </P>
61 <hr>
62 </html>