Improve CI Workflows

[paullatzelsperger]

WHAT

Tractus-X EDC Github Actions workflows have become quite complex, and in that there are several suboptimal spots and room for improvement. Specifically:

1. workflows, that are intended for manual-only tasks should be prefixed manual-, e.g. manual-docker-publish.yaml instead of publish-docker.yaml
2. workflows should be reused. Currently, the publish-new-release.yaml duplicates steps for publishing docker, maven, openapi, etc. This should get consolidated.
3. improvement to the release flow:

• configurable base: currently releases are always created off of main, but for isolated bugfixes we will need an option to do it off of some other branch
• duplicated branches: we currently have releases and release/x.y.z, which seems spurious. We can probably skip the releases branch altogether.

4. introduction of intermediate builds: the run-all-tests.yaml job gets a new scheduled trigger, that runs tests and publishes a snapshot version every Monday at 03:00. Lets see how far we get with weekly builds, we can always move to nightlies later. The naming scheme is X.Y.Z-<YEAR><MONTH><DAY>-SNAPSHOT

WHY

Implements this decision record

HOW

• Prefix publish workflows with trigger- #1446
• Make manual workflows reusable #1447
• Release workflow: make base branch configurable #1448
• Introduce intermediate builds #1449

FURTHER NOTES

// anything else you want to outline

Please be sure to take a look at
our contribution guidelines and
our PR etiquette.

[github-actions]

This issue is stale because it has been open for 4 weeks with no activity.

[ndr-brt]

@paullatzelsperger @rafaelmag110 can this be closed?

[github-actions]

This issue is stale because it has been open for 2 weeks with no activity.

[github-actions]

This issue was closed because it has been inactive for 7 days since being marked as stale.