You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* refactor package selection methodology to utilize Save-Package-Properties for package targeting
* introduce the python - pullrequest build definition that is triggered against all sdk/ directories, and builds/tests the packages which were changed
* this also includes abstractions to reduce runtime by distributing sets of packages and duplicating matrix definition
* refactor all analyze checks which used to operate on ServiceDirectory to instead operate upon the packages present within a PackageInfoFolder from Save-Package-Properties
* miscellaneous tooling changes to account for new matrix possibilities
---------
Co-authored-by: Wes Haggard <[email protected]>
Co-authored-by: Patrick Hallisey <[email protected]>
Copy file name to clipboardExpand all lines: eng/pipelines/templates/steps/analyze.yml
+15-14Lines changed: 15 additions & 14 deletions
Original file line number
Diff line number
Diff line change
@@ -8,12 +8,7 @@ parameters:
8
8
ValidateFormatting: false
9
9
GenerateApiReviewForManualOnly: false
10
10
11
-
# The variable TargetingString is set by template `eng/pipelines/templates/steps/targeting-string-resolve.yml`. This template is invoked from yml files:
12
-
# eng/pipelines/templates/jobs/ci.tests.yml
13
-
# eng/pipelines/templates/jobs/ci.yml
14
-
# eng/pipelines/templates/jobs/live.test.yml
15
-
16
-
# Please use `$(TargetingString)` to refer to the python packages glob string. This was previously `${{ parameters.BuildTargetingString }}`.
11
+
# Please use `$(TargetingString)` to refer to the python packages glob string. This variable is set from resolve-package-targeting.yml.
0 commit comments