Story: Improve EDC's build pipelines

[paullatzelsperger]

Feature Request

We should improve our build pipelines to have cascaded builds. Also, Github Actions should trigger a (snapshot) release directly.

Which Areas Would Be Affected?

build (Jenkins), build (Github Actions)

Why Is the Feature Desired?

We need to make sure all our components stay compatible to one another, and that we don't inadvertently break stuff.

Solution Proposal

Reactive builds

all Dataspace Components should trigger Jenkins upon a commit on main, rather than having Jenkins poll the repo every 30 min

Cascaded "nightly" builds

A full cascaded build should be performed periodically. All dataspace components are built and published to ensure compatibility, each one triggering the next. The sequence would be runtime-metamodel -> edc -> [federated-catalog, registration-service, identity-hub]. As a side note, these would not be "true" nightlies, but rather conventional -SNAPSHOT versions, because otherwise we'd have to modify and git-commit the dependency configuration of every downstream project, which seems excessive

Cascaded "release" builds

Similar to cascaded nightlies, we also need to have a single-click build for releasing all components. Thus, the version must be supplied through build parameters, which are tunneled through to all downstream projects.

[github-actions]

This issue is stale because it has been open for 28 days with no activity.