summaryrefslogtreecommitdiff
path: root/meta-phosphor/recipes-extended/pam/pam-ipmi_git.bb
diff options
context:
space:
mode:
authorAdriana Kobylak <anoo@us.ibm.com>2021-10-25 18:58:19 +0300
committerPatrick Williams <patrick@stwcx.xyz>2021-11-10 00:54:55 +0300
commitcdd91ad2909116d136f5152b645f87592f39a1db (patch)
tree805ac0036be2747115a4dc57233f232479ea05f5 /meta-phosphor/recipes-extended/pam/pam-ipmi_git.bb
parent5577bf45a23118c3d5e34fd35921c59985641c95 (diff)
downloadopenbmc-cdd91ad2909116d136f5152b645f87592f39a1db.tar.xz
image_types: Add BUILD_ID to MANIFEST
Add the BUILD_ID value to the MANIFEST so that it can be used alongside the VERSION value to generate a version id during firmware updates. Add a function to read BUILD_ID from the os-release file instead of reading it from a variable because the BUILD_ID value could be set via a os_release.bbappend file instead of a .conf file. Tested: Verified the BUILD_ID value was added to the MANIFEST by default, and when BUILD_ID was specified in a .conf file, and on a os-release.bbappend. Ex: $ cat MANIFEST purpose=xyz.openbmc_project.Software.Version.VersionPurpose.BMC version=2.11.0-dev-566-g263df7f852 BuildId=20211025151654 ExtendedVersion= KeyType=OpenBMC HashType=RSA-SHA256 MachineName=p10bmc Change-Id: I3b7beaccbbd47d8820d499180ccdf021b004cf85 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Diffstat (limited to 'meta-phosphor/recipes-extended/pam/pam-ipmi_git.bb')
0 files changed, 0 insertions, 0 deletions