From 479cdda780391d364d1c5841a15da850acd9071b Mon Sep 17 00:00:00 2001
From: GotthardG <51994228+GotthardG@users.noreply.github.com>
Date: Thu, 10 Apr 2025 18:53:33 +0200
Subject: [PATCH] Add job processing system with streaming endpoint

Introduced a `processing` router to handle job streaming using server-sent events. Added `Jobs` and `JobStatus` models for managing job-related data, along with database creation logic. Updated the `sample` router to create new job entries during experiment creation.
---
 .gitlab-ci.yml | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index a8c74de..26ba8dc 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -60,13 +60,17 @@ release:
     TWINE_USERNAME: gitlab-ci-token
     TWINE_PASSWORD: $CI_JOB_TOKEN
     ENVIRONMENT: test
+  before_script:
+    - sudo chown -R gitlab-runner:gitlab-runner "$CI_PROJECT_DIR" || true
+    - sudo find "$CI_PROJECT_DIR" -type f -exec chmod 644 {} + || true
+    - sudo find "$CI_PROJECT_DIR" -type d -exec chmod 755 {} + || true
   script:
     # build and run commands within docker container context
     - docker compose build backend
 
     # Run commands inside your 'backend' service container
     - docker compose run --rm backend mkdir -p /app/backend/ssl
-    - docker compose run --rm backend bash make_openapi_client.sh
+    - docker compose run --rm -e ENVIRONMENT=test backend bash make_openapi_client.sh
 
     # After script finishes execution within the container,
     # revert to the runner environment context if needed