feat: add precise pre-deployment workflow readiness checks

[mertilginoglu]

Motivation

Related issue: #348

Deployments can currently be triggered immediately after a new commit is pushed, even if the corresponding Build workflow for that exact branch and commit has not finished yet. In that case, deployment may fail because the required build artifacts do not exist yet.

This change improves that flow by checking whether required pre-deployment workflows are ready for the exact revision being deployed and warning the user when they are not.

Description

• Added support for configuring requiredPreDeploymentWorkflows per environment, including persistence, DTO changes, and the database migration.
• Added a deployment readiness API that checks the exact source branch and commit against the configured required workflows and reports whether they are READY, WAITING, FAILED, or MISSING_RUN.
• Updated the environment edit form so maintainers can configure required pre-deployment workflows separately from the deployment workflow.
• Updated the deploy confirmation dialog to:
  • show the actual source branch and commit being deployed
  • evaluate readiness for that exact revision
  • warn when required workflows such as Build are still running, failed, or missing
  • link to the latest matching workflow runs for easier inspection
• Passed the commit SHA through the deploy flow so readiness checks are based on the exact revision instead of only the branch name.
• Regenerated the OpenAPI specification and client bindings and added server/client tests for the new readiness behavior.

Testing Instructions

Prerequisites:

• GitHub Account without having any additional access-rights (e.g. admin, owner)
• A repository in Helios with at least one deployable environment
• An environment configured with a deployment workflow and at least one required pre-deployment workflow such as Build
• A branch/commit pair where one required workflow is still running, failed, or has no matching run
• Optional: set Deployment Workflow Branch to a different branch than the source branch to verify the displayed source reference

Flow:

1. Log in to Helios as a Developer.
2. Navigate to the environment settings of a deployable environment.
3. Select a deployment workflow and one or more required pre-deployment workflows, then save the environment.
4. Open the deploy flow for a branch or PR and choose that environment.
5. Verify the confirmation dialog shows the actual source branch and commit that will be deployed.
6. Verify a warning is shown when a required workflow such as Build for the exact branch and commit is still running, failed, or missing.
7. Verify the warning lists the affected workflows and offers links to the latest matching runs.
8. Verify deployment is still possible even when the warning is shown.
9. Re-run the same flow for a branch/commit where all required workflows succeeded and verify the warning is no longer displayed.

Screenshots

Checklist

General

• PR description explains the purpose and changes. (f.e. following the 'Conventional Commits')
• Changes have been tested locally.
• Screenshots have been attached.

Server

• Code is performant and follows best practices
• I documented the Java code using JavaDoc style.

Client

• I documented the TypeScript code using JSDoc style.
• I added multiple screenshots/screencasts of my UI changes.

[github-actions]

There hasn't been any activity on this pull request recently. Therefore, this pull request has been automatically marked as stale and will be closed if no further activity occurs within seven days. Thank you for your contributions.

[codacy-production]

Not up to standards ⛔

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🔴 Metrics 22 complexity

Metric	Results
Complexity	⚠️ 22 (≤ 20 complexity)

View in Codacy

🟢 Coverage 85.21% diff coverage · +0.62% coverage variation

Metric	Results
Coverage variation	✅ +0.62% coverage variation (-1.00%)
Diff coverage	✅ 85.21% diff coverage

View coverage diff in Codacy

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (aace175)	9705	3916	40.35%
Head commit (c139f2e)	9843 (+138)	4033 (+117)	40.97% (+0.62%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#923)	142	121	85.21%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

_{TIP This summary will be updated as you push new changes. Give us feedback}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ca2710c53d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[meryemefe]

I reviewed and tested locally in detail. It looks very good!