projects / mirror_edk2.git / blame
| Commit | Line | Data |
|---|---|---|
| 4fcfd089 SB |
1 | # Azure DevOps Pipelines\r |
| 2 | \r | |
| 3 | These yml files are used to provide CI builds using the Azure DevOps Pipeline Service.\r | |
| 4 | Most of the CI leverages edk2-pytools to support cross platform building and execution.\r | |
| 5 | \r | |
| 6 | ## Core CI\r | |
| 7 | \r | |
| 8 | Focused on building and testing all packages in Edk2 without an actual target platform.\r | |
| 9 | \r | |
| 10 | See `.pytools/ReadMe.py` for more details\r | |
| 11 | \r | |
| 12 | ## Platform CI\r | |
| 13 | \r | |
| 14 | Focused on building a single target platform and confirming functionality on that platform.\r | |
| 15 | \r | |
| 16 | ## Conventions\r | |
| 17 | \r | |
| 18 | * Files extension should be *.yml. *.yaml is also supported but in Edk2 we use those for our package configuration.\r | |
| 19 | * Platform CI files should be in the `<PlatformPkg>/.azurepipelines` folder.\r | |
| 20 | * Core CI files are in the root folder.\r | |
| 21 | * Shared templates are in the `templates` folder.\r | |
| 22 | * Top level CI files should be named `<host os>-<tool_chain_tag>.yml`\r | |
| 23 | \r | |
| 24 | ## Links\r | |
| 25 | \r | |
| 26 | * Basic Azure Landing Site - https://docs.microsoft.com/en-us/azure/devops/pipelines/?view=azure-devops\r | |
| 27 | * Pipeline jobs - https://docs.microsoft.com/en-us/azure/devops/pipelines/process/phases?view=azure-devops&tabs=yaml\r | |
| 28 | * Pipeline yml scheme - https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=azure-devops&tabs=schema%2Cparameter-schema\r | |
| 29 | * Pipeline expression - https://docs.microsoft.com/en-us/azure/devops/pipelines/process/expressions?view=azure-devops\r | |
| 30 | * PyTools - https://github.com/tianocore/edk2-pytool-extensions and https://github.com/tianocore/edk2-pytool-library\r | |
| 31 | \r | |
| 32 | ## Lessons Learned\r | |
| 33 | \r | |
| 34 | ### Templates and parameters\r | |
| 35 | \r | |
| 36 | They are great but evil. If they are used as part of determining the steps of a build they must resolve before the build starts. They can not use variables set in a yml or determined as part of a matrix. If they are used in a step then they can be bound late.\r | |
| 37 | \r | |
| 38 | ### File matching patterns\r | |
| 39 | \r | |
| 40 | On Linux this can hang if there are too many files in the search list.\r | |
| 41 | \r | |
| 42 | ### Templates and file splitting\r | |
| 43 | \r | |
| 44 | Suggestion is to do one big yaml file that does what you want for one of your targets. Then do the second one and find the deltas. From that you can start to figure out the right split of files, steps, jobs.\r | |
| 45 | \r | |
| 46 | ### Conditional steps\r | |
| 47 | \r | |
| 48 | If you want the step to show up in the log but not run, use a step conditional. This is great when a platform doesn't currently support a feature but you want the builders to know that the features exists and maybe someday it will.\r | |
| 49 | \r | |
| 50 | If you want the step to not show up use a template step conditional wrapper. Beware this will be evaluated early (at build start). This can hide things not needed on a given OS for example.\r |