From 79dba020901d06728b2e2a9e5915c01a1684a9e2 Mon Sep 17 00:00:00 2001 From: Wolfgang Hottgenroth Date: Thu, 30 May 2019 16:07:35 +0200 Subject: [PATCH] readme change --- readme.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/readme.md b/readme.md index c0488b0..446bb0c 100644 --- a/readme.md +++ b/readme.md @@ -95,9 +95,11 @@ Then add the following stage into your CI script: - gitlabreleaseuploader.py -p $PRIVATE_TOKEN -i $CI_PROJECT_ID -u $CI_PROJECT_URL -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 +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.) +``Requests`` package. + +Note too, please: this job is releasing the ``gitlabreleaseuploader.py`` script itself, so you see the name of the script twice in the CI script. Don't be confused, the option ``-f`` gets the file to be released. Most information are taken from CI builtin variables, the tag name, release name and release description should be stored in the release info file (here: ``info.json``), which is under version control.