feat: Staging deployments

[gbanu]

Motivation

This PR introduces support for staging deployments directly from the release page, allowing better testing workflow and deployment management across different environments.

Description

Database Schema Changes

• Modified workflow table:
  • Updated label column to support new environment values:
    • NONE
    • TEST_SERVER
    • STAGING_SERVER
    • PRODUCTION_SERVER
• Added type column to environment table:
  • Possible values: TEST, STAGING, PRODUCTION
  • Default value: TEST

The logic to find a deployment workflow has changed and requires a deployment environment as argument, to find deployment workflow for the specific environment.

This logic must be refactored in the future and we should think about how to reduce hardcoded values in our backend.
(Suggestion: for each environment save deployment workflow, and for the workflows save required inputs)

Debugging

• Added launch.json configuration for:
  • Angular debugging
  • TanStack Query DevTools (development mode only)

Testing Instructions

Staging deployments rely on webhooks, so you will need to ensure your backend receives webhooks, you can configure your static ngrok domain with ngrok's guide and set the webhook in the Helios repository.

Prerequisites:

1. Configure webhooks in Helios repository
2. Set up environments:
   • Configure artemis-staging-localci.artemis.cit.tum.de as Staging environment
   • Set up mock-staging-deployment-helios.yml as Staging server deployment environment

Screen.Recording.2025-02-15.at.19.47.52.mov

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.
• I translated all newly inserted strings into English and German.

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
Report missing for bdaf33e1	✅ 1.00%

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (bdaf33e)	Report Missing	Report Missing	Report Missing
Head commit (cfd2279)	5230	320	6.12%

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 (#358)	201	2	1.00%

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%

See your quality gate settings    Change summary preferences

_{Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more}

Footnotes

1. Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct. ↩

[egekocabas]

Can be added later on but staging deployment setup information should be added into the documentation as well
here is my initial how to start using Helios guide