Branch: refs/heads/master
Home: https://github.com/tianocore/edk2
Commit: 842720ed0943cc031cdc8547a8e5bfc041010f90
https://github.com/tianocore/edk2/commit/842720ed0943cc031cdc8547a8e5bfc041010f90
Author: Michael Kubacki <[email protected]>
Date: 2026-01-27 (Tue, 27 Jan 2026)
Changed paths:
M .azurepipelines/Ubuntu-GCC.yml
M .azurepipelines/Windows-VS.yml
Log Message:
-----------
.azurepipelines: Move post-merge to a daily build
Pipelines currently run at two main points:
- Pushes to pull requests
- Post-merge (after a commit is merged to the master branch)
There are two main reasons this has historically been done:
1. To catch any issues that may have been missed during PR validation
due to timing related factors (e.g., merge order into master).
2. To separate a more extensive set of tests from the PR validation
to reduce the feedback time for contributors in PRs.
PRs are ordered in master with mergify's merge queue, which helps
reduce timing related issues for (1). For (2), the current
post-merge tests are not significantly different from the PR
validation tests, so the value is limited. The main differentiation
is that the PR eval tool is only run in PR triggered pipelines and
always runs in non-PR triggered runs:
For example:
```
- task: CmdLine@2
displayName: Check if ${{ parameters.build_pkgs }} need testing
inputs:
script: stuart_pr_eval ...
condition: eq(variables['Build.Reason'], 'PullRequest')
```
It is rare for an issue not be found in the PR eval run. Therefore,
we are moving post-merge runs to a daily schedule. This will
still provide regular testing of the master branch while reducing
overall resource usage lending more capacity to PR validation runs
and the introduction of Clang pipelines.
These pipelines are scheduled to run daily at 7AM UTC chosen to
minimize overlap with other scheduled pipelines.
Signed-off-by: Michael Kubacki <[email protected]>
Commit: 8d3d9d2f0ea6c9602f654a182250119343b00bed
https://github.com/tianocore/edk2/commit/8d3d9d2f0ea6c9602f654a182250119343b00bed
Author: Michael Kubacki <[email protected]>
Date: 2026-01-27 (Tue, 27 Jan 2026)
Changed paths:
M ArmVirtPkg/PlatformCI/.azurepipelines/Ubuntu-GCC.yml
Log Message:
-----------
ArmVirtPkg: Move post-merge pipelines runs to a daily build
Pipelines currently run at two main points:
- Pushes to pull requests
- Post-merge (after a commit is merged to the master branch)
There are two main reasons this has historically been done:
1. To catch any issues that may have been missed during PR validation
due to timing related factors (e.g., merge order into master).
2. To separate a more extensive set of tests from the PR validation
to reduce the feedback time for contributors in PRs.
PRs are ordered in master with mergify's merge queue, which helps
reduce timing related issues for (1). For (2), the current
post-merge tests are not significantly different from the PR
validation tests, so the value is limited. The main differentiation
is that the PR eval tool is only run in PR triggered pipelines and
always runs in non-PR triggered runs:
For example:
```
- task: CmdLine@2
displayName: Check if ${{ parameters.build_pkgs }} need testing
inputs:
script: stuart_pr_eval ...
condition: eq(variables['Build.Reason'], 'PullRequest')
```
It is rare for an issue not be found in the PR eval run. Therefore,
we are moving post-merge runs to a daily schedule. This will
still provide regular testing of the master branch while reducing
overall resource usage lending more capacity to PR validation runs
and the introduction of Clang pipelines.
These pipelines are scheduled to run daily at 2AM UTC chosen to
minimize overlap with other scheduled pipelines.
Signed-off-by: Michael Kubacki <[email protected]>
Commit: f16447702c48caee2509aadea11569ff7a026b41
https://github.com/tianocore/edk2/commit/f16447702c48caee2509aadea11569ff7a026b41
Author: Michael Kubacki <[email protected]>
Date: 2026-01-27 (Tue, 27 Jan 2026)
Changed paths:
M EmulatorPkg/PlatformCI/.azurepipelines/Ubuntu-GCC.yml
M EmulatorPkg/PlatformCI/.azurepipelines/Windows-VS.yml
Log Message:
-----------
EmulatorPkg: Move post-merge pipelines runs to a daily build
Pipelines currently run at two main points:
- Pushes to pull requests
- Post-merge (after a commit is merged to the master branch)
There are two main reasons this has historically been done:
1. To catch any issues that may have been missed during PR validation
due to timing related factors (e.g., merge order into master).
2. To separate a more extensive set of tests from the PR validation
to reduce the feedback time for contributors in PRs.
PRs are ordered in master with mergify's merge queue, which helps
reduce timing related issues for (1). For (2), the current
post-merge tests are not significantly different from the PR
validation tests, so the value is limited. The main differentiation
is that the PR eval tool is only run in PR triggered pipelines and
always runs in non-PR triggered runs:
For example:
```
- task: CmdLine@2
displayName: Check if ${{ parameters.build_pkgs }} need testing
inputs:
script: stuart_pr_eval ...
condition: eq(variables['Build.Reason'], 'PullRequest')
```
It is rare for an issue not be found in the PR eval run. Therefore,
we are moving post-merge runs to a daily schedule. This will
still provide regular testing of the master branch while reducing
overall resource usage lending more capacity to PR validation runs
and the introduction of Clang pipelines.
These pipelines are scheduled to run daily at 2AM UTC chosen to
minimize overlap with other scheduled pipelines.
Signed-off-by: Michael Kubacki <[email protected]>
Commit: 0ba3897fb3d120d73e466c1b319473726735fced
https://github.com/tianocore/edk2/commit/0ba3897fb3d120d73e466c1b319473726735fced
Author: Michael Kubacki <[email protected]>
Date: 2026-01-27 (Tue, 27 Jan 2026)
Changed paths:
M OvmfPkg/PlatformCI/.azurepipelines/Ubuntu-GCC.yml
M OvmfPkg/PlatformCI/.azurepipelines/Windows-VS.yml
Log Message:
-----------
OvmfPkg: Move post-merge pipelines runs to a daily build
Pipelines currently run at two main points:
- Pushes to pull requests
- Post-merge (after a commit is merged to the master branch)
There are two main reasons this has historically been done:
1. To catch any issues that may have been missed during PR validation
due to timing related factors (e.g., merge order into master).
2. To separate a more extensive set of tests from the PR validation
to reduce the feedback time for contributors in PRs.
PRs are ordered in master with mergify's merge queue, which helps
reduce timing related issues for (1). For (2), the current
post-merge tests are not significantly different from the PR
validation tests, so the value is limited. The main differentiation
is that the PR eval tool is only run in PR triggered pipelines and
always runs in non-PR triggered runs:
For example:
```
- task: CmdLine@2
displayName: Check if ${{ parameters.build_pkgs }} need testing
inputs:
script: stuart_pr_eval ...
condition: eq(variables['Build.Reason'], 'PullRequest')
```
It is rare for an issue not be found in the PR eval run. Therefore,
we are moving post-merge runs to a daily schedule. This will
still provide regular testing of the master branch while reducing
overall resource usage lending more capacity to PR validation runs
and the introduction of Clang pipelines.
These pipelines are scheduled to run daily at 5AM UTC chosen to
minimize overlap with other scheduled pipelines.
Signed-off-by: Michael Kubacki <[email protected]>
Compare: https://github.com/tianocore/edk2/compare/b7d0b8331fd5...0ba3897fb3d1
To unsubscribe from these emails, change your notification settings at
https://github.com/tianocore/edk2/settings/notifications
_______________________________________________
edk2-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-commits
