UefiCpuPkg: Move AsmRelocateApLoopStart from Mpfuncs.nasm to AmdSev.nasm

[mirror_edk2.git] / .pytool / Readme.md

# Edk2 Continuous Integration\r
\r
This file focuses on information for those working with the `.pytools` directory\r
directly or interested in lower-level details about how CI works.\r
\r
If you just want to get started building code, visit\r
[Build Instructions](https://github.com/tianocore/tianocore.github.io/wiki/Build-Instruction)\r
on the TianoCore wiki.\r
\r
## Basic Status\r
\r
| Package              | Windows VS2019 (IA32/X64)| Ubuntu GCC (IA32/X64/ARM/AARCH64) | Known Issues |\r
| :----                | :-----                   | :----                             | :---         |\r
| ArmPkg               |                    | :heavy_check_mark: |\r
| ArmPlatformPkg       |                    | :heavy_check_mark: |\r
| ArmVirtPkg           | SEE PACKAGE README | SEE PACKAGE README |\r
| CryptoPkg            | :heavy_check_mark: | :heavy_check_mark: | Spell checking in audit mode\r
| DynamicTablesPkg     |                    | :heavy_check_mark: |\r
| EmbeddedPkg          |\r
| EmulatorPkg          | SEE PACKAGE README | SEE PACKAGE README | Spell checking in audit mode\r
| FatPkg               | :heavy_check_mark: | :heavy_check_mark: |\r
| FmpDevicePkg         | :heavy_check_mark: | :heavy_check_mark: |\r
| IntelFsp2Pkg         |\r
| IntelFsp2WrapperPkg  |\r
| MdeModulePkg         | :heavy_check_mark: | :heavy_check_mark: | DxeIpl dependency on ArmPkg, Depends on StandaloneMmPkg, Spell checking in audit mode\r
| MdePkg               | :heavy_check_mark: | :heavy_check_mark: | Spell checking in audit mode\r
| NetworkPkg           | :heavy_check_mark: | :heavy_check_mark: | Spell checking in audit mode\r
| OvmfPkg              | SEE PACKAGE README | SEE PACKAGE README | Spell checking in audit mode\r
| PcAtChipsetPkg       | :heavy_check_mark: | :heavy_check_mark: |\r
| SecurityPkg          | :heavy_check_mark: | :heavy_check_mark: | Spell checking in audit mode\r
| ShellPkg             | :heavy_check_mark: | :heavy_check_mark: | Spell checking in audit mode, 3 modules are not being built by DSC\r
| SignedCapsulePkg     |\r
| SourceLevelDebugPkg  |\r
| StandaloneMmPkg      | :heavy_check_mark: | :heavy_check_mark: |\r
| UefiCpuPkg           | :heavy_check_mark: | :heavy_check_mark: | Spell checking in audit mode, 2 binary modules not being built by DSC\r
| UefiPayloadPkg       |\r
| UnitTestFrameworkPkg | :heavy_check_mark: | :heavy_check_mark: |\r
\r
For more detailed status look at the test results of the latest CI run on the\r
repo readme.\r
\r
## Background\r
\r
This Continuous integration and testing infrastructure leverages the TianoCore EDKII Tools PIP modules:\r
[library](https://pypi.org/project/edk2-pytool-library/) and\r
[extensions](https://pypi.org/project/edk2-pytool-extensions/) (with repos\r
located [here](https://github.com/tianocore/edk2-pytool-library) and\r
[here](https://github.com/tianocore/edk2-pytool-extensions)).\r
\r
The primary execution flows can be found in the\r
`.azurepipelines/Windows-VS2019.yml` and `.azurepipelines/Ubuntu-GCC5.yml`\r
files. These YAML files are consumed by the Azure Dev Ops Build Pipeline and\r
dictate what server resources should be used, how they should be configured, and\r
what processes should be run on them. An overview of this schema can be found\r
[here](https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=azure-devops&tabs=schema).\r
\r
Inspection of these files reveals the EDKII Tools commands that make up the\r
primary processes for the CI build: 'stuart_setup', 'stuart_update', and\r
'stuart_ci_build'. These commands come from the EDKII Tools PIP modules and are\r
configured as described below. More documentation on the tools can be\r
found [here](https://github.com/tianocore/edk2-pytool-extensions/blob/master/docs/using.md)\r
and [here](https://github.com/tianocore/edk2-pytool-extensions/blob/master/docs/features/feature_invocables.md).\r
\r
## Configuration\r
\r
Configuration of the CI process consists of (in order of precedence):\r
\r
* command-line arguments passed in via the Pipeline YAML\r
* a per-package configuration file (e.g. `<package-name>.ci.yaml`) that is\r
  detected by the CI system in EDKII Tools.\r
* a global configuration Python module (e.g. `CISetting.py`) passed in via the\r
  command-line\r
\r
The global configuration file is described in\r
[this readme](https://github.com/tianocore/edk2-pytool-extensions/blob/master/docs/usability/using_settings_manager.md)\r
from the EDKII Tools documentation. This configuration is written as a Python\r
module so that decisions can be made dynamically based on command line\r
parameters and codebase state.\r
\r
The per-package configuration file can override most settings in the global\r
configuration file, but is not dynamic. This file can be used to skip or\r
customize tests that may be incompatible with a specific package.  Each test generally requires\r
per package configuration which comes from this file.\r
\r
## Running CI locally\r
\r
The EDKII Tools environment (and by extension the ci) is designed to support\r
easily and consistently running locally and in a cloud ci environment.  To do\r
that a few steps should be followed.  Details of EDKII Tools can be found in the\r
[docs folder here](https://github.com/tianocore/edk2-pytool-extensions/tree/master/docs)\r
\r
### Running CI\r
\r
Quick notes:\r
\r
* By default all CI plugins are opted in.\r
  * Setting the plugin to `skip` as an argument will skip running the plugin.\r
    Examples:\r
    * `CompilerPlugin=skip` skip the build test\r
    * `GuidCheck=skip` skip the Guid check\r
    * `SpellCheck=skip` skip the spell checker\r
    * etc.\r
* Detailed reports and logs per package are captured in the `Build` directory.\r
\r
## Current PyTool Test Capabilities\r
\r
All CI tests are instances of EDKII Tools plugins. Documentation on the plugin\r
system can be found [here](https://github.com/tianocore/edk2-pytool-extensions/blob/master/docs/usability/using_plugin_manager.md)\r
and [here](https://github.com/tianocore/edk2-pytool-extensions/blob/master/docs/features/feature_plugin_manager.md).\r
Upon invocation, each plugin will be passed the path to the current package\r
under test and a dictionary containing its targeted configuration, as assembled\r
from the command line, per-package configuration, and global configuration.\r
\r
Note: CI plugins are considered unique from build plugins and helper plugins,\r
even though some CI plugins may execute steps of a build.\r
\r
In the example, these plugins live alongside the code under test (in the\r
`.pytool/Plugin` directory), but may be moved to the 'edk2-test' repo if that\r
location makes more sense for the community.\r
\r
### Module Inclusion Test - DscCompleteCheck\r
\r
This scans all INF files from a package and confirms they are\r
listed in the package level DSC file. The test considers it an error if any INF\r
does not appear in the `Components` section of the package-level DSC (indicating\r
that it would not be built if the package were built). This is critical because\r
much of the CI infrastructure assumes that all modules will be listed in the DSC\r
and compiled.\r
\r
This test will ignore INFs in the following cases:\r
\r
1. When `MODULE_TYPE` = `HOST_APPLICATION`\r
2. When a Library instance **only** supports the `HOST_APPLICATION` environment\r
\r
### Host Module Inclusion Test - HostUnitTestDscCompleteCheck\r
\r
This test scans all INF files from a package for those related to host\r
based unit tests and confirms they are listed in the unit test DSC file for the package.\r
The test considers it an error if any INF meeting the requirements does not appear\r
in the `Components` section of the unit test DSC. This is critical because\r
much of the CI infrastructure assumes that  modules will be listed in the DSC\r
and compiled.\r
\r
This test will only require INFs in the following cases:\r
\r
1. When `MODULE_TYPE` = `HOST_APPLICATION`\r
2. When a Library instance explicitly supports the `HOST_APPLICATION` environment\r
\r
### Code Compilation Test - CompilerPlugin\r
\r
Once the Module Inclusion Test has verified that all modules would be built if\r
all package-level DSCs were built, the Code Compilation Test simply runs through\r
and builds every package-level DSC on every toolchain and for every architecture\r
that is supported. Any module that fails to build is considered an error.\r
\r
### Host Unit Test Compilation and Run Test - HostUnitTestCompilerPlugin\r
\r
A test that compiles the dsc for host based unit test apps.\r
On Windows this will also enable a build plugin to execute that will run the unit tests and verify the results.\r
\r
These tools will be invoked on any CI\r
pass that includes the NOOPT target. In order for these tools to do their job,\r
the package and tests must be configured in a particular way...\r
\r
#### Including Host-Based Tests in the Package YAML\r
\r
For example, looking at the `MdeModulePkg.ci.yaml` config file, there are two\r
config options that control HostBased test behavior:\r
\r
```json\r
    ## options defined .pytool/Plugin/HostUnitTestCompilerPlugin\r
    "HostUnitTestCompilerPlugin": {\r
        "DscPath": "Test/MdeModulePkgHostTest.dsc"\r
    },\r
```\r
\r
This option tell the test builder to run. The test builder needs to know which\r
modules in this package are host-based tests, so that DSC path is provided.\r
\r
#### Configuring the HostBased DSC\r
\r
The HostBased DSC for `MdeModulePkg` is located at\r
`MdeModulePkg/Test/MdeModulePkgHostTest.dsc`.\r
\r
To add automated host-based unit test building to a new package, create a\r
similar DSC. The new DSC should make sure to have the `NOOPT` BUILD_TARGET\r
and should include the line:\r
\r
```\r
!include UnitTestFrameworkPkg/UnitTestFrameworkPkgHost.dsc.inc\r
```\r
\r
All of the modules that are included in the `Components` section of this\r
DSC should be of type HOST_APPLICATION.\r
\r
### GUID Uniqueness Test - GuidCheck\r
\r
This test works on the collection of all packages rather than an individual\r
package. It looks at all FILE_GUIDs and GUIDs declared in DEC files and ensures\r
that they are unique for the codebase. This prevents, for example, accidental\r
duplication of GUIDs when using an existing INF as a template for a new module.\r
\r
### Cross-Package Dependency Test - DependencyCheck\r
\r
This test compares the list of all packages used in INFs files for a given\r
package against a list of "allowed dependencies" in plugin configuration for\r
that package. Any module that depends on a disallowed package will cause a test\r
failure.\r
\r
### Library Declaration Test - LibraryClassCheck\r
\r
This test scans at all library header files found in the `Library` folders in\r
all of the package's declared include directories and ensures that all files\r
have a matching LibraryClass declaration in the DEC file for the package. Any\r
missing declarations will cause a failure.\r
\r
### Invalid Character Test - CharEncodingCheck\r
\r
This test scans all files in a package to make sure that there are no invalid\r
Unicode characters that may cause build errors in some character\r
sets/localizations.\r
\r
### Spell Checking - cspell\r
\r
This test runs a spell checker on all files within the package.  This is done\r
using the NodeJs cspell tool.  For details check `.pytool/Plugin/SpellCheck`.\r
For this plugin to run during ci you must install nodejs and cspell and have\r
both available to the command line when running your CI.\r
\r
Install\r
\r
* Install nodejs from https://nodejs.org/en/\r
* Install cspell\r
  1. Open cmd prompt with access to node and npm\r
  2. Run `npm install -g cspell`\r
\r
  More cspell info: https://github.com/streetsidesoftware/cspell\r
\r
### License Checking - LicenseCheck\r
\r
Scans all new added files in a package to make sure code is contributed under\r
BSD-2-Clause-Patent.\r
\r
### Ecc tool - EccCheck\r
\r
Run the Ecc tool on the package. The Ecc tool is available in the BaseTools\r
package. It checks that the code complies to the EDKII coding standard.\r
\r
### Coding Standard Compliance - UncrustifyCheck\r
\r
Runs the Uncrustify application to check for coding standard compliance issues.\r
\r
## PyTool Scopes\r
\r
Scopes are how the PyTool ext_dep, path_env, and plugins are activated.  Meaning\r
that if an invocable process has a scope active then those ext_dep and path_env\r
will be active. To allow easy integration of PyTools capabilities there are a\r
few standard scopes.\r
\r
| Scope      | Invocable                                            | Description    |\r
| :----      | :-----                                               | :----          |\r
| global     | edk2_invocable++ - should be base_abstract_invocable | Running an invocables |\r
| global-win | edk2_invocable++                                     | Running on Microsoft Windows |\r
| global-nix | edk2_invocable++                                     | Running on Linux based OS    |\r
| edk2-build |                                                      | This indicates that an invocable is building EDK2 based UEFI code |\r
| cibuild    | set in .pytool/CISettings.py                         | Suggested target for edk2 continuous integration builds.  Tools used for CiBuilds can use this scope.  Example: asl compiler |\r
| host-based-test | set in .pytool/CISettings.py                    | Turns on the host based tests and plugin |\r
| host-test-win | set in .pytool/CISettings.py                      | Enables the host based test runner for Windows |\r
\r
## Future investments\r
\r
* PatchCheck tests as plugins\r
* MacOS/xcode support\r
* Clang/LLVM support\r
* Visual Studio AARCH64 and ARM support\r
* BaseTools C tools CI/PR and binary release process\r
* BaseTools Python tools CI/PR process\r
* Extensible private/closed source platform reporting\r
* UEFI SCTs\r
* Other automation\r