Branch: refs/heads/move_post_merge_to_nightly
Home: https://github.com/tianocore/edk2
Commit: 4247ec97a36bae39007147e6989c173bc10d1147
https://github.com/tianocore/edk2/commit/4247ec97a36bae39007147e6989c173bc10d1147
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: d4b978a388a5c92d7cd8c88c6feceab15fa532c7
https://github.com/tianocore/edk2/commit/d4b978a388a5c92d7cd8c88c6feceab15fa532c7
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: 9337dda118ac09037cafc9c69c909f09473a36a0
https://github.com/tianocore/edk2/commit/9337dda118ac09037cafc9c69c909f09473a36a0
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: 96569d91df39285f72c5f55e5a628916ece96cee
https://github.com/tianocore/edk2/commit/96569d91df39285f72c5f55e5a628916ece96cee
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/4247ec97a36b%5E...96569d91df39
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
