Filter
Top Products
build associate. A TeamConnection part that is
not an input to or an output from a build. An
example of such a part is a read.me file.
build cache. A directory that the build processor
uses to enhance performance.
build dependent. A TeamConnection part that is
needed for the compile operation to complete, but
it will not be passed directly to the compiler. An
example of this is an include file. See also
dependencies
.
builder. An object that can transform one set of
TeamConnection parts into another by invoking
tools such as compilers and linkers.
build event. An individual step in the build of an
application, such as the compiling of hello.c into
hello.obj.
build input. A TeamConnection part that will be
used as input to the object being built.
build output. A TeamConnection part that will be
generated output from a build, such as an .obj or
.exe file.
build pool. A group of build servers that resides
in an environment. The environment in which
several build servers operate. Typically, several
servers are set up for each environment that the
enterprise develops applications for.
build scope. A collection of build events that
implement a specific build request. See also
build
event
.
build script. An executable or command file that
specifies the steps that should occur during a
build operation. This file can be a compiler, a
linker, or the name of a .cmd file you have written.
build server. A program that invokes the tools,
such as compilers and linkers, that construct an
application.
build target. The name of the part at the top of
the build tree which is the final output of a build.
TeamConnection uses the build target to
determine the scope of the build. See also
build
tree
.
build tree. A graphical representation of the
dependencies that the parts in an application have
on one another. If you change the relationship of
one part to another, the build tree changes
accordingly.
C
change control process. The process of limiting
and auditing changes to parts through the
mechanism of checking parts in and out of a
central, controlled, storage location. Change
control for individual releases can be integrated
with problem tracking by specifying a process for
the release that includes the tracking subprocess.
check in. The return of a TeamConnection part
to version control.
check out. The retrieval of a version of a part
under TeamConnection control. In non-concurrent
releases, the check out operation does not allow a
second user to check out a part until the first user
has checked it back in.
child component. Any component in a
TeamConnection family, except the root
component, that is created in reference to an
existing component. The existing component is the
parent component, and the new component is the
child component. A parent component can have
more than one child component, and a child
component can have more than one parent
component. See also
component
and
parent
component
.
child part. Any part in a build tree that has a
parent defined. A child part can be input, output,
or dependent. See also
part
and
parent part
.
client. A functional unit that receives shared
services from a server. Contrast with
server
.
collision record. A status record associated with
a work area or driver, a part, and one of the
following:
314 User’s Guide