[Dart] Proposed changes to Nightly targets
Miller, James V (CRD)
millerjv at crd.ge.com
Tue, 24 Jul 2001 10:21:49 -0400
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_000_01C1144B.F9DCE2B0
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C1144B.F9DCE2B0"
------_=_NextPart_001_01C1144B.F9DCE2B0
Content-Type: text/plain;
charset="iso-8859-1"
Ken, Bill, and I were discussing changing Dart in the following ways:
1. Move the dashboards start time from 3am EST to 11pm EST
Motivation:
This would allow people in Europe to submit dashboards that they can use. They could start
their builds at 6am and hopefully finish before they got into work.
Solution:
Modify existing cron jobs on servers to open/close the dashboard. Clients still have the
flexibility to run their jobs at a time that is convenient for them. But we should strive to have
results on the Dashboards early enough to be useful to Europe.
Modify Update.tcl to specify a different time for an update
We should probably parameterize Update.tcl so that a given project can decide for itself when
Nighly dashboards will be done.
Impact:
Eastern US would have to check in changes to be tested by nightly dashboard to 11pm. Western
US would have to check in changes to be tested by nightly dashboard 8pm.
Does this impact dashboard rollups, navigations, or datestamps? I think datestamps are based
on GMT. So moving from 3am EST to 11pm EST will not cause a change in date in GMT.
2. make Nightly should do an Update
Motivation:
Clients current have to do a
make DashboardStart
make Nightly
While servers have to do a
make DashboardStart
make DashboardEnd
This will be confusing to people setting up clients because they need to run a server
operation (DashboardStart) before they do a client operation (make Nightly) but they never run the
matching server operation DashboardEnd.
Solution:
"make Nightly" target should always do an update.
Clients can then just do a "make Nightly".
Servers would still do
make DashboardStart
make DashboardEnd
make DashboardStart would still generate Update.xml for the server's Dashboard tree
Client's should generate an Update.xml and put it in the Sites tree. This will allow us to
summarize the changes that appear for each build (Nightly or Experimental). This is vital for
Experimental builds (we can determine whether this is a continuous build and what changed) and is
nice for Nightly builds (so we can verify that all builds actually succeeded in performing the
update).
Overall, we are striving to separate the client operation from the server operation. So
people that just want to submit to the dashboard have the "simplest" task. People running Dart
servers, have a little more to do but there is a clear distinction on what is a client operation and
what is a server operation.
Impact:
Shared source builds would have multiple updates being run on the same tree. Probably not a
big deal since cvs should properly lock/unlock so one machine would do the update and the others
would have an up to date tree. We can finess this problem by building in some delays in our shared
source builds.
I'll attack these in the next few days. I may wait until we label our alpha for Insight before I
change Dart.
Jim Miller
_____________________________________
Visualization & Computer Vision
GE Corporate Research & Development
Bldg. KW, Room C218B
P.O. Box 8, Schenectady NY 12301
millerjv at crd.ge.com < mailto:millerjv at crd.ge.com <mailto:millerjv at crd.ge.com> >
(518) 387-4005, Dial Comm: 8*833-4005,
Cell: (518) 505-7065, Fax: (518) 387-6981
------_=_NextPart_001_01C1144B.F9DCE2B0
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4611.1300" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=420202613-24072001><FONT size=2>Ken, Bill, and I were
discussing changing Dart in the following ways:</FONT></SPAN></DIV>
<DIV><SPAN class=420202613-24072001><FONT size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=420202613-24072001><FONT size=2><STRONG>1. Move the dashboards
start time from 3am EST to 11pm EST</STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=420202613-24072001><FONT size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=420202613-24072001> <FONT
size=2><STRONG>Motivation:</STRONG></FONT></SPAN></DIV>
<DIV><SPAN
class=420202613-24072001> <FONT
size=2>This would allow people in Europe to submit dashboards that they can
use. They could start their builds at 6am and hopefully finish before they
got into work.</FONT></SPAN></DIV>
<DIV><SPAN class=420202613-24072001><FONT size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=420202613-24072001><STRONG><FONT size=2>
Solution:</FONT></STRONG>
<DIV><SPAN class=420202613-24072001><FONT size=2>
<DIV><SPAN class=420202613-24072001><FONT
size=2> Modify existing cron jobs on
servers to open/close the dashboard. Clients still have the flexibility to
run their jobs at a time that is convenient for them. But we should strive
to have results on the Dashboards early enough to be useful to
Europe.</FONT></SPAN></DIV>
<DIV><SPAN
class=420202613-24072001>
</SPAN></DIV>
<DIV><SPAN class=420202613-24072001><FONT
size=2> Modify Update.tcl to specify a
different time for an update</FONT></SPAN></DIV>
<DIV><SPAN class=420202613-24072001><FONT
size=2> </FONT></SPAN></DIV>
<DIV><SPAN class=420202613-24072001><FONT
size=2> We should probably
parameterize Update.tcl so that a given project can decide for itself when
Nighly dashboards will be done.</FONT></SPAN></DIV>
<DIV><SPAN class=420202613-24072001></SPAN> </DIV></FONT></SPAN></DIV>
<DIV><SPAN class=420202613-24072001></SPAN><STRONG><FONT size=2><SPAN
class=420202613-24072001>
</SPAN>Impact:</FONT></STRONG></SPAN></DIV></DIV>
<DIV><SPAN class=420202613-24072001><FONT
size=2> Eastern US would have to check
in changes to be tested by nightly dashboard to 11pm. Western US would have to
check in changes to be tested by nightly dashboard 8pm.</FONT></SPAN></DIV>
<DIV><SPAN class=420202613-24072001><FONT size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=420202613-24072001>
<FONT size=2>Does this impact dashboard rollups, navigations, or datestamps? I
think datestamps are based on GMT. So moving from 3am EST to 11pm EST will
not cause a change in date in GMT.</FONT></SPAN></DIV>
<DIV><SPAN class=420202613-24072001><FONT size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=420202613-24072001>
</SPAN><SPAN class=420202613-24072001><FONT size=2></FONT></SPAN></DIV>
<DIV><SPAN class=420202613-24072001><FONT size=2>
<DIV><SPAN class=420202613-24072001><FONT size=2><STRONG>2. make Nightly should
do an Update</STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=420202613-24072001><STRONG></STRONG></SPAN><SPAN
class=420202613-24072001><FONT size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=420202613-24072001> <FONT
size=2><STRONG>Motivation:</STRONG></FONT></SPAN></DIV>
<DIV><SPAN
class=420202613-24072001> Clients
current have to do a </SPAN></DIV>
<DIV><SPAN
class=420202613-24072001>
make DashboardStart</SPAN></DIV>
<DIV><SPAN
class=420202613-24072001>
make Nightly</SPAN></DIV>
<DIV><SPAN class=420202613-24072001></SPAN> </DIV>
<DIV><SPAN class=420202613-24072001>
While servers have to do a</SPAN></DIV>
<DIV><SPAN
class=420202613-24072001>
make DashboardStart</SPAN></DIV>
<DIV><SPAN
class=420202613-24072001>
make DashboardEnd</SPAN></DIV>
<DIV><SPAN class=420202613-24072001></SPAN> </DIV>
<DIV><SPAN class=420202613-24072001>
This will be confusing to people setting up clients because they need to run a
server operation (DashboardStart) before they do a client operation (make
Nightly) but they never run the matching server operation
DashboardEnd.</SPAN></DIV>
<DIV><SPAN class=420202613-24072001><FONT size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=420202613-24072001><STRONG>
Solution:</STRONG></SPAN></DIV>
<DIV><SPAN class=420202613-24072001>
"make Nightly" target should always do an update. </SPAN></DIV>
<DIV><SPAN class=420202613-24072001></SPAN> </DIV>
<DIV><SPAN class=420202613-24072001>
Clients can then just do a "make Nightly".</SPAN></DIV>
<DIV><SPAN class=420202613-24072001></SPAN> </DIV>
<DIV><SPAN class=420202613-24072001>
Servers would still do </SPAN></DIV>
<DIV><SPAN
class=420202613-24072001> make
DashboardStart</SPAN></DIV>
<DIV><SPAN
class=420202613-24072001> make
DashboardEnd</SPAN></DIV>
<DIV><SPAN class=420202613-24072001></SPAN> </DIV>
<DIV><SPAN class=420202613-24072001>
make DashboardStart would still generate Update.xml for the server's
<STRONG>Dashboard </STRONG>tree</SPAN></DIV>
<DIV><SPAN class=420202613-24072001></SPAN> </DIV>
<DIV><SPAN class=420202613-24072001>
Client's should generate an Update.xml and put it in the <STRONG>Sites</STRONG>
tree. This will allow us to summarize the changes that appear for each
build (Nightly or Experimental). This is vital for Experimental builds (we
can determine whether this is a continuous build and what changed) and is nice
for Nightly builds (so we can verify that all builds actually succeeded in
performing the update).</SPAN></DIV>
<DIV><SPAN class=420202613-24072001></SPAN> </DIV>
<DIV><SPAN class=420202613-24072001>
Overall, we are striving to separate the client operation from the server
operation. So people that just want to submit to the dashboard have the
"simplest" task. People running Dart servers, have a little more to do but
there is a clear distinction on what is a client operation and what is a server
operation.</SPAN></DIV>
<DIV><SPAN class=420202613-24072001></SPAN><SPAN
class=420202613-24072001></SPAN> </DIV>
<DIV><SPAN class=420202613-24072001> <FONT
size=2><STRONG>Impact:</STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=420202613-24072001><FONT
size=2> Shared source builds would
have multiple updates being run on the same tree. Probably not a big deal
since cvs should properly lock/unlock so one machine would do the update and the
others would have an up to date tree. We can finess this problem by building in
some delays in our shared source builds.</FONT></SPAN></DIV>
<DIV><SPAN class=420202613-24072001></SPAN> </DIV>
<DIV><SPAN class=420202613-24072001></SPAN> </DIV>
<DIV><SPAN class=420202613-24072001>I'll attack these in the next few days. I
may wait until we label our alpha for Insight before I change Dart.</SPAN></DIV>
<DIV><SPAN class=420202613-24072001></SPAN> </DIV></FONT></SPAN></DIV>
<DIV><SPAN class=420202613-24072001><FONT size=2></FONT></SPAN> </DIV>
<DIV><B><FONT face="Comic Sans MS" color=#000080>Jim
Miller</FONT></B> <BR><B><I><FONT face=Arial color=#ff0000
size=2>_____________________________________</FONT></I></B><I></I><BR><I></I><I><FONT
face=Arial color=#000000 size=1>Visualization & Computer Vision<BR>GE
Corporate Research & Development<BR>Bldg. KW, Room C218B<BR>P.O. Box 8,
Schenectady NY 12301<BR><BR></FONT><U><FONT face=Arial color=#0000ff
size=1>millerjv at crd.ge.com <<A
href="mailto:millerjv at crd.ge.com">mailto:millerjv at crd.ge.com</A>></FONT></U></I><BR><I><FONT
face=Arial color=#000000 size=1>(518) 387-4005, Dial Comm: 8*833-4005,
</FONT></I><BR><I><FONT face=Arial color=#000000 size=1>Cell: (518) 505-7065,
Fax: (518) 387-6981</FONT></I> </DIV><BR>
<DIV><FONT size=2></FONT> </DIV></BODY></HTML>
------_=_NextPart_001_01C1144B.F9DCE2B0--
------_=_NextPart_000_01C1144B.F9DCE2B0
Content-Type: application/octet-stream;
name="Miller, James V (CRD).vcf"
Content-Disposition: attachment;
filename="Miller, James V (CRD).vcf"
BEGIN:VCARD
VERSION:2.1
N:Miller;James
FN:Miller, James V (CRD)
ORG:CRD;ESL
TITLE:Computer Scientist
TEL;WORK;VOICE:*833-4005
TEL;WORK;VOICE:1 518 387-4005
ADR;WORK:;KW-C218B;P.O. Box 8;Schenectady;New York;12301;USA
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:KW-C218B=0D=0AP.O. Box 8=0D=0ASchenectady, New York 12301=0D=0AUSA
EMAIL;PREF;INTERNET:millerjv at crd.ge.com
REV:20010420T140329Z
END:VCARD
------_=_NextPart_000_01C1144B.F9DCE2B0--