Question

when you create a build types how do you deal with?

do you create 3 builds per each branch as (ci,gate, manual) or per branch what is suffice to.
(ex. ci- for dev branch, nightly- main branch,manual…)

in general what is good way to follow. i have found some recommendation saying that it s good to have at least 3 build types for each branch.rules for better source control.

thx.

Answer 1

I think it’s really whatever meets your needs. We create 3 types per brach (Continuous, Daily, Manual)

Continuous is used to give developers immediate feedback on their checkin so we restrict which unit tests run to keep the build nice and quick. The daily build is more comprehensive as it runs overnight and can also be used to deploy in to a smoke test environment. The manual build is used for specific milestones in the project. These builds are used to create installers and pass the application over for formal testing. So it looks something like this

Dev Branch
– Continuous (used for dev feedback)
– Daily (used for full test runs and deployment to smoke test environment)
– Manual (Not used)

Main Branch
– Continuous (Used for quick check that merging activity hasn’t broken the build)
– Daily (used for full test runs and deployment to smoke test environment)
– Manual (used to denote that a build will be formally handed over to testers)

Hotfix Branch
– Continuous (used for dev feedback)
– Daily (used for full test runs and deployment to smoke test environment)
– Manual (used to denote that a build will be formally handed over to testers)

Release Branch
– Continuous (Used for quick check that merging activity hasn’t broken the build)
– Daily (used for full test runs and deployment to smoke test environment)
– Manual (used to denote that a build will be formally handed over to testers)

Of course your branching strategy may differ from ours.