Skip to main content

Eclipse SDV Hephaestus

Eclipse SDV Hephaestus centralizes and standardizes build, tooling, and development environments across Eclipse SDV projects to reduce duplication, enable seamless integration and open-source development workflows.

In Scope

  • Bazel-based build and dependency management as the harmonized build system, enabling joint integration of multiple Eclipse SDV components
  • Other build and dependency management systems e.g. Cargo should be supported
  • Doc-as-Code via Sphinx-Needs, establishing a digital thread linking requirements to technical specifications and test execution results
  • Using the Eclipse Common Build Infrastructure
  • Pilot adoption with Eclipse S-CORE, Eclipse OpenSOVD, and Eclipse Automotive API Framework
  • SIL KIT (Eclipse OpenXilEnv) as a candidate for tool integration.
  • Qualification process compliant with ASPICE and ISO 26262, preparation and tooling support only
  • Automotive Edge but exploring potential synergies between edge and cloud

Out of Scope

  • Actual Safety Certification (such as receiving a final product certificate) and the management of associated liability are excluded, because this is considered as a part of a business model or private agreement between contractual partners
  • Mandatory integration of commercial or closed-source tools. These remain optional via well-defined plugin interfaces
  • Replacing project-specific domain logic

Basics

Active repositories

Repository Commits Reviews Issues
This project has no activity.

The EMO oversees the lifecycle of Eclipse projects, trademark and IP management, and provides a governance framework and recommendations on open source best practices.

See the project’s PMI page at https://projects.eclipse.org/projects/automotive.hephaestus

Releases

Reviews

IP Lab requests

Organization Settings

  • GitHub organization: eclipse-hephaestus
  • 2FA enforced: True
  • Default workflow permissions: read

Branch Protections

This project has a total of 2 repositories in its associated GitHub organization eclipse-hephaestus . The graph below outlines the percentange of repositories that have either defined a Branch Protection Rule or Repository Ruleset: Branch protections

SDV Maturity badges recognise achievements made by the project towards the SDV maturity assessment goals. Learn more on the dedicated page .

These badges only apply to the SDV Working Group .

Blueprints integration

Is the project used to showcase the resolution of a real-life situation, either individually or integrated with other Eclipse SDV projects? See the SDV Blueprints project for more information.

This project has not registered any activity on the criteria.

Requirements

How well is the project doing when it comes to Requirements e.g. defining, versioning and managing, traceability, coverage, etc? For more details on the needs for the different levels of the Requirements Criteria read its definition here .

This project has not registered any activity on the criteria.

Testing

How well is the project doing when it comes to Testing e.g. defining, versioning and managing, traceability, coverage, types of tests etc? For more details on the needs for the different levels of the Testing Criteria read its definition here .

This project has not registered any activity on the criteria.

Documentation

How well is the project doing when it comes to Documentation e.g. types of documents depending on contents, versioning, etc? For more details on the needs for the different levels of the Documentation Criteria read its definition here .

This project has not registered any activity on the criteria.

Coding Guidelines

How well is the project doing when it comes to Coding Guidelines e.g. defining, adhering, managing issues etc? For more details on the needs for the different levels of the Coding Guidelines Criteria read its definition here .

This project has not registered any activity on the criteria.

Release process

How well is the project doing when it comes to Releases e.g. defining a process, versioning and managing, release notes, coverage etc? For more details on the needs for the different levels of the Release Process Criteria read its definition here .

This project has not registered any activity on the criteria.

OSS Best Practices

Is the project respecting OSS good practices files in their repositories? See also the legal documentation checker for more information.

This project has not registered any activity on the criteria.

Back to the top