从生产分支合并到主分支时,如何在GitLab CI/CD中以增量方式进行版本或标记 [英] How to version or tag incrementally in Gitlab CI/CD when merging from Production to Master branch
本文介绍了从生产分支合并到主分支时,如何在GitLab CI/CD中以增量方式进行版本或标记的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!
问题描述
我正在做一个项目,我想标记或给出一个版本号。当合并发生并且我的配置项/CD成功运行时,我希望GitLab在我的gitci.yml文件中标记V 1.0、1.1等。
推荐答案
您可以使用-semantic release工具。它通过提交前缀自动检测要递增的版本(主要、次要、补丁)。它不仅可以更新GitLab标签,还可以发送延迟通知、更新版本文件或具有任何自定义逻辑
示例设置如下所示(完整的示例链接将位于答案的末尾)
.gitlab-ci.yml
文件
Build Release:
image: node:dubnium
stage: build release
script:
- npm i semantic-release @semantic-release/changelog @semantic-release/commit-analyzer @semantic-release/gitlab @semantic-release/git @semantic-release/npm @semantic-release/release-notes-generator semantic-release-slack-bot
- npx semantic-release
only:
- master
except:
refs:
- tags
variables:
- $CI_COMMIT_TITLE =~ /^RELEASE:.+$/
.releaserc.yaml
文件(与.gitlab-ci.yml处于同一级别)
branches: ['master']
ci: true
debug: true
dryRun: false
tagFormat: '${version}'
# Global plugin options (will be passed to all plugins)
preset: 'conventionalcommits'
gitlabUrl: 'http://gitlab.mycomany.com/' # your gitlab url
slackWebhook: 'https://slack.xxx.com/hooks/q3dtkec6yjyg9x6616o3atgkkr' # if you need slack notifies
# Responsible for verifying conditions necessary to proceed with the release:
# configuration is correct, authentication token are valid, etc...
verifyConditions:
- '@semantic-release/changelog'
- '@semantic-release/git'
- '@semantic-release/gitlab'
- 'semantic-release-slack-bot'
# Responsible for determining the type of the next release (major, minor or patch).
# If multiple plugins with a analyzeCommits step are defined, the release type will be
# the highest one among plugins output.
# Look details at: https://github.com/semantic-release/commit-analyzer#configuration
analyzeCommits:
- path: '@semantic-release/commit-analyzer'
# Responsible for generating the content of the release note.
# If multiple plugins with a generateNotes step are defined,
# the release notes will be the result of the concatenation of each plugin output.
generateNotes:
- path: '@semantic-release/release-notes-generator'
writerOpts:
groupBy: 'type'
commitGroupsSort: 'title'
commitsSort: 'header'
linkCompare: true
linkReferences: true
# Responsible for preparing the release, for example creating or updating files
# such as package.json, CHANGELOG.md, documentation or compiled assets
# and pushing a commit.
prepare:
- path: '@semantic-release/changelog'
- path: '@semantic-release/git'
message: 'RELEASE: ${nextRelease.version}'
assets: ['CHANGELOG.md']
# Responsible for publishing the release.
publish:
- path: '@semantic-release/gitlab'
success:
- path: 'semantic-release-slack-bot'
notifyOnSuccess: true
markdownReleaseNotes: false
fail:
- path: 'semantic-release-slack-bot'
notifyOnFail: true
- 要测试它,请尝试使DEBUG COMMIT:
$ git commit --allow-empty -m "fix: fake release"
(将跳转到路径版本)
完整的工作示例可用here on gitlab
这篇关于从生产分支合并到主分支时,如何在GitLab CI/CD中以增量方式进行版本或标记的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!
查看全文