TFS Session 3 : Team Foundation Build

TFS – TEAM FOUNDATION BUILD VERSION (1.0)

MOUDLE NAME TEAM FOUNDATION BUILD

SUBMITTED FOR

Saudi Post

SUBMITTED BY

ARCOM

TFS COURSE – TEAM FOUNDATION BUILD MODULE

البريد السعودي – 4محاضرة

TFS – TEAM FOUNDATION BUILD Page | 2

1. TABLE OF CONTENT

1. TABLE OF CONTENT ................................................................................................................... 2

2. WHAT IS TEAM FOUNDATION BUILD? ........................................................................................ 3

3. WHAT IS BUILD PROCESS? ......................................................................................................... 3

4. WHAT HAPPEN WHEN BUILD RUN? ........................................................................................... 3

6. BUILD TRIGGER TYPE: ................................................................................................................ 4

7. BUILD DEFINITION ..................................................................................................................... 6

OVERVIEW ................................................................................................................................. 6

TOOL GUIDELINES ...................................................................................................................... 6




2. WHAT IS TEAM FOUNDATION BUILD?

The team foundation build provides a mechanism to implement continuous

building and testing using the Build function

helps to Prevent "work on my box" problem, prove you can build your app

build system consists of two constructs: Build controller and the Build agents.

BUILD CONTROLLER BUILD AGENT

job is to queue build requests and

send them to the "most available"

build agent.

job is to perform the actual build

3. WHAT IS BUILD PROCESS?

contains your instructions about which code projects to compile

what actions trigger a build, what tests to run and other procedures

Build process also part of the traceability mechanism, build brings together

many of the artifacts that are created and stored in TFS.

Assuming developers associate source code with work items on check-in,

Team Build has the ability to report on the changes in each build - both

source code changes and work item changes as well as test results

4. WHAT HAPPEN WHEN BUILD RUN?

1. Does a 'GetLatest'

2. Labels the code in version control

3. Compile the code

4. Optionally run tests

5. Copy the binaries to a "drop" folder




6. BUILD TRIGGER TYPE: There are 5 types of how the build is triggered

1. MANUAL TRIGGER

run only when the build is explicitly queued by a user in Visual Studio,

Eclipse or by the tfsbuild.exe command

useful when first creating the build definition to ensure that everything is

working correctly before turning to one of the other triggers

2. CONTINOUS INTEGRATION

trigger monitors every check-in affecting the build files and causes a new

build to be queued

by performing a build for every check-in, it is easy to see which check-in

caused a problem (“Who broke the build?”)

3. SCHEDULE

define a time on a weekly schedule that a build is queued

optionally, you can make new build even if no changes happened since

the last build




4. ROLLING BUILDS

Same as continuous integration but group together several check-ins to

ensure that the build controller never has a large queue of builds waiting

to be processed

Optionally, a time interval can be specified to control the minimum

duration that must have passed before a new build is triggered

reduce the number of builds performed and, therefore, can guarantee a

time in which the results of a particular check-in will be known

5. GATED CHECK-IN

Any check-ins are first automatically stored as a shelveset

Build server then merges the code as it was before the check-in was

attempted with the code stored in the shelveset.

Only when the build is successful, the changes then committed to the

version control repository

commonly used when organizations wish to ensure that code committed

to the main codebase meets certain requirements




7. BUILD DEFINITION

OVERVIEW

Place where you put all configuration about build, queue processing type or

trigger, workspace items included into build and the drop folder location

OVERVIEW

A. QUEUE PROCESSING

ENABLED PAUSED DISABLED

Build will be in queue,

using manual or auto

trigger, controller will

run in order of priory

Same as enabled but

run will be manually

forced by

administrator

never be used to

queue or start a build.

Used to archive build

definition

B. STAGING LOCATION

OPTION-1: don't copy to output

OPTION-2: copy to drop folder ( \\server\share )

OPTION-3: copy output to server (find in build project portal)

C. PROCESS:

BUILD SECTION: choose solution to be build

TOOL GUIDELINES

1. Add new definition

2. Source settings

3. Staging location (drop folder)

4. Process

5. Queue new build

6. Add to favourite build

7. Clone build definition

8. Edit build definition

9. View controller queue

Education

TFS Session 3 : Team Foundation Build