Improve Dev Experience

[eliobischof]

In this issue, we define how we want to improve the experience of developing ZITADEL along the continuous integration pipeline: contributing, building, testing and releasing.

Goals

• Developers know what conditions apply so their change is reviewed and merged.
• Developers are able to test a code change locally and manually within 10 minutes under normal conditions.
• Developers know they deliver high-quality functional changes when PR checks pass.
• Developers know they deliver high-quality non-functional changes when they are released.
• Developers enjoy releasing ZITADEL.

Priorities

• build go binary with coverage integration tests #6684
• [Pipeline]: exclude docs PR from full pipeline runs #7661
• Local Development and E2E Testing #7350 moved to Improve Ops Experience #7932
• simplify go generate file handling #5666

[eliobischof]

I rethought the priorities again and think these are the highest in this order:

1. Automate releasing hotfixes by manually passing a commit and a list of minor versions to a GitHub action
2. Speed up the pipeline [Pipeline]: exclude docs PR from full pipeline runs #7661
3. Speed up the pipeline build go binary with coverage integration tests #6684
4. Run benchmark tests on PRs
5. ZITADEL New Login UI: Standardize the way of writing and running acceptance tests. typescript#7

@livio-a do you think the benefits from the first item justify the investments

[livio-a]

I rethought the priorities again and think these are the highest in this order:

1. Automate releasing hotfixes by manually passing a commit and a list of minor versions to a GitHub action
2. Speed up the pipeline [Pipeline]: exclude docs PR from full pipeline runs #7661
3. Speed up the pipeline build go binary with coverage integration tests #6684
4. Run benchmark tests on PRs
5. ZITADEL New Login UI: Standardize the way of writing and running acceptance tests. typescript#7

@livio-a do you think the benefits from the first item justify the investments

Kind of depends on our strategy on release channels / how many back ports we create of a fix and if this fixes to maintenance branches are automated as well.

Edit: improving the performance / pipeline speed would be far more important, e.g. being able to run (integration) tests in parallel