User Story: Easily trigger builds for all MCP Components, incl. new MCP Landscape Versions

[In-Ko]

1. User Story Description

• As an MCP DevOps engineer,
• I need to be able to easily trigger builds for individual MCP Components as well as the complete MCP package,
• so that I can consistently create new versions of individual MCP Components and
• a new MCP Landscape Version

---

2. Tasks

• Identify and agree upon the minimum set on build tools we require to build the individual MCP Components
• Task: Optimizations to Makefiles #53

---

3. Acceptance Criteria

• The result of each individual build must be that the artifacts (mostly docker images and helm charts) are stored alongside their OCM Component Descriptor in an OCI-compatible repository.
• The individual build processes do not differ in terms of tools being used, in order to reduce the amount of technical knowledge required to be kept in the team
  • ...

---

4. Dependencies

• Dependency to the tools provided by the Open Component Model Project

---

5. Assumptions

• ...

---

6. Stakeholders

• MCP DevOps Engineers

---

7. Notes/Comments

[In-Ko]

All done, can be closed