Tape 004 - Clip 1
Short_Description:
Tara describing the bug fix chart
Vimeo_:
TranscriptText:
It was pretty green. green is good we always like to see green weve been having
problems with this build its Macintosh build Right now were in flames were in
flames burning and were trying to fix that The yellows represent builds in progress
The yellows that have red or green above them means that we killed the build and we
started again And this is how we keep track on cross platform basis of all changes that
are going in Heres uh time stamps of people who are checking in or who are trying to
check in and you can see after which point things start breaking lot of changes going in
right here and wham the build all died This is really nifty tool that Lloyd tab is the
original creator of various people have been tweaking it ever since You can do all kinds
of fun things with it HTML CDI scripting to generate lots of information see this looks
kind of familiar it just generated it pulled from the Bonsai information lots of inter
dependencies references So theres sort of like redundant information to make sure that
youve covered as many areas as possible Lots of developers never look at Bonsai the
only look at tinder box to see whats going on
Does red mean
The Build broke And we can look at the build to see why it broke Theres lit of errors
and you can click on the error and go and see in the build log exactly what happened So
we have syntax error in this file
Yeah We try and put as much information into this as possible
Well the build...and it will run even if you see long period of time when there are no
check ins like here well thats not that long period of time but theres periods where
the builds just kept going and unfortunately at that point they were still broken
19 .æ IL
Page
Netscape Documentary
Tape Don Milton Interview
Each box is separate build
It goes as far as it can and then it thinks about things for while and then recycles and
starts over picking up any additional changes that have gone in and hopefully those
changes have been completely fixed for why it was broken
Right So the thing with the pinter box is it does check out from the depository does
build uh reports the results thinks about things for while and settles down uh
basically give it little time out period so why not constantly getting. .over and over again
trying to space it out as much as possible and then it starts the whole thing all over again
And the last
part of this is...this bugs flat
Bug spot represents is all of the bugs that are currently logged into the products and
which will eventually correspond to change in the tree So at some point probably
starting next week on Monday every cheek in that we saw here will have an equivalent
bug number associated with it from this list Where you can see the bug number who its
assigned to what the actual bug is you can pick up bug
Right But not all bugs are build busters most of em arent The build bustage is usually
something that happens...its an accidental thing Right This would be for example if
you pick bug and SJS source OK Java script code needs sanitizing we need to make
sure..
What would bust the build was if in the process Brendan who its assigned to checking
in broke the build that would be trouble
Page
Netscape Documentary
Tape Don Milton Interview
Potential if you checked in bad stuff you would break the build and in this case we would
go smack him around little bit to fix it
So we use all these different components tools urn make up the vast chunk of the visible
development process
Right bunch of geeks sitting in their cubes hacking away until the wee hours of the
morning
problems with this build its Macintosh build Right now were in flames were in
flames burning and were trying to fix that The yellows represent builds in progress
The yellows that have red or green above them means that we killed the build and we
started again And this is how we keep track on cross platform basis of all changes that
are going in Heres uh time stamps of people who are checking in or who are trying to
check in and you can see after which point things start breaking lot of changes going in
right here and wham the build all died This is really nifty tool that Lloyd tab is the
original creator of various people have been tweaking it ever since You can do all kinds
of fun things with it HTML CDI scripting to generate lots of information see this looks
kind of familiar it just generated it pulled from the Bonsai information lots of inter
dependencies references So theres sort of like redundant information to make sure that
youve covered as many areas as possible Lots of developers never look at Bonsai the
only look at tinder box to see whats going on
Does red mean
The Build broke And we can look at the build to see why it broke Theres lit of errors
and you can click on the error and go and see in the build log exactly what happened So
we have syntax error in this file
Yeah We try and put as much information into this as possible
Well the build...and it will run even if you see long period of time when there are no
check ins like here well thats not that long period of time but theres periods where
the builds just kept going and unfortunately at that point they were still broken
19 .æ IL
Page
Netscape Documentary
Tape Don Milton Interview
Each box is separate build
It goes as far as it can and then it thinks about things for while and then recycles and
starts over picking up any additional changes that have gone in and hopefully those
changes have been completely fixed for why it was broken
Right So the thing with the pinter box is it does check out from the depository does
build uh reports the results thinks about things for while and settles down uh
basically give it little time out period so why not constantly getting. .over and over again
trying to space it out as much as possible and then it starts the whole thing all over again
And the last
part of this is...this bugs flat
Bug spot represents is all of the bugs that are currently logged into the products and
which will eventually correspond to change in the tree So at some point probably
starting next week on Monday every cheek in that we saw here will have an equivalent
bug number associated with it from this list Where you can see the bug number who its
assigned to what the actual bug is you can pick up bug
Right But not all bugs are build busters most of em arent The build bustage is usually
something that happens...its an accidental thing Right This would be for example if
you pick bug and SJS source OK Java script code needs sanitizing we need to make
sure..
What would bust the build was if in the process Brendan who its assigned to checking
in broke the build that would be trouble
Page
Netscape Documentary
Tape Don Milton Interview
Potential if you checked in bad stuff you would break the build and in this case we would
go smack him around little bit to fix it
So we use all these different components tools urn make up the vast chunk of the visible
development process
Right bunch of geeks sitting in their cubes hacking away until the wee hours of the
morning
