Skip to content

Commit

Permalink
Handle when no "direct" packages are changed (#37599)
Browse files Browse the repository at this point in the history
* ensure the default isn't "scan the entire repo"
  • Loading branch information
scbedd authored Sep 27, 2024
1 parent a61273f commit 5f5ab59
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 2 deletions.
4 changes: 2 additions & 2 deletions eng/pipelines/templates/jobs/ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -138,7 +138,7 @@ jobs:
parameters:
BuildTargetingString: ${{ parameters.BuildTargetingString }}
PackagePropertiesFolder: $(Build.ArtifactStagingDirectory)/PackageInfo
IncludeIndirect: true
IncludeIndirect: false

- template: /eng/pipelines/templates/steps/build-extended-artifacts.yml
parameters:
Expand Down Expand Up @@ -170,7 +170,7 @@ jobs:
parameters:
BuildTargetingString: ${{ parameters.BuildTargetingString }}
PackagePropertiesFolder: $(Build.ArtifactStagingDirectory)/PackageInfo
IncludeIndirect: true
IncludeIndirect: false

- template: ../steps/build-extended-artifacts.yml
parameters:
Expand Down
6 changes: 6 additions & 0 deletions eng/pipelines/templates/steps/resolve-package-targeting.yml
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,12 @@ steps:
}
$setting = $packageProperties -join ","
# in case we don't expect any packages, we should set the variable to null, which will match NO packages and cause whatever the check
# is to skip with exit 0 (which is what we want!)
if (-not $setting) {
$setting = "null"
}
}
}
Expand Down

0 comments on commit 5f5ab59

Please sign in to comment.