# Preface
Please ensure you have read the [contribution
docs](https://github.com/microsoft/mu/blob/master/CONTRIBUTING.md) prior
to submitting the pull request. In particular,
[pull request
guidelines](https://github.com/microsoft/mu/blob/master/CONTRIBUTING.md#pull-request-best-practices).
## Description
This change added a few new matrix entries to support building
mu_tiano_platforms on native ARM64 systems. The PR will cover both
https://github.com/microsoft/mu_basecore/issues/369 and
https://github.com/microsoft/mu_basecore/issues/305.
The PR should also be incorporated with mu_devops change.
For each item, place an "x" in between `[` and `]` if true. Example:
`[x]`.
_(you can also check items in the GitHub UI)_
- [x] Impacts functionality?
- **Functionality** - Does the change ultimately impact how firmware
functions?
- Examples: Add a new library, publish a new PPI, update an algorithm,
...
- [ ] Impacts security?
- **Security** - Does the change have a direct security impact on an
application,
flow, or firmware?
- Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- [ ] Breaking change?
- **Breaking change** - Will anyone consuming this change experience a
break
in build or boot behavior?
- Examples: Add a new library class, move a module to a different repo,
call
a function in a new library class in a pre-existing module, ...
- [ ] Includes tests?
- **Tests** - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- [ ] Includes documentation?
- **Documentation** - Does the change contain explicit documentation
additions
outside direct code modifications (and comments)?
- Examples: Update readme file, add feature readme file, link to
documentation
on an a separate Web page, ...
## How This Was Tested
This was tested on selfhost-agents and existing agents.
## Integration Instructions
Pipeline changes, N/A for integration.
## Description
A new identifier can be used to identify published artifacts (as
of mu_devops 2.0.0 release). This change passes the packages and
targets being built to clarify artifact names.
The default value for the identifier is "Artifacts" so that is
what is being used at the moment. For example, build logs are
published under `"Logs Artifacts"`. After this change, the
identifier will be `"Logs <packages> <targets>"`.
- [ ] Impacts functionality?
- **Functionality** - Does the change ultimately impact how firmware functions?
- Examples: Add a new library, publish a new PPI, update an algorithm, ...
- [ ] Impacts security?
- **Security** - Does the change have a direct security impact on an application,
flow, or firmware?
- Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- [x] Breaking change?
- **Breaking change** - Will anyone consuming this change experience a break
in build or boot behavior?
- Examples: Add a new library class, move a module to a different repo, call
a function in a new library class in a pre-existing module, ...
- [ ] Includes tests?
- **Tests** - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- [ ] Includes documentation?
- **Documentation** - Does the change contain explicit documentation additions
outside direct code modifications (and comments)?
- Examples: Update readme file, add feature readme file, link to documentation
on an a separate Web page, ...
## How This Was Tested
Verified pipeline artifacts are named as expected.
## Integration Instructions
This is considered a "breaking change" because artifacts are accessible via
ADO APIs and can be identified by the artifact name. While it is unlikely any
process is consuming these artifacts based on name, if they are, they will
need to use the new artifact naming convention introduced in this change.
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
# Preface
Please ensure you have read the [contribution
docs](https://github.com/microsoft/mu/blob/master/CONTRIBUTING.md) prior
to submitting the pull request. In particular,
[pull request
guidelines](https://github.com/microsoft/mu/blob/master/CONTRIBUTING.md#pull-request-best-practices).
## Description
DfciPkg will be moving to a new repo, mu_feature_dfci. This PR is part
of that process.
For each item, place an "x" in between `[` and `]` if true. Example:
`[x]`.
_(you can also check items in the GitHub UI)_
- [ ] Impacts functionality?
- [ ] Impacts security?
- [x ] Breaking change?
- [ ] Includes tests?
- [ ] Includes documentation?
## How This Was Tested
Only tested manually using the QuemuQ35 platform.
## Integration Instructions
A (TBD) PR for mu_tiano_patforms will publish the integration
instructions.
Co-authored-by: kuqin12 <42554914+kuqin12@users.noreply.github.com>
## Description
Changes the matrix build job to be able to take input for the container
image used in the generic mu_devops file generated.
Will be used by: https://github.com/microsoft/mu_devops/pull/59
- [ ] Impacts functionality?
- [ ] Impacts security?
- [ ] Breaking change?
- [ ] Includes tests?
- [ ] Includes documentation?
## How This Was Tested
Tested on test pipeline with mu_devops changes made locally
## Integration Instructions
N/A
## Description
Updates this repo to use mu_devops for Azure Pipeline definitions.
In order to centralize definitions and avoid build churn in individual
Mu repos,
some changes are made to allow build administrators to quickly adjust
settings:
- Toolchain, VM image, and architecture are controlled by build
administrators through centralized
variable groups
- CI triggers, CI schedules, and PR triggers are controlled by build
administrators within the
individual pipeline UI settings
- [ ] Breaking change?
- Will this change break pre-existing builds or functionality without
action being taken?
**No**
## How This Was Tested
Verified in test pipelines.
## Integration Instructions
N/A - No developer integration required
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
REF:https://bugzilla.tianocore.org/show_bug.cgi?id=3891
Changes the Python version used in pipelines to 3.10.6 or greater
since that version introduces a fix (bp0-47231) for inconsistent
trailing slashes in tarfile longname directories.
This is required for stuart_update to succeed when handling a
web_dependency (e.g. GCC ARM compilers).
Remove 10 second delay workarounds for issues observed
when Mergify was originally enabled. These issues are
no longer present when GitHub branch protections are
used for status checks.
Cc: Sean Brogan <sean.brogan@microsoft.com>
Cc: Bret Barkelew <Bret.Barkelew@microsoft.com>
Cc: Liming Gao <gaoliming@byosoft.com.cn>
Signed-off-by: Michael D Kinney <michael.d.kinney@intel.com>
Reviewed-by: Bret Barkelew <bret.barkelew@microsoft.com>
Reviewed-by: Liming Gao <gaoliming@byosoft.com.cn>
(cherry picked from commit 5ef08a49e3411a56a2afedbb11127279033c8915)
The purpose of this package is to provide a generic Boot HID layer that can be
used so that devices that implement the Boot Mouse and Boot Keyboard HID
interfaces defined in the USB 1.1 spec can share a common HID processing layer.
This avoids duplication of the HID parsing/processing code and provides a
natural interface layer where various HID-supporting hardware can plug into
the UEFI input stack.
Manufacturer Firmware Configuration Interface (MFCI) provides a mechanism for an authenticated
agent, such as an OEM or ODM, to modify firmware security properties of a specific device, typically
for the purposes of remanufacturing or refurbishment.
Documentation for the feature begins here:
/MfciPkg/Docs/Mfci_Feature.md
Advanced in memory logger that is configurable for SEC-PEI-PEIPOSTMEM-DXE-SMM-up to Exit Boot Services, or, for systems that UEFI doesn't really participate until DXE, from DXE +optional SMM up to Exit Boot Services. Also include an Advanced File Logger
Project Mu UEFI Bot [bot]
uefibot
Joey Vagedes
Michael Kubacki
kuqin12
Michael Turner
Chris Fernald
kenlautner
Ken Lautner
Sean Brogan
Kun Qin
Bret Barkelew
Bret Barkelew
Jeremiah Cox
John Schock
Matthew Carlson