Note: All Builds should have a corresponding repo manifest (with corresponding git hash for each repo) available point to the code using which the build is triggered.
Daily Builds:
Daily scheduled builds are triggered by CI/CD pipeline of Tungsten Fabric infrastructure, for master branch and all other active branches.
It is expected to have only one daily build out of any branch.
Active branch: A Branch that maps to an active community release as per release lifecycle definition or otherwise approved as an exception by TSC
Master branch:
Build Tag format: <YYYY-MM-DD> (eg: 2020-10-09)
Additionally running tag "latest" can be used to point to the latest build
* if build passes the pre-defined minimum acceptance criteria it can be additionally tagged as "latest-stable"
Other Active Branches:
Build Tag format: <BranchName-YYYY-MM-DD> (eg: R2011-2020-10-09)
Additionally running tag <BranchName-latest> can be used to point to the latest build (eg: R2011-latest)
* if build passes the pre-defined minimum acceptance criteria it can be additionally tagged as <BranchName-latest-stable> (eg: R2011-latest-stable)
Release Builds:
While we are approaching Release dates for a particular release, daily builds based on acceptance test criteria will be rebuilt as Release candidates with appropriate build tag.
Release Candidate Build Tag Format: <ReleaseName-RCx> (eg: R2011-RC0 or R2011-RC1 and so on based on number of release candidates considered)
* Recommendation is not to have more than 4 release candidate builds
With Inputs from PTLs and Release Manager TSC approves one of these Release Candidates as a release build
Release Build Tag Format: <ReleaseName> (eg: R2011)
Release Naming: community release is labelled as <RYYMM> (eg: R2011) and subsequent service release will be labelled as <RYYMM.x> (eg: R2011.1) where x represents the service release number