Skip to content

Latest commit

 

History

History
51 lines (38 loc) · 2.06 KB

ci-platform-coverage-guidelines.md

File metadata and controls

51 lines (38 loc) · 2.06 KB

Guidelines for Platforms Tested in CI

This document contains the guidelines for which platforms (OS and architectures) to test in the source build CI.

Distro Families

  1. Prefer testing base distros of families over derivatives.
  2. Prioritize testing distros that source build .NET.
  3. Use CentOS Stream instead of Red Hat because it is the free alternative.
  4. Include a permutation of distros for the supported C standard library implementations (e.g. glibc and musl).
  5. For each C standard library implementation, include at least one distro that uses the minimum supported version of this library.
  6. Only test distros that are officially supported by .NET. Community supported distros will not be covered.

Distro Versions

  1. Prefer testing latest LTS version. If LTS is unsupported, use the latest version instead.
  2. Drop distro versions that will be or are nearing EOL on the .NET release day.
  3. Stop updating the test matrix in the last 6 months of support for a .NET version as new distro versions are released.

Architectures

  1. Amd64
  2. Arm64

Permutations

It is not the intent to test every permutation of distro family, distro version, and architecture. Rather, smart decisions should be made to best utilize resources.

The following distro versions will be included in the CI matrix:

  1. CentOS Stream - Latest version (amd64)
  2. Fedora - Latest version (amd64)
  3. Ubuntu - Latest LTS version at the time of the release (amd64/arm64)
  4. Alpine - Latest and previous versions (amd64)
  5. AlmaLinux - Oldest version (targets lowest glibc version) (amd64)

When updating the distro versions in the CI matrix as new versions are released and older versions reach EOL:

  1. Update main to the newer version one to two months prior to the GA/EOL date. This is done to flush out any issues and to avoid destabilizing the servicing branches.
  2. At the GA/EOL date, update the servicing branches.