Skip to content

EP Process

Overview

  • EP stands for exception release, EP means to release code to BTS or PROD out of a regular monthly release
  • EP is basically a special small-scale release, so it's recommended to read monthly release for related knowledge, and this wiki focuses on the EP particular part
  • Case for 16.9.0-EP
    • Latest release branch: release/16.9.0
    • Latest release CMC version-build: 16.9.0:9999
    • working CMC version-build: 17.0.0:9999
    • Created EP branch: release/16.9.0-EP
    • Created EP CMC version build: 16.9.0:99991
    • Created EP CDP release: 16.9.1

QA EP release

1. Create EP branch and merge release code to EP branch

  • EP branch should base on the latest release branch

2. Create EP CMC version-build

  • EP CMC version number should be the last release CMC version numbmer
  • EP CMC build number should be the largest one in the last release CMC version
  • Update CMC configuration if needed

3. Build MCT Component packages based on EP branch and refresh on QA

  • Remember to refresh with EP CMC version-build

4. QA Verification pass

BTS and PROD EP release

💡 Do not forget to upgrade CMC EP version-build to BTS or PROD

1. CDP preparation

  1. Create CDP release for DevOps

    If choose the Others item as Implementation Type as the below screenshoot shown, CDP change and ticket can be opened, but CDP pipeline will not take effect (e.g. skip and complete in CDP pipeline) , then release owner can manual release with CMC

    picture 3

  2. Create CDP DevOps ticket

  3. release and change synchronization

    1. release BTS EP with CDP
    2. BTS verification pass
    3. release PROD EP with CDP
    4. PROD verification pass
    5. Synchronize EP change to the main branch and working CMC version-build configuration. Otherwise, the next monthly release will clear the EP change