# This file is a template, and might need editing before it works on your project. # This is a sample GitLab CI/CD configuration file that should run without any modifications. # It demonstrates a basic 3 stage CI/CD pipeline. Instead of real tests or scripts, # it uses echo commands to simulate the pipeline execution. # # A pipeline is composed of independent jobs that run scripts, grouped into stages. # Stages run in sequential order, but jobs within stages run in parallel. # # For more information, see: https://docs.gitlab.com/ee/ci/yaml/index.html#stages # # You can copy and paste this template into a new `.gitlab-ci.yml` file. # You should not add this template to an existing `.gitlab-ci.yml` file by using the `include:` keyword. # # To contribute improvements to CI/CD templates, please follow the Development guide at: # https://docs.gitlab.com/ee/development/cicd/templates.html # This specific template is located at: # https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Getting-Started.gitlab-ci.yml # Python-specific template is located at # https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Python.gitlab-ci.yml # Official language image. Look for the different tagged releases at: # https://hub.docker.com/r/library/python/tags/ image: python:3.10 #Otherwise use 'latest' # Change pip's cache directory to be inside the project directory since we can # only cache local items. variables: PIP_CACHE_DIR: "$CI_PROJECT_DIR/.cache/pip" # https://pip.pypa.io/en/stable/topics/caching/ cache: paths: - .cache/pip before_script: - python --version ; pip --version # For debugging - pip install virtualenv - virtualenv venv - source venv/bin/activate - pip install --upgrade pip setuptools wheel stages: # List of stages for jobs, and their order of execution - build - test - deploy build-job: # This job runs in the build stage, which runs first. stage: build script: - echo "Compiling the code..." - pip install h5py --only-binary h5py - pip install -e . - echo "Compile complete." artifacts: paths: - build/* unit-test-job: # This job runs in the test stage. stage: test # It only starts when the job in the build stage completes successfully. script: - echo "Running unit tests..." - pip install pytest - pip install pytest-cov - pip install -e . - pytest --junitxml=report.xml #- python -m pytest # tests/ artifacts: paths: - report.xml reports: junit: report.xml rules: - changes: - src/**/* - tests/**/* when: always pages: stage: deploy script: - apt update - apt-get -y install graphviz - pip install -U sphinx m2r2 furo pyUML pydot=2.0.0 gprof2dot - pip install graphviz=2.50.0 - pip install -e . - mkdir public - cd public - mkdir diagrams - cd ../ - cp docs/diagrams/* public/diagrams #- cp docs/diagrams/class_diagram.py public/diagrams - cd public/diagrams - python class_diagram.py - cd ../../ - sphinx-build -b html docs/source public #- mv docs/diagrams ./public artifacts: paths: - public #only: #- master deploy-job: # This job runs in the deploy stage. stage: deploy # It only runs when *both* jobs in the test stage complete successfully. environment: production script: - echo "Deploying application..." - echo "Application successfully deployed."