SDV SectorNews and signals from the software-defined vehicle sector. Global coverage, daily.

Elektrobit puts Classic AUTOSAR integration under version control and CI/CD

Elektrobit said its integration-as-code approach on the EB tresos toolchain turns AUTOSAR configuration into reusable, version-controlled workflows that run inside continuous integration pipelines, replacing manual work in a graphical tool.

Elektrobit set out an approach it calls integration-as-code in a statement dated October 29, describing it as an automation-first method for AUTOSAR Classic configuration and integration. Built on the company’s EB tresos toolchain, it transforms integration logic into reusable, version-controlled workflows, and by reducing dependence on manual configuration in a graphical interface and connecting to continuous integration and continuous delivery pipelines, the company said, it streamlines integration and supports development at scale. Elektrobit also described the approach as codifying engineering expertise into reusable software assets. Yaocheng Ni, general manager and chief revenue officer of Elektrobit China, said integration-as-code “redefines AUTOSAR integration through automation and reusable engineering”.

The occasion for the statement was an award, and the two dates are not the same. Gasgoo’s own winner list names Elektrobit among the 148 companies recognized with the Best Technical Practice Award, and records that the eighth Gasgoo Awards ceremony concluded in Shanghai on October 23 — six days before the English-language statement this report cites. Elektrobit’s statement, datelined Shanghai, says this is the fifth consecutive year the company has been recognized by the awards; that count is the company’s own and is not independently established here.

Elektrobit is a wholly owned subsidiary of AUMOVIO and says it is run as a separate business. The statement named no customer, no vehicle program using the approach and no date on which it entered production use, and gave no figure for the effect on integration effort.

Why it mattersTreating integration as code makes the configuration step reviewable and repeatable in the same pipeline as the software it configures, which is the distance between a software-defined vehicle program and the toolchain that actually builds it.

Source: Elektrobit newsroom

The SDV Sector Brief

The month in vehicle software — top stories, what our readers read most, and an editor's take. First Tuesday of the month, 08:30 CET. Double opt-in, unsubscribe anytime.