Initial commit

Author: X-SP33D

.gitignore

@@ -0,0 +1,203 @@
+__pycache__/
+scripts/
+*.DS_Store
+.rsync-exclude.txt
+.ipynb_checkpoints
+*.egg-info
+*.pyc
+build/
+dist/
+.tox/
+licenses_example/choosealicense.com
+.idea/
+*.iml
+.gradle/
+venv/
+.venv-*
+lib64/
+bin/
+activate
+**/mypy-precision/
+**/.coverage
+*.log
+.ipynb
+.vscode/
+*.code-workspace
+**/venv-*/*
+
+# VSCode extensions
+npm-debug.log
+Thumbs.db
+**/node_modules/
+**/out/
+**/.vs/
+tsconfig.lsif.json
+*.lsif
+*.db
+*.vsix
+
+# Dependency directories
+node_modules
+jspm_packages
+
+# User-specific stuff:
+.idea
+
+# Gradle:
+.gradle
+build
+
+# IntelliJ
+/out/
+*/**/out/
+
+# OS generated files #
+.DS_Store
+.DS_Store?
+._*
+.Spotlight-V100
+.Trashes
+ehthumbs.db
+Thumbs.db
+
+*.py[cod]
+*$py.class
+bin/
+*.cfg
+!wayflowcore/setup.cfg
+cx_Oracle*
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+/lcnc/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/wayflowcore/build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/#use-with-ide
+.pdm.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# User-specific stuff:
+.idea
+.DS_Store
+Thumbs.db
+
+*.pklz
+*.sqlite

.gitlab-ci.yml

@@ -0,0 +1,9 @@
+image : $GITLAB_CI_CD_IMAGE
+include:
+  - local: '.gitlab/jobs/templates/get_private_branch.yml'
+  - local: '.gitlab/jobs/templates/get_merge_request_id.yml'
+  - local: '.gitlab/jobs/schedule_mergegate.yml'
+  - local: '.gitlab/jobs/schedule_regression.yml'
+
+stages:
+  - trigger

.gitlab/CHANGELOG.md

@@ -0,0 +1,5 @@
+# Changelog
+
+## [1.0.0] - 2025-07-15
+### Added
+- Initial version of the GitLab CI Integration.

.gitlab/README.md

@@ -0,0 +1,37 @@
+# GitLab CI Integration
+
+## Overview
+
+This folder contains Giltab CI/CD configurations and supporting files. It contains jobs that are designed to interface with Jenkins, allowing manual trigger jobs to initiate Jenkins pipelines from within Gitlab. The folder includes:
+- GitLab CI manual jobs
+
+Currently, we support three key pipelines:
+- **Regression Pipeline** – for running regression tests
+
+Each job is a scheduler that initiates a corresponding Jenkins pipeline.
+
+## Getting Started
+
+This guide helps you understand the structure, setup, and usage of the GitLab CI integration with Jenkins. 
+
+## Prerequisites
+
+- Access to the Gitlab repository hosted in **Gitlab**
+- Jenkins access token to trigger pipelines
+- Gitlab project access token
+- Proper configuration in the Jenkins job to accept remote triggers
+
+## Configuration
+
+1. update the `.gitlab/jobs` folder to add your jobs and update `.gitlab-ci.yml` file to include or reference manual jobs you added.
+2. Ensure Jenkins is configured to accept remote builds via token or webhook.
+3. Link Jenkins job names and parameters in the GitLab job scripts as needed.
+4. Add required environment variables in GitLab CI/CD settings (e.g., `GITLAB_MERGE_BOT_TOKEN`, `JENKINS_BOT_AUTH`).
+
+## How to Use the Jobs
+
+### Regression Pipeline
+
+This pipeline is triggered manually ,and it's responsibility is to trigger the regression pipeline in jenkins.
+
+

.gitlab/jobs/schedule_mergegate.yml

@@ -0,0 +1,27 @@
+schedule_mergegate:
+  stage: trigger
+  when: manual
+  variables:
+    DELETE_BRANCH:
+      value: "false"
+  script:
+    - !reference [ .get_merge_request_id, script ]
+    - !reference [ .get_private_branch, script ]
+    - |
+      curl -X POST "${JENKINS_URL}/job/Regression/job/mergegate/buildWithParameters" \
+      --user "$JENKINS_BOT_AUTH" \
+      --data-urlencode "BRANCH=$PRIVATE_BRANCH" \
+      --data-urlencode "PUBLIC_BRANCH=$CI_COMMIT_REF_NAME" \
+      --data-urlencode "EMAIL=$GITLAB_USER_EMAIL" \
+      --data-urlencode "PUBLIC_PRID=$PUBLIC_MERGE_REQUEST_ID" \
+      --data-urlencode "PRIVATE_PRID=$PRIVATE_MERGE_REQUEST_ID" \
+      --data-urlencode "COMMIT=$PRIVATE_MERGE_REQUEST_COMMIT_HASH" \
+      --data-urlencode "PUBLIC_COMMIT=$CI_COMMIT_SHA" \
+      --data-urlencode "PR_SOURCE_PROJECT=$CI_PROJECT_NAMESPACE" \
+      --data-urlencode "PR_SOURCE_REPOSITORY=$CI_PROJECT_NAME" \
+      --data-urlencode "PR_SOURCE_ID=$PUBLIC_MERGE_REQUEST_ID" \
+      --data-urlencode "USE_${REPOSITORY_HOST}=true" \
+      --data-urlencode "DELETE_BRANCH=$DELETE_BRANCH" \
+      --data-urlencode "${REPOSITORY_HOST}_PIPELINE_ID=$CI_PIPELINE_ID"
+    - echo "waiting for external pipeline to appear on gitlab UI"
+    - sleep 50

.gitlab/jobs/schedule_regression.yml

@@ -0,0 +1,23 @@
+schedule_regression:
+  stage: trigger
+  when: manual
+  variables:
+    llmCodeGenSubmodule:
+      value: "all"
+    dryRunSubmodule:
+      value: "same"
+  script:
+    - !reference [ .get_private_branch, script ]
+    - |
+      curl -X POST "${JENKINS_URL}/job/Regression/job/regression/buildWithParameters" \
+      --user "$JENKINS_BOT_AUTH" \
+      --data-urlencode "BRANCH=$PRIVATE_BRANCH" \
+      --data-urlencode "PUBLIC_BRANCH=$CI_COMMIT_REF_NAME" \
+      --data-urlencode "PUBLIC_COMMIT=$CI_COMMIT_SHA" \
+      --data-urlencode "PR_SOURCE_PROJECT=$CI_PROJECT_NAMESPACE" \
+      --data-urlencode "PR_SOURCE_REPOSITORY=$CI_PROJECT_NAME" \
+      --data-urlencode "EMAIL=$GITLAB_USER_EMAIL" \
+      --data-urlencode "llmCodeGenSubmodule=$llmCodeGenSubmodule" \
+      --data-urlencode "USE_${REPOSITORY_HOST}=true" \
+      --data-urlencode "${REPOSITORY_HOST}_PIPELINE_ID=$CI_PIPELINE_ID"
+    - sleep 50

.gitlab/jobs/templates/get_merge_request_id.yml

@@ -0,0 +1,44 @@
+.get_merge_request_id:
+  script:
+    - |
+      #!/bin/bash
+
+      # Encode the branch name
+      ENCODED_BRANCH_NAME=$(echo -n "${CI_COMMIT_REF_NAME}" | sed 's|/|%2F|g')
+      API_URL="$GITLAB_URL/projects/$CI_PROJECT_ID"
+
+      echo "Checking merge requests for branch: '${CI_COMMIT_REF_NAME}'"
+
+      # Temporary file for HTTP response
+      HTTP_RESPONSE=$(mktemp)
+
+      # Make API call and capture response + HTTP code
+      HTTP_STATUS=$(curl -s -o "$HTTP_RESPONSE" -w "%{http_code}" \
+        --header "PRIVATE-TOKEN: $GITLAB_BOT_TOKEN" \
+        "${API_URL}/merge_requests?state=opened&source_branch=$ENCODED_BRANCH_NAME")
+
+      if [ "$HTTP_STATUS" -ne 200 ]; then
+        echo "Error: Received HTTP status $HTTP_STATUS when fetching merge requests. Exiting."
+        cat "$HTTP_RESPONSE"
+        rm "$HTTP_RESPONSE"
+        exit 1
+      fi
+
+      RESPONSE=$(cat "$HTTP_RESPONSE")
+      rm "$HTTP_RESPONSE"
+
+      # Count merge requests by counting occurrences of "iid"
+      MR_COUNT=$(echo "$RESPONSE" | grep -o '"iid":' | wc -l)
+
+      if [ "$MR_COUNT" -eq 0 ]; then
+        echo "No merge requests found for branch '${CI_COMMIT_REF_NAME}'."
+        exit 1
+      elif [ "$MR_COUNT" -gt 1 ]; then
+        echo "Error: More than one merge request ($MR_COUNT) is open for branch '${CI_COMMIT_REF_NAME}' in $CI_PROJECT_NAMESPACE/$CI_PROJECT_NAME."
+        exit 1
+      else
+        echo "One merge request found for branch '${CI_COMMIT_REF_NAME}'."
+        MR_ID=$(echo "$RESPONSE" | grep -o '"iid":[0-9]*' | head -n1 | cut -d ':' -f2)
+        export PUBLIC_MERGE_REQUEST_ID="$MR_ID"
+        echo "PUBLIC_MERGE_REQUEST_ID='$PUBLIC_MERGE_REQUEST_ID'"
+      fi