Icse2011 build maintenance

Hinweis der Redaktion

1. \n
2. \n
3. \n
4. \n
5. \n
6. \n
7. \n
8. \n
9. \n
10. \n
11. \n
12. \n
13. Cars have features like AC and Power windows...\nSoftware has features... Linux -> CPU freq scaling, pluggable module support\nYou need tools to build a car, and you also need tools...compilers and linkers...\n
14. Cars have features like AC and Power windows...\nSoftware has features... Linux -> CPU freq scaling, pluggable module support\nYou need tools to build a car, and you also need tools...compilers and linkers...\n
15. Cars have features like AC and Power windows...\nSoftware has features... Linux -> CPU freq scaling, pluggable module support\nYou need tools to build a car, and you also need tools...compilers and linkers...\n
16. Cars have features like AC and Power windows...\nSoftware has features... Linux -> CPU freq scaling, pluggable module support\nYou need tools to build a car, and you also need tools...compilers and linkers...\n
17. Cars have features like AC and Power windows...\nSoftware has features... Linux -> CPU freq scaling, pluggable module support\nYou need tools to build a car, and you also need tools...compilers and linkers...\n
18. Cars have features like AC and Power windows...\nSoftware has features... Linux -> CPU freq scaling, pluggable module support\nYou need tools to build a car, and you also need tools...compilers and linkers...\n
19. Cars have features like AC and Power windows...\nSoftware has features... Linux -> CPU freq scaling, pluggable module support\nYou need tools to build a car, and you also need tools...compilers and linkers...\n
20. \n
21. \n
22. \n
23. \n
24. \n
25. \n
26. \n
27. \n
28. \n
29. \n
30. \n
31. \n
32. \n
33. \n
34. \n
35. \n
36. \n
37. \n
38. devs: constantly have to rebuilt artifacts to test changes... bld sys incrementally updates builds\n\n\n
39. devs: constantly have to rebuilt artifacts to test changes... bld sys incrementally updates builds\n\n\n
40. devs: constantly have to rebuilt artifacts to test changes... bld sys incrementally updates builds\n\n\n
41. devs: constantly have to rebuilt artifacts to test changes... bld sys incrementally updates builds\n\n\n
42. devs: constantly have to rebuilt artifacts to test changes... bld sys incrementally updates builds\n\n\n
43. devs: constantly have to rebuilt artifacts to test changes... bld sys incrementally updates builds\n\n\n
44. devs: constantly have to rebuilt artifacts to test changes... bld sys incrementally updates builds\n\n\n
45. devs: constantly have to rebuilt artifacts to test changes... bld sys incrementally updates builds\n\n\n
46. devs: constantly have to rebuilt artifacts to test changes... bld sys incrementally updates builds\n\n\n
47. devs: constantly have to rebuilt artifacts to test changes... bld sys incrementally updates builds\n\n\n
48. devs: constantly have to rebuilt artifacts to test changes... bld sys incrementally updates builds\n\n\n
49. devs: constantly have to rebuilt artifacts to test changes... bld sys incrementally updates builds\n\n\n
50. devs: constantly have to rebuilt artifacts to test changes... bld sys incrementally updates builds\n\n\n
51. Firefox 3.0 was built and delivered incorrectly\nusers in a networked environment address/search bar broken\ndue to an incorrect version of the SQLite library being linked in build process\nFix was delivered 4 months late in a service pack (3.0.1)\n
52. Firefox 3.0 was built and delivered incorrectly\nusers in a networked environment address/search bar broken\ndue to an incorrect version of the SQLite library being linked in build process\nFix was delivered 4 months late in a service pack (3.0.1)\n
53. Firefox 3.0 was built and delivered incorrectly\nusers in a networked environment address/search bar broken\ndue to an incorrect version of the SQLite library being linked in build process\nFix was delivered 4 months late in a service pack (3.0.1)\n
54. Firefox 3.0 was built and delivered incorrectly\nusers in a networked environment address/search bar broken\ndue to an incorrect version of the SQLite library being linked in build process\nFix was delivered 4 months late in a service pack (3.0.1)\n
55. Firefox 3.0 was built and delivered incorrectly\nusers in a networked environment address/search bar broken\ndue to an incorrect version of the SQLite library being linked in build process\nFix was delivered 4 months late in a service pack (3.0.1)\n
56. Firefox 3.0 was built and delivered incorrectly\nusers in a networked environment address/search bar broken\ndue to an incorrect version of the SQLite library being linked in build process\nFix was delivered 4 months late in a service pack (3.0.1)\n
57. Firefox 3.0 was built and delivered incorrectly\nusers in a networked environment address/search bar broken\ndue to an incorrect version of the SQLite library being linked in build process\nFix was delivered 4 months late in a service pack (3.0.1)\n
58. Firefox 3.0 was built and delivered incorrectly\nusers in a networked environment address/search bar broken\ndue to an incorrect version of the SQLite library being linked in build process\nFix was delivered 4 months late in a service pack (3.0.1)\n
59. Firefox 3.0 was built and delivered incorrectly\nusers in a networked environment address/search bar broken\ndue to an incorrect version of the SQLite library being linked in build process\nFix was delivered 4 months late in a service pack (3.0.1)\n
60. Based on survey results...\n
61. \n
62. Studied 10 projects of different:\n- prog language (c, c++, java)\n- domain (web communications, compilers, RDBMS, IDE...)\n- dev methodology (open, proprietary)\n
63. \n
64. \n
65. \n
66. \n
67. \n
68. \n
69. \n
70. \n
71. \n
72. \n
73. \n
74. \n
75. \n
76. We find that the build system accounts for 9% of the build files in a project (median).\n- Small!\n
77. \n
78. \n
79. \n
80. \n
81. \n
82. \n
83. \n
84. \n
85. \n
86. \n
87. \n
88. \n
89. 1) churn of the build system is close to that of the source code (normalized)\n2) Prior research => High churn may produce bugs!\n
90. 1) churn of the build system is close to that of the source code (normalized)\n2) Prior research => High churn may produce bugs!\n
91. 1) churn of the build system is close to that of the source code (normalized)\n2) Prior research => High churn may produce bugs!\n
92. \n
93. \n
94. \n
95. \n
96. \n
97. \n
98. \n
99. \n
100. \n
101. \n
102. \n
103. \n
104. \n
105. \n
106. \n
107. \n
108. \n
109. \n
110. \n
111. \n
112. \n
113. \n
114. \n
115. \n
116. \n
117. \n
118. - measures strength of implication...\n
119. - measures strength of implication...\n
120. - measures strength of implication...\n
121. - measures strength of implication...\n
122. - measures strength of implication...\n
123. - measures strength of implication...\n
124. - measures strength of implication...\n
125. Counter intuitive and does not match with prior survey results (<12%)\n
126. - Mozilla is scary high\n- Eclipse-core and Jazz are considerably lower\n- Use of PDE build\n
127. - Mozilla is scary high\n- Eclipse-core and Jazz are considerably lower\n- Use of PDE build\n
128. - Mozilla is scary high\n- Eclipse-core and Jazz are considerably lower\n- Use of PDE build\n
129. - Mozilla is scary high\n- Eclipse-core and Jazz are considerably lower\n- Use of PDE build\n
130. \n
131. \n
132. - devs may not commit all changes in one revision\n
133. - devs may not commit all changes in one revision\n
134. - devs may not commit all changes in one revision\n
135. - devs may not commit all changes in one revision\n
136. - devs may not commit all changes in one revision\n
137. - devs may not commit all changes in one revision\n
138. - devs may not commit all changes in one revision\n
139. - devs may not commit all changes in one revision\n
140. - devs may not commit all changes in one revision\n
141. - devs may not commit all changes in one revision\n
142. - devs may not commit all changes in one revision\n
143. - devs may not commit all changes in one revision\n
144. - devs may not commit all changes in one revision\n
145. - devs may not commit all changes in one revision\n
146. - devs may not commit all changes in one revision\n
147. - devs may not commit all changes in one revision\n
148. - devs may not commit all changes in one revision\n
149. - devs may not commit all changes in one revision\n
150. - devs may not commit all changes in one revision\n
151. - devs may not commit all changes in one revision\n
152. - devs may not commit all changes in one revision\n
153. - devs may not commit all changes in one revision\n
154. - devs may not commit all changes in one revision\n
155. - devs may not commit all changes in one revision\n
156. - devs may not commit all changes in one revision\n
157. - devs may not commit all changes in one revision\n
158. - devs may not commit all changes in one revision\n
159. - Jazz src devs are often responsible for build dev\n- Git and Linux are less so\n
160. - Jazz distributes build work...\n
161. - Jazz distributes build work...\n
162. - Jazz distributes build work...\n
163. - Jazz distributes build work...\n
164. \n
165. Build maintenance is a nuisance for developers\nneed tools to help them to cope\ne.g., Jazz has tools, lowered build coupling to 4%\n
166. \n
167. \n
168. \n
169. \n
170. \n
171. \n
172. \n
173. \n
174. \n
175. \n
176. \n
177. \n
178. \n
179. \n
180. \n
181. Build maintenance is a nuisance for developers!\nneed tools to help them to cope!\n