a·gen·tic a·gil·i·ty

Do you know the minimum builds to create on any branch?

Explains the essential three build types—Gate, CI, and Nightly—needed per branch to ensure code quality, test coverage, and collaboration in team projects.

Published on
2 minute read
Image
https://nkdagility.com/resources/wPA1p1UQ6Bi
Subscribe

Do you know the minimum builds to create on any branch?

When creating projects one of the only ways that you have of proving that it works and is a viable solution is to build it. This is easy when you only have one developer and that developer will be the only one using a solution. But what if you have 2 developers? How do you prove that one developers code works with the other? The answer is build servers. These build servers take specific code away to another computer and build it there.

Updated 29th March 2010: I was missing an intro for this one.


You should always have three builds on your team project. These should be setup and tested using an empty solution before you write any code at all.

Do you know the minimum builds to create on any branch?

Figure: Three builds named in the format [TeamProject].[AreaPath]_[Branch].[Gate|CI|Nightly] for every branch.

These builds should use the same XAML build workflow; however you may set them up to run a different set of tests depending on the time it takes to run a full build.

Do you know the minimum builds to create on any branch?

Figure: You can control what tests are run and what data is collected while they are running.

Note: We do not run all the tests every time because of the time consuming nature of running some tests, but ALL tests should be run overnight.

Note: If you had a really large project with thousands of tests including long running Load tests you may need to add a Weekly build to the mix.

Do you know the minimum builds to create on any branch?

Figure: Bad example, you can’t tell what these builds do if they are in a larger list

Do you know the minimum builds to create on any branch?

Figure: Good example, you know exactly what project, branch and type of build these are for.

Technorati Tags: SSW   SSW Rules   ALM   TFBS   VS 2010

Software Development Continuous Integration
Subscribe

Related Blog

No related videos found.

Connect with Martin Hinshelwood

If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.

Our Happy Clients​

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.​

CR2

Brandes Investment Partners L.P. Logo

Brandes Investment Partners L.P.

Jack Links Logo

Jack Links

Ericson Logo

Ericson

Microsoft Logo

Microsoft

Boxit Document Solutions Logo

Boxit Document Solutions

Teleplan Logo

Teleplan

MacDonald Humfrey (Automation) Ltd. Logo

MacDonald Humfrey (Automation) Ltd.

New Signature Logo

New Signature

Healthgrades Logo

Healthgrades

Slicedbread Logo

Slicedbread

Flowmaster (a Mentor Graphics Company) Logo

Flowmaster (a Mentor Graphics Company)

Deliotte Logo

Deliotte

NIT A/S

Milliman Logo

Milliman

Freadom Logo

Freadom

Big Data for Humans Logo

Big Data for Humans

ALS Life Sciences Logo

ALS Life Sciences

Ghana Police Service Logo

Ghana Police Service

New Hampshire Supreme Court Logo

New Hampshire Supreme Court

Washington Department of Transport Logo

Washington Department of Transport

Royal Air Force Logo

Royal Air Force

Washington Department of Enterprise Services Logo

Washington Department of Enterprise Services

Department of Work and Pensions (UK) Logo

Department of Work and Pensions (UK)

Illumina Logo

Illumina

Slicedbread Logo

Slicedbread

Freadom Logo

Freadom

CR2

DFDS Logo

DFDS

Emerson Process Management Logo

Emerson Process Management