wn/gitlabreleaseuploader
Archived
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

more readme work

Browse Source
This commit is contained in:
Wolfgang Hottgenroth 2019-05-30 15:55:06 +02:00
parent 131ab9e789
commit 3e09e510da
Signed by: wn
GPG Key ID: B586EAFCDF2F65F4
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
readme.md
View File

@ -89,18 +89,18 @@ Then add the following stage into your CI script:
release: release:
stage: release stage: release
image: registry.gitlab.com/wolutator/base-build-env image: registry.gitlab.com/wolutator/base-build-env
tags:
- hottis
- linux
- docker
only: only:
- release - release
script: script:
- gitlabreleaseuploader.py -p $PRIVATE_TOKEN -i $CI_PROJECT_ID -u $CI_PROJECT_URL - gitlabreleaseuploader.py -p $PRIVATE_TOKEN -i $CI_PROJECT_ID -u $CI_PROJECT_URL
-f gitlabreleaseuploader.py -F info.json -T $CI_COMMIT_REF_NAME -f gitlabreleaseuploader.py -F info.json -T $CI_COMMIT_REF_NAME
(Note, please: this stage definition is for a docker worker. It uses my ``base-build-env`` image, which already contains the
uploader script. However, it is no problem to use the uploader script also in different environments. It just depends on the
``Requests`` package.)
Most information are taken from CI builtin variables, the tag name, release name and release description should be stored in Most information are taken from CI builtin variables, the tag name, release name and release description should be stored in
the info file, which is under version control. the release info file (here: ``info.json``), which is under version control.
To avoid releasing a file with everything single push to an arbitrary branch, add the ``only`` block. To avoid releasing a file with everything single push to an arbitrary branch, add the ``only`` block.