From fa6745da8343e812d22b37897e2cf352bfe87f90 Mon Sep 17 00:00:00 2001 From: Jason SECULA Date: Thu, 5 Jun 2025 15:09:37 +0200 Subject: [PATCH] Suppression du script de pipeline --- .gitlab-ci.yml | 35 ----------------------------------- 1 file changed, 35 deletions(-) delete mode 100644 .gitlab-ci.yml diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml deleted file mode 100644 index cc153c9..0000000 --- a/.gitlab-ci.yml +++ /dev/null @@ -1,35 +0,0 @@ -# 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/#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/development/cicd/templates/ -# This specific template is located at: -# https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Getting-Started.gitlab-ci.yml - -image: registry.gitlab.com/gitlab-org/release-cli:latest - -stages: # List of stages for jobs, and their order of execution - - release - -create-release: # This job runs in the deploy stage. - stage: release # It only runs when *both* jobs in the test stage complete successfully. - environment: production - script: echo 'Creating release' - release: - tag_name: '$CI_COMMIT_TAG' - name: 'Release $CI_COMMIT_TAG' - description: 'LAPS' - assets: - links: - - name: 'laps.exe' - url: https://gitlab.forge.education.gouv.fr/jsecula/laps/-/raw/main/laps.exe?ref_type=heads&inline=false