Firmware DevOps is a web-based source code distribution and development solution that provides a unique, enhanced source code hosting solution with metadata-aware microservices and bots, together with a complete DevOps solution for BIOS and BMC firmware development. It features an enhanced robust Git™-based source control system with powerful integrated DevOps capabilities to help make firmware development simpler, faster and more secure. With fully integrated virtual and physical hardware testing services, Firmware DevOps is a vital tool for bringing products to market on budget and on time.
Firmware DevOps is available to AMI ODM and OEM firmware customers with the option to use specific components of the solution as needed and to integrate and add custom DevOps capabilities to Firmware DevOps. The solution is not intended to replace each customer’s own development methodologies, but rather to provide an opportunity to enhance and complement them, with the aim of shortening the development cycle and time to market.
Complete DevOps environment for firmware development
Automated testing for reliable, consistent source code
Git-based source code control
Multi-party development models for any combination of AMI / OEM / ODM collaboration
Cloud-based, on-premise and hybrid solutions available
Modular architecture — use only what is needed
Git access available via HTTPS, SSH or web browser
Why Firmware DevOps?
One of the key benefits of Firmware DevOps is a highly streamlined development experience for all types of firmware engineering teams. It also has secure development at its core – as all source code developed in conjunction with Firmware DevOps is required to pass static code analysis and other tests to ensure customer coding standards are enforced.
To make it familiar and compatible with existing OEM/ODM customer development methodologies, Firmware DevOps also incorporates several well-known industry tools into its framework, such as Git, GitLab™, Docker™, Ansible®, Kubernetes™ and more.
As part of its code verification process, Firmware DevOps enables continuous integration to ensure every check-in still builds. Firmware DevOps also integrates automated testing to ensure the latest source is always well tested. For quick on-boarding of engineering or development teams, Firmware DevOps moves complicated tool setup to the cloud.
The Git Source Control System
Firmware DevOps leverages the widely used Git source-control system to support standard git commands, minimize complexity, and enable easy migration of existing projects to the Firmware DevOps environment.
Most importantly, Firmware DevOps leverages the open source, widely used Gitlab source-control system to ensure that it is secure and constantly updated.
Standard git commands can be used with AMI’s system and the customer has single login with customer LDAP setup in AMI.
Firmware DevOps also scales to cloud environments with ease. The source deliverable model for BMC includes Release Tree, Active Tree and patch detail information.
Flexible Hosting for Easy Multi-party Development
Firmware DevOps scales to cloud environments with ease and provides the ultimate in flexibility, security and compatibility while accommodating the preferred deployment models of each customer. This flexibility means that multi-party development models can be arranged between any combination of AMI/OEM/ODM engineering teams.
The main Firmware DevOps server is hosted in the USA with full disaster recovery capability, with mirrors operating in Taiwan, China and India. AMI also offers git push mirroring capability to customers as a means of receiving automatic updates to customer mirrors.
All code merged with the master branch is run through static code analysis and a suite of security testing tools. Any issues detected are clearly listed in a report format pointing to exact lines of code for quick analysis and resolution.
Other security tools find common weaknesses or vulnerabilities in the code that arise when using common libraries incorrectly, pointing to exact lines and links to the explanation of the issue. All security issues require a logged sign-off if not corrected, while tool selection and aggressiveness also can be customized.
Enforcing Strong Coding Standards
While coding standards allow easy reading of source code within an engineering team or across an entire corporation, new employees can sometimes face challenges in conforming without heavy supervision. To help with this, specific rules for enforcement can be customized by the OEM/ODM, while rejection of coding standards can be overridden by specific power users.
Firmware DevOps uses multiple automated testing frameworks such as Robot Framework to enable automated testing, in addition to supporting manual testing and incorporates all test results into a common report. Firmware DevOps allows for test hardware to be connected at AMI or the customer site, while continuous testing allows the latest firmware image to be ready for deployment at any time.