Skip to content

release_process.md

Latest commit

 

History

History
28 lines (23 loc) · 1.92 KB

release_process.md

File metadata and controls

28 lines (23 loc) · 1.92 KB

Releasing the CLR Instrumentation Engine

Release occurs from the release branch. Please notify clrieowners@microsoft.com to initiate the release process.

Microsoft Internal Process

Develop Phase

  1. When changes are merged to main branch, the Main-CI build runs and creates artifacts (NuGet, zip, etc.)
  2. Once the build completes, the Main-CI Release pipeline automatically publishes artifacts to the internal NuGet feed with a preview version (eg. 1.0.15-build00001)
  3. When a release occurs, a PR to version bump the Instrumentation Engine as well as updating the CHANGELOG should occur.

Test Phase

Based on the changes and targeted platform releases, impacted scenarios and partner teams should be involved in testing for regressions.

Release Phase

  1. Once testing completes, PR to merge main branch to release branch
  2. Manually run the Signed build to create release artifacts
  3. Manually run the CLR Instrumentation Engine Release YAML pipeline (build/yaml/pipelines/release.yaml) to publish NuGets to the internal InstrumentationEngine feed. This pipeline consumes the Signed build artifacts. The remaining release steps below are still performed via the legacy classic release definition (definitionId=901) until they are migrated.
    • Publish NuGets to the internal NuGet feed and MSAzure (for Azure VM/VMSS WAD)
    • Publish Preinstalled CLR Instrumentation Engine zip file to Azure App Service
    • Publish msi/msm files to CDN and expose aka.ms links on this repo.