<br><font size=2 face="sans-serif">So far, Peter is doing the following
numbering scheme: 38, 38.1, 38.2. Where 38 is the original build for rev
38, and 38.N is an Nth attempt to <b>re</b>build it. </font>
<br><font size=2 face="sans-serif">And saying "no" to force build
comments looks like a consensus opinion. </font>
<br>
<br><font size=2 face="sans-serif">Alex</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Jeremy Stell-Smith"
<jeremystellsmith@gmail.com></b> </font>
<br><font size=1 face="sans-serif">Sent by: cruisecontrolrb-developers-bounces@rubyforge.org</font>
<p><font size=1 face="sans-serif">02/06/2007 11:17 AM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">"Peter Zhao" <qzhao@thoughtworks.com></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">cruisecontrolrb-developers@rubyforge.org</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [Cruisecontrolrb-developers] questions
of force build story</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=3>I would vote for either <br>
<br>
on build 38 if the build is force, the new build is <br>
<br>
build 38 (forced)<br>
and every build after that just overwrites build 38 (forced)<br>
<br>
or<br>
<br>
build 38 (forced 1 time)<br>
build 38 (forced 2 times) <br>
build 38 (forced 3 times)<br>
etc<br>
<br>
and I agree, I don't think we should have a comment on a force build, I
think it's unnecessary complexity<br>
<br>
jeremy<br>
</font>
<br><font size=3>On 2/6/07, <b>Peter Zhao</b> <</font><a href=mailto:qzhao@thoughtworks.com><font size=3 color=blue><u>qzhao@thoughtworks.com</u></font></a><font size=3>>
wrote:</font>
<br><font size=2 face="sans-serif"><br>
Hi,</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
I have some questions about the force build story:</font><font size=3>
<br>
</font><font size=2 face="sans-serif"><br>
- What build label should be used if it is a force build? So far the force
build just calls project.build to build latest version of svn and therefore
the build label is something like "build #{svn_latest_version}"
which means the force build always replace the latest build result if it
exists. </font><font size=3><br>
</font><font size=2 face="sans-serif"><br>
- Where should the comment of force build be used? in the build label or
in a log file? Is the comment really needed? I feel it is not very useful
to collect the comment when force build as the purpose of force build is
"</font><font size=3>so that I can verify a build status (broken)
is consistently reproducible for the code base. </font><font size=2 face="sans-serif">".</font><font size=3>
<br>
</font><font size=2 face="sans-serif"><br>
Any opinions?</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
Thanks</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
Peter Zhao</font><font size=3><br>
_______________________________________________<br>
Cruisecontrolrb-developers mailing list</font><font size=3 color=blue><u><br>
</u></font><a href="mailto:Cruisecontrolrb-developers@rubyforge.org"><font size=3 color=blue><u>Cruisecontrolrb-developers@rubyforge.org</u></font></a><font size=3 color=blue><u><br>
</u></font><a href="http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers" target=_blank><font size=3 color=blue><u>http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers
</u></font></a><font size=3><br>
</font>
<br><tt><font size=2>_______________________________________________<br>
Cruisecontrolrb-developers mailing list<br>
Cruisecontrolrb-developers@rubyforge.org<br>
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers<br>
</font></tt>
<br>