Compare commits

...

2 Commits

Author SHA1 Message Date
amevarashi 3a4f4cc739 Update .gitlab-ci.yml file 2024-04-29 08:35:39 +00:00
amevarashi 41adf10865 Update .gitlab-ci.yml file 2024-04-29 08:22:51 +00:00
1 changed files with 4 additions and 23 deletions

View File

@ -3,20 +3,7 @@
# This specific template is located at:
# https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/dotNET-Core.gitlab-ci.yml
# This is a simple example illustrating how to build and test .NET Core project
# with GitLab Continuous Integration / Continuous Delivery.
#
# ### Specify the Docker image
#
# Instead of installing .NET Core SDK manually, a docker image is used
# with already pre-installed .NET Core SDK.
#
# The 'latest' tag targets the latest available version of .NET Core SDK image.
# If preferred, you can explicitly specify version of .NET Core (e.g. using '2.2-sdk' tag).
#
# See other available tags for .NET Core: https://hub.docker.com/_/microsoft-dotnet
# Learn more about Docker tags: https://docs.docker.com/glossary/?term=tag
# and the Docker itself: https://opensource.com/resources/what-docker
image: mcr.microsoft.com/dotnet/sdk:latest
# ### Define variables
@ -109,13 +96,6 @@ build:
#tests:
# stage: test
# ### Run the tests
#
# You can either run tests for all test projects that are defined in your solution
# with 'dotnet test' or run tests only for specific project by specifying
# a relative path to the directory where it is located (e.g. 'dotnet test ./test/UnitTests').
#
# You may want to define separate testing jobs for different types of testing
# (e.g. integration tests, unit tests etc).
# script:
# - 'dotnet test --no-restore'
@ -129,8 +109,9 @@ release_dev:
- if: $CI_COMMIT_BRANCH == "ci-test" # Run this job when commits are pushed or merged to the dev branch
script:
- 'apk add gitlab-release-cli'
release: # See https://docs.gitlab.com/ee/ci/yaml/#release for available properties
tag_name: 'test-build-$CI_PIPELINE_IID' # The version is incremented per pipeline.
description: 'Automated release based on commit CI_COMMIT_SHA'
- 'ls -l'
release:
tag_name: '$CI_COMMIT_BRANCH-$CI_PIPELINE_IID' # The version is incremented per pipeline.
description: 'Automated release based on commit $CI_COMMIT_SHORT_SHA $CI_COMMIT_TAG'
ref: '$CI_COMMIT_SHA' # The tag is created from the pipeline SHA.