CI: reduce team's pipeline code duplication via custom GHA actions

cmur2 commented 6 months ago

Description

After migrating existing CI workflows of multiple teams to the monorepo there is some redundancy across GHA workflow code. Due to similarities in tech stack all team's CIs have code to set up Java+Maven, build, run tests and create artifacts like Docker images. This can be seen in https://github.com/camunda/camunda/tree/main/.github/actions where several redundant GHA exists like build-operate-docker, build-tasklist-docker, build-zeebe-docker or collect-test-artifacts, collect-operate-test-artifacts, collect-tasklist-test-artifacts.

Goal: solve common tasks in CI with the same code without redundancies.

This can be achieved by unifying redundant code from e.g. https://github.com/camunda/camunda/tree/main/.github/actions in to single parameterized reusable actions that are used by all teams afterward:

build-frontend action should replace build-operate-fe, build-tasklist-fe
build-operate-setup and build-tasklist-setup and setup-zeebe and setup-maven from Optimize to be merged into one generic action
collect-test-artifacts should replace collect-operate-test-artifacts and collect-tasklist-test-artifacts but retain their fix for https://github.com/camunda/camunda/issues/9959
consider if https://github.com/camunda/camunda/tree/main/.github/actions/login-registry is needed

cmur2 commented 4 months ago

Work for Docker build action in https://github.com/camunda/camunda/pull/19521

cmur2 commented 1 month ago

Subtask https://github.com/camunda/team-infrastructure/issues/675

camunda / camunda

CI: reduce team's pipeline code duplication via custom GHA actions #18214

Description