Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add job matrix generation scripts #16450

Merged
merged 1 commit into from
Feb 1, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions eng/scripts/job-matrix/Create-JobMatrix.ps1
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
<#
.SYNOPSIS
Generates a JSON object representing an Azure Pipelines Job Matrix.
See https://docs.microsoft.com/en-us/azure/devops/pipelines/process/phases?view=azure-devops&tabs=yaml#parallelexec

.EXAMPLE
.\eng\scripts\Create-JobMatrix $context
#>

[CmdletBinding()]
param (
[Parameter(Mandatory=$True)][string] $ConfigPath,
[Parameter(Mandatory=$True)][string] $Selection,
[Parameter(Mandatory=$False)][string] $DisplayNameFilter,
[Parameter(Mandatory=$False)][array] $Filters
)

. $PSScriptRoot/job-matrix-functions.ps1

$config = GetMatrixConfigFromJson (Get-Content $ConfigPath)

[array]$matrix = GenerateMatrix $config $Selection $DisplayNameFilter $Filters
$serialized = SerializePipelineMatrix $matrix

Write-Output $serialized.pretty
Write-Output "##vso[task.setVariable variable=matrix;isOutput=true]$($serialized.compressed)"
274 changes: 274 additions & 0 deletions eng/scripts/job-matrix/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,274 @@
# Azure Pipelines Matrix Generator

* [Usage in a pipeline](#usage-in-a-pipeline)
* [Matrix config file syntax](#matrix-config-file-syntax)
* [Fields](#fields)
* [matrix](#matrix)
* [include](#include)
* [exclude](#exclude)
* [displayNames](#displaynames)
* [Matrix Generation behavior](#matrix-generation-behavior)
* [all](#all)
* [sparse](#sparse)
* [include/exclude](#includeexclude)
* [displayNames](#displaynames-1)
* [Filters](#filters)
* [Under the hood](#under-the-hood)
* [Testing](#testing)


This directory contains scripts supporting dynamic, cross-product matrix generation for azure pipeline jobs.
It aims to replicate the [cross-product matrix functionality in github actions](https://docs.github.com/free-pro-team@latest/actions/reference/workflow-syntax-for-github-actions#example-running-with-more-than-one-version-of-nodejs),
but also adds some additional features like sparse matrix generation, cross-product includes and excludes, and programmable matrix filters.

This functionality is made possible by the ability for the azure pipelines yaml to take a [dynamic variable as an input
for a job matrix definition](https://docs.microsoft.com/azure/devops/pipelines/process/phases?view=azure-devops&tabs=yaml#multi-job-configuration) (see the code sample at the bottom of the linked section).

## Usage in a pipeline

In order to use these scripts in a pipeline, you must provide a config file and call the matrix creation script within a powershell job.

For a single matrix, you can include the `eng/pipelines/templates/jobs/job-matrix.yml` template in a pipeline:

```
jobs:
- template: /eng/pipelines/templates/jobs/job-matrix.yml
parameters:
MatrixConfigs:
- Name: base_product_matrix
Path: /eng/pipelines/matrix.json
Selection: sparse
GenerateVMJobs: true
- Name: sdk_specific_matrix
Path: /sdk/foobar/matrix.json
Selection: all
GenerateContainerJobs: true
steps:
- pwsh:
...
```

## Matrix config file syntax

Matrix parameters can either be a list of strings, or a set of grouped strings (represented as a hash). The latter parameter
type is useful for when 2 or more parameters need to be grouped together, but without generating more than one matrix permutation.

```
"matrix": {
"<parameter1 name>": [ <values...> ],
"<parameter2 name>": [ <values...> ],
"<parameter set>": {
"<parameter set 1 name>": {
"<parameter set 1 value 1": "value",
"<parameter set 1 value 2": "<value>",
},
"<parameter set 2 name>": {
"<parameter set 2 value 1": "value",
"<parameter set 2 value 2": "<value>",
}
}
}
"include": [ <matrix>, <matrix>, ... ],
"exclude": [ <matrix>, <matrix>, ... ],
"displayNames": { <parameter value>: <human readable override> }
```

See `samples/matrix.json` for a full sample.

### Fields

#### matrix

The `matrix` field defines the base cross-product matrix. The generated matrix can be full or sparse.

Example:
```
"matrix": {
"operatingSystem": [
"windows-2019",
"ubuntu-18.04",
"macOS-10.15"
],
"framework": [
"net461",
"netcoreapp2.1",
"net50"
],
"additionalTestArguments": [
"",
"/p:UseProjectReferenceToAzureClients=true",
]
}
```

#### include

The `include` field defines any number of matrices to be appended to the base matrix after processing exclusions.

#### exclude

The `include` field defines any number of matrices to be removed from the base matrix. Exclude parameters can be a partial
set, meaning as long as all exclude parameters match against a matrix entry (even if the matrix entry has additional parameters),
then it will be excluded from the matrix. For example, the below entry will match the exclusion and be removed:

```
matrix entry:
{
"a": 1,
"b": 2,
"c": 3,
}

"exclude": [
{
"a": 1,
"b": 2
}
]
```

#### displayNames

Specify any overrides for the azure pipelines definition and UI that determines the matrix job name. If some parameter
values are too long or unreadable for this purpose (e.g. a command line argument), then you can replace them with a more
readable value here. For example:

```
"displayNames": {
"/p:UseProjectReferenceToAzureClients=true": "UseProjectRef"
},
"matrix": {
"additionalTestArguments": [
"/p:UseProjectReferenceToAzureClients=true"
]
}
```

## Matrix Generation behavior

#### all

`all` will output the full matrix, i.e. every possible permutation of all parameters given (p1.Length * p2.Length * ...).

#### sparse

`sparse` outputs the minimum number of parameter combinations while ensuring that all parameter values are present in at least one matrix job.
Effectively this means the total length of a sparse matrix will be equal to the largest matrix dimension, i.e. `max(p1.Length, p2.Length, ...)`.

To build a sparse matrix, a full matrix is generated, and then walked diagonally N times where N is the largest matrix dimension.
This pattern works for any N-dimensional matrix, via an incrementing index (n, n, n, ...), (n+1, n+1, n+1, ...), etc.
Index lookups against matrix dimensions are calculated modulus the dimension size, so a two-dimensional matrix of 4x2 might be walked like this:

```
index: 0, 0:
o . . .
. . . .

index: 1, 1:
. . . .
. o . .

index: 2, 2 (modded to 2, 0):
. . o .
. . . .

index: 3, 3 (modded to 3, 1):
. . . .
. . . o
```

#### include/exclude

Include and exclude support additions and subtractions off the base matrix. Both include and exclude take an array of matrix values.
Typically these values will be a single entry, but they also support the cross-product matrix definition syntax of the base matrix.

Include and exclude are parsed fully. So if a sparse matrix is called for, a sparse version of the base matrix will be generated, but
the full matrix of both include and exclude will be processed.

Excludes are processed first, so includes can be used to add back any specific jobs to the matrix.

#### displayNames

In the matrix job output that azure pipelines consumes, the format is a dictionary of dictionaries. For example:

```
{
"net461_macOS1015": {
"framework": "net461",
"operatingSystem": "macOS-10.15"
},
"net50_ubuntu1804": {
"framework": "net50",
"operatingSystem": "ubuntu-18.04"
},
"netcoreapp21_windows2019": {
"framework": "netcoreapp2.1",
"operatingSystem": "windows-2019"
},
"UseProjectRef_net461_windows2019": {
"additionalTestArguments": "/p:UseProjectReferenceToAzureClients=true",
"framework": "net461",
"operatingSystem": "windows-2019"
}
}
```

The top level keys are used as job names, meaning they get displayed in the azure pipelines UI when running the pipeline.

The logic for generating display names works like this:

- Join parameter values by "_"
a. If the parameter value exists as a key in `displayNames` in the matrix config, replace it with that value.
b. For each name value, strip all non-alphanumeric characters (excluding "_").
c. If the name is greater than 100 characters, truncate it.

#### Filters

Filters can be passed to the matrix as an array of strings, each matching the format of <key>=<regex>. When a matrix entry
does not contain the specified key, it will default to a value of empty string for regex parsing. This can be used to specify
filters for keys that don't exist or keys that optionally exist and match a regex, as seen in the below example.

Display name filters can also be passed as a single regex string that runs against the [generated display name](#displaynames) of the matrix job.
The intent of display name filters is to be defined primarily as a top level variable at template queue time in the azure pipelines UI.

For example, the below command will filter for matrix entries with "windows" in the job display name, no matrix variable
named "ExcludedKey", a framework variable containing either "461" or "5.0", and an optional key "SupportedClouds" that, if exists, must contain "Public":

```
./Create-JobMatrix.ps1 `
-ConfigPath samples/matrix.json `
-Selection all `
-DisplayNameFilter ".*windows.*" `
-Filters @("ExcludedKey=^$", "framework=(461|5\.0)", "SupportedClouds=^$|.*Public.*")
```

#### Under the hood

The script generates an N-dimensional matrix with dimensions equal to the parameter array lengths. For example,
the below config would generate a 2x2x1x1x1 matrix (five-dimensional):

```
"matrix": {
"framework": [ "net461", "netcoreapp2.1" ],
"additionalTestArguments": [ "", "/p:SuperTest=true" ]
"pool": [ "ubuntu-18.04" ],
"container": [ "ubuntu-18.04" ],
"testMode": [ "Record" ]
}
```

The matrix is stored as a one-dimensional array, with a row-major indexing scheme (e.g. `(2, 1, 0, 1, 0)`).

## Testing

The matrix functions can be tested using [pester](https://pester.dev/):

```
$ Invoke-Pester

Starting discovery in 1 files.
Discovery finished in 384ms.
[+] /home/ben/sdk/azure-sdk-for-net/eng/scripts/job-matrix/job-matrix-functions.tests.ps1 4.09s (1.52s|2.22s)
Tests completed in 4.12s
Tests Passed: 120, Failed: 0, Skipped: 4 NotRun: 0
```
84 changes: 84 additions & 0 deletions eng/scripts/job-matrix/job-matrix-functions.filter.tests.ps1
Original file line number Diff line number Diff line change
@@ -0,0 +1,84 @@
Import-Module Pester

BeforeAll {
. ./job-matrix-functions.ps1

$matrixConfig = @"
{
"matrix": {
"operatingSystem": [ "windows-2019", "ubuntu-18.04", "macOS-10.15" ],
"framework": [ "net461", "netcoreapp2.1" ],
"additionalArguments": [ "", "mode=test" ]
}
}
"@
$config = GetMatrixConfigFromJson $matrixConfig
}

Describe "Matrix Filter" -Tag "filter" {
It "Should filter by matrix display name" -TestCases @(
@{ regex = "windows.*"; expectedFirst = "windows2019_net461"; length = 4 }
@{ regex = "windows2019_netcoreapp21_modetest"; expectedFirst = "windows2019_netcoreapp21_modetest"; length = 1 }
@{ regex = ".*ubuntu.*"; expectedFirst = "ubuntu1804_net461"; length = 4 }
) {
[array]$matrix = GenerateMatrix $config "all" $regex
$matrix.Length | Should -Be $length
$matrix[0].Name | Should -Be $expectedFirst
}

It "Should handle no display name filter matches" {
$matrix = GenerateMatrix $config "all"
[array]$filtered = FilterMatrixDisplayName $matrix "doesnotexist"
$filtered | Should -BeNullOrEmpty
}

It "Should filter by matrix key/value" -TestCases @(
@{ filterString = "operatingSystem=windows.*"; expectedFirst = "windows2019_net461"; length = 4 }
@{ filterString = "operatingSystem=windows-2019"; expectedFirst = "windows2019_net461"; length = 4 }
@{ filterString = "framework=.*"; expectedFirst = "windows2019_net461"; length = 12 }
@{ filterString = "additionalArguments=mode=test"; expectedFirst = "windows2019_net461_modetest"; length = 6 }
@{ filterString = "additionalArguments=^$"; expectedFirst = "windows2019_net461"; length = 6 }
) {
[array]$matrix = GenerateMatrix $config "all" -filters @($filterString)
$matrix.Length | Should -Be $length
$matrix[0].Name | Should -Be $expectedFirst
}

It "Should filter by optional matrix key/value" -TestCases @(
@{ filterString = "operatingSystem=^$|windows.*"; expectedFirst = "windows2019_net461"; length = 4 }
@{ filterString = "doesnotexist=^$|.*"; expectedFirst = "windows2019_net461"; length = 12 }
) {
[array]$matrix = GenerateMatrix $config "all" -filters @($filterString)
$matrix.Length | Should -Be $length
$matrix[0].Name | Should -Be $expectedFirst
}

It "Should handle multiple matrix key/value filters " {
[array]$matrix = GenerateMatrix $config "all" -filters "operatingSystem=windows.*","framework=.*","additionalArguments=mode=test"
$matrix.Length | Should -Be 2
$matrix[0].Name | Should -Be "windows2019_net461_modetest"
}

It "Should handle no matrix key/value filter matches" {
[array]$matrix = GenerateMatrix $config "all" -filters @("doesnot=exist")
$matrix | Should -BeNullOrEmpty
}

It "Should handle invalid matrix key/value filter syntax" {
{ GenerateMatrix $config "all" -filters @("invalid") } | Should -Throw
{ GenerateMatrix $config "all" -filters @("emptyvalue=") } | Should -Throw
{ GenerateMatrix $config "all" -filters @("=emptykey") } | Should -Throw
{ GenerateMatrix $config "all" -filters @("=") } | Should -Throw
}

It "Should filter by key exclude" {
[array]$matrix = GenerateMatrix $config "all" -filters @("operatingSystem=^$")
$matrix | Should -BeNullOrEmpty

[array]$matrix = GenerateMatrix $config "all"
$matrix.Length | Should -Be 12
$matrix += @{ Name = "excludeme"; Parameters = [Ordered]@{ "foo" = 1 } }
[array]$matrix = FilterMatrix $matrix @("foo=^$")
$matrix.Length | Should -Be 12
}
}
Loading