commit | 5577bf45a23118c3d5e34fd35921c59985641c95 | [log] [tgz] |
---|---|---|
author | Adriana Kobylak <anoo@us.ibm.com> | Mon Oct 25 15:16:00 2021 +0000 |
committer | Patrick Williams <patrick@stwcx.xyz> | Tue Nov 09 21:54:27 2021 +0000 |
tree | e0a5341cc57efd583fd6bb2e88e37e08273914c9 | |
parent | 7a35a9299af15772f2da00176f372e1400ac643b [diff] |
os-release: Set BUILD_ID to DATETIME In the community it was discussed having a field that would contain the date of when an image was built (timestamp) so that it could be used to generate a unique version id during firmware updates, and that could also be used to display the specific date of a build such as when it was released or the general availability date. The yocto recipe for os-release sets BUILD_ID to DATETIME by default. The current implementation of BUILD_ID duplicates the output of VERSION, therefore remove the openbmc implementation of BUILD_ID to pick up the default value of DATETIME. The value can be overwritten in a machine's conf file, or set to what it was before in an os-release.bbappend in a meta layer. Tested: - The os-release BUILD_ID has a timestamp value by default, ex: BUILD_ID="20211025151654". - The os-release BUILD_ID is set to the value specified in a machine conf file, ex: Ex: In: meta-ibm/conf/machine/p10bmc.conf BUILD_ID = "20211231120000" - The os-release BUILD_ID is set to the value specified in a meta-layer os-release bbappend: Ex: In: meta-ibm/recipes-core/os-release/os-release.bbappend BUILD_ID = "${@run_git(d, 'describe --abbrev=0')}" Change-Id: If5238c53e0c3463c181788afc713c560fb5fe034 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
OpenBMC is a Linux distribution for management controllers used in devices such as servers, top of rack switches or RAID appliances. It uses Yocto, OpenEmbedded, systemd, and D-Bus to allow easy customization for your platform.
sudo apt-get install -y git build-essential libsdl1.2-dev texinfo gawk chrpath diffstat
sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake \ rpcgen perl-Thread-Queue perl-bignum perl-Crypt-OpenSSL-Bignum sudo dnf groupinstall "C Development Tools and Libraries"
git clone git@github.com:openbmc/openbmc.git cd openbmc
Any build requires an environment set up according to your hardware target. There is a special script in the root of this repository that can be used to configure the environment as needed. The script is called setup
and takes the name of your hardware target as an argument.
The script needs to be sourced while in the top directory of the OpenBMC repository clone, and, if run without arguments, will display the list of supported hardware targets, see the following example:
$ . setup <machine> [build_dir] Target machine must be specified. Use one of: bletchley gsj romulus dl360poc kudo s2600wf e3c246d4i mihawk swift ethanolx mtjade tiogapass evb-ast2500 nicole transformers evb-ast2600 olympus-nuvoton witherspoon evb-npcm750 on5263m5 witherspoon-tacoma f0b p10bmc x11spi fp5280g2 palmetto yosemitev2 g220a qemuarm zaius gbs quanta-q71l
Once you know the target (e.g. romulus), source the setup
script as follows:
. setup romulus
bitbake obmc-phosphor-image
Additional details can be found in the docs repository.
The OpenBMC community maintains a set of tutorials new users can go through to get up to speed on OpenBMC development out here
Commits submitted by members of the OpenBMC GitHub community are compiled and tested via our Jenkins server. Commits are run through two levels of testing. At the repository level the makefile make check
directive is run. At the system level, the commit is built into a firmware image and run with an arm-softmmu QEMU model against a barrage of CI tests.
Commits submitted by non-members do not automatically proceed through CI testing. After visual inspection of the commit, a CI run can be manually performed by the reviewer.
Automated testing against the QEMU model along with supported systems are performed. The OpenBMC project uses the Robot Framework for all automation. Our complete test repository can be found here.
Support of additional hardware and software packages is always welcome. Please follow the contributing guidelines when making a submission. It is expected that contributions contain test cases.
Issues are managed on GitHub. It is recommended you search through the issues before opening a new one.
First, please do a search on the internet. There's a good chance your question has already been asked.
For general questions, please use the openbmc tag on Stack Overflow. Please review the discussion on Stack Overflow licensing before posting any code.
For technical discussions, please see contact info below for Discord and mailing list information. Please don't file an issue to ask a question. You'll get faster results by using the mailing list or Discord.
Feature List
Features In Progress
Features Requested but need help
Dive deeper into OpenBMC by opening the docs repository.
The Technical Steering Committee (TSC) guides the project. Members are: