platform-ui-home/builds/index.html

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.3 - (view) (download) (as text)

1 : dpollock 1.1 <html>
2 :     <head>
3 :     <title>Builds (Platform-UI)</title>
4 :     <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
5 :     <link rel="stylesheet" href="http://dev.eclipse.org/default_style.css" type="text/css">
6 :     </head>
7 :    
8 :     <body bgcolor="#FFFFFF" text="#000000">
9 :    
10 : dpollock 1.3 <table border=0 cellspacing=5 cellpadding=2 width="100%">
11 :     <tr>
12 :     <td align=left width="72%">
13 :     <font class=indextop>Builds</font><br>
14 :     <font class=indexsub>platform user interface</font>
15 :     </td>
16 :     <td width="28%">
17 :     <img src="http://dev.eclipse.org/images/Idea.jpg" height=86 width=120 alt="Eclipse documentation banner">
18 :     </td>
19 :     </tr>
20 :     </table>
21 :     <table border=0 cellspacing=5 cellpadding=2 width="100%">
22 : dpollock 1.1 <tr>
23 : dpollock 1.3 <td align=LEFT valign=TOP bgcolor="#0080C0">
24 :     <b><font color="#FFFFFF" face="Arial,Helvetica">Topics</font></b>
25 :     </td>
26 : dpollock 1.1 </tr>
27 : dpollock 1.3 <tr>
28 :     <td width="98%">
29 :     <b>Topics</b>
30 :     <ul>
31 :     <li><a href="#BUILDS">Build Submissions</a></li>
32 :     <li><a href="#INSTALLING">Installing Release Engineering Tools</a></li>
33 :     <li><a href="#RELENGMAP">Making a Build Submission with Release
34 :     Engineering Tools</a></li>
35 :     <li><a href="#CVSMAP">Making a Build Submission with CVS Only</a></li>
36 :     <li><a href="#RECOVERY">Recovery Builds</a></li>
37 :     </ul>
38 :     </td>
39 :     </tr>
40 :     </table>
41 :     <a name="BUILDS">
42 :     <table border=0 cellspacing=5 cellpadding=2 width="100%">
43 :     <tr>
44 :     <td align=LEFT valign=TOP bgcolor="#0080C0">
45 :     <b><font color="#FFFFFF" face="Arial,Helvetica">Build Submissions</font></b>
46 :     </td>
47 :     </tr>
48 :     <tr>
49 :     <td width="98%">
50 :     <p>Build submissions are done before every integration build and
51 :     milestone build. Integration builds typically occur on Tuesday. Please
52 :     see the <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-releng-home/index.html">Platform
53 :     Release Engineering</a> page for more information. We do our build
54 :     submission for an 8 a.m. build, at 4 p.m. the previous day.</p>
55 :     <p>If you miss the cut-off for the official build submission, but
56 :     it is still before the build has started, then you can do your own build
57 :     submission to make sure your fix gets into the build.</p>
58 :     <p>A warning email should be sent to "platform-ui-dev@eclipse.org" (or
59 :     all committers) at the beginning of the days on which an official build
60 :     submission is to occur, or if you do your own build submission.</p>
61 :     </tr>
62 :     </table>
63 :     <a name="INSTALLING">
64 :     <table border=0 cellspacing=5 cellpadding=2 width="100%">
65 : dpollock 1.1 <tr>
66 : dpollock 1.3 <td align=LEFT valign=TOP bgcolor="#0080C0">
67 :     <b><font color="#FFFFFF" face="Arial,Helvetica">Installing the Release Engineering Tool</font></b>
68 :     </td>
69 :     </tr>
70 :     <tr>
71 :     <td>
72 : dpollock 1.1 <p>The Platform-UI team suggests that the Release Engineering (releng)
73 :     tool be installed before doing a build submission. It reduces the
74 :     chance of error.</p>
75 :     <ol>
76 :     <li>Exit Eclipse (if running)</li>
77 : dpollock 1.2 <li>Download the <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-releng-home/org.eclipse.releng.tools_2.1.0.zip">releng tool</a>.</li>
78 : dpollock 1.1 <li>Unzip the tool into your <code>plugins</code> directory.</li>
79 :     <li>Start Eclipse</li>
80 :     </ol>
81 : dpollock 1.3 </td>
82 :     </tr>
83 :     </table>
84 :     <a name="RELENGMAP">
85 :     <table border=0 cellspacing=5 cellpadding=2 width="100%">
86 :     <tr>
87 :     <td align=LEFT valign=TOP bgcolor="#0080C0">
88 :     <b><font color="#FFFFFF" face="Arial,Helvetica">Making a Build Submission with the Release Engineering Tool</font></b>
89 :     </td>
90 :     </tr>
91 :     <tr>
92 :     <td>
93 : dpollock 1.1 <p>Before performing an build submission, it is the responsibility of
94 :     the submitter to verify that the UI tests all pass. To perform a
95 :     submission using the releng tool, please do as follows:</p>
96 :     <ol>
97 :     <li>Select the project you need to version, and select "Team >
98 :     Release".</li>
99 :     <li>Supply the name of the release. Our convention is to use vYYYYMMDD,
100 :     where the date is the day of the build. If the name is already in use,
101 :     then use a letter suffix (i.e., a, b, c, etc.).</li>
102 :     <li>The synchronize view will open showing the changes in the file
103 :     "<code>ui.map</code>".</li>
104 :     <li>Continue to version all of the packages that you need.</li>
105 :     <li>When you are done, commit the changes to "<code>ui.map</code>".
106 :     </ol>
107 : dpollock 1.3 </td>
108 :     </tr>
109 :     </table>
110 :     <a name="CVSMAP">
111 :     <table border=0 cellspacing=5 cellpadding=2 width="100%">
112 :     <tr>
113 :     <td align=LEFT valign=TOP bgcolor="#0080C0">
114 :     <b><font color="#FFFFFF" face="Arial,Helvetica">Making a Build Submission with CVS Only</font></b>
115 :     </td>
116 :     </tr>
117 :     <tr>
118 :     <td>
119 :     <p>To do a build submission using CVS, please do as follows:</p>
120 : dpollock 1.1 <ol>
121 :     <li>Tag all projects you have changed with the name of the release. Our
122 :     convention is to use vYYYYMMDD, where the date is the day of the build.
123 :     If the name is already in use, then use a letter suffix (i.e., a, b, c,
124 :     etc.).</li>
125 :     <li>Checkout "org.eclipse.releng".</li>
126 :     <li>Open "<code>maps/ui.map</code>".</li>
127 :     <li>Change the version(s) of the project(s) you have tagged.</li>
128 :     <li>Save the map.</li>
129 :     <li>Commit your changes to the map to CVS.</li>
130 :     </ol>
131 : dpollock 1.3 <p>
132 :     </td>
133 :     </tr>
134 :     </table>
135 :     <a name="RECOVERY">
136 :     <table border=0 cellspacing=5 cellpadding=2 width="100%">
137 :     <tr>
138 :     <td align=LEFT valign=TOP bgcolor="#0080C0">
139 :     <b><font color="#FFFFFF" face="Arial,Helvetica">Recovery Builds</font></b>
140 : dpollock 1.1 </td>
141 : dpollock 1.3 </tr>
142 :     <td>
143 :     <p>In the event of a test failure, our team must respond to
144 :     <a href="mailto:eclipse-dev@eclipse.org">eclipse-dev</a> with one of two
145 :     responses. We can say that we want a recovery build the following day.
146 :     Alternatively, we can say that the test failure is not significant, and
147 :     that the quality of the build should not be affected. (In either case, a
148 :     bug should likely be entered into the bug database.)</p>
149 :     <p>A recovery build can also be requested if there is a problem affecting
150 :     the usability of the build. This problem should make the build unusable
151 :     for testing and development use.</p>
152 :     <p>For a recovery build, the map will need to be updated to include our
153 :     fixes. This can either be everything on the head in CVS, or just the
154 :     particular fixes we need. The former should only be done if no risky
155 :     changes have gone onto the head since the last (i.e., the failed) build
156 :     submission.</p>
157 :     </td>
158 :     <tr>
159 : dpollock 1.1 </tr>
160 :     </table>
161 :     </body>
162 :     </html>