Latest release issues

Lack of Expertise in Core Release Management:

We're facing a gap in our team's knowledge regarding core release procedures. Previously, team members that already departed handled this responsibility.

Absence of Separate Release Branch:

Tickets from AO and SELV ended up in our core repository, causing uncertainty about whether to include them in releases. Usually, if unsure, we revert or restore. Additionally, the lack of a detailed board outlining inclusions and exclusions further complicated matters.

Sequential Frontend Releases:

Releasing the frontend sequentially raised questions about whether each repository required an update. Complications arose recently due to issues with the ui-layout build after changes from BuQ. Initially attempted to rectify, but it turned out to be a frontend error, leading us to proceed without releasing ui-layout.

Frequent Jenkins Errors:

Jenkins often encounters errors in deleting files from the folder ..../workspace/some_pipeline. SSH connection and manual deletion become necessary. Initially lacked the key, but obtained it from a team member. We should pay more attention to our Credential pages - updating them and providing clearer instructions. Currently, many information/files transition from one person to another.

Excessive Manual Steps in Release Process:

Releasing requires an excessive amount of manual clicking.

Missing Commit Descriptions:

Commit descriptions are absent, which would be highly beneficial during releases. For instance, a version change in SchemaSpy lacks description, due to that it wasn't clear if it must be released.