12 Commits
v1.2 ... v1.6

4 changed files with 152 additions and 15 deletions

28
.gitlab-ci.yml Normal file
View File

@ -0,0 +1,28 @@
stages:
- check
- release
build:
stage: check
image: registry.gitlab.com/wolutator/base-build-env:latest
tags:
- hottis
- linux
- docker
script:
- for I in *.py; do python -m py_compile $I; done
- for I in *.py; do python -m pycodestyle --max-line-length=120 $I; done
release:
stage: release
image: registry.gitlab.com/wolutator/base-build-env
tags:
- hottis
- linux
- docker
only:
- release
script:
- python gitlabreleaseuploader.py -p $PRIVATE_TOKEN -i $CI_PROJECT_ID -u $CI_PROJECT_URL
-f gitlabreleaseuploader.py -F info.json -T $CI_COMMIT_REF_NAME

21
gitlabreleaseuploader.py Normal file → Executable file
View File

@ -1,3 +1,5 @@
#!/usr/bin/python
import requests
import json
import argparse
@ -46,7 +48,6 @@ parser.add_argument('--verbose', '-v',
action='store_true',
default=False)
args = parser.parse_args()
print(args)
privateToken = args.privateToken
projectId = args.projectId
@ -73,7 +74,8 @@ if (releaseInfoFilename):
if 'releaseTagTarget' in releaseInfo:
releaseTagTarget = releaseInfo['releaseTagTarget']
if 'createReleaseTag' in releaseInfo:
createReleaseTag = (releaseInfo['createReleaseTag'] in ('true', 'True'))
createReleaseTag = (releaseInfo['createReleaseTag'] in
('true', 'True'))
if 'description' in releaseInfo:
releaseDescription = releaseInfo['description']
@ -108,14 +110,10 @@ uploadResultJson = json.loads(uploadResult.text)
# --- create release tag
if createReleaseTag:
createReleaseTagUrl = "%s/api/v4//projects/%s/repository/tags" % (instanceUrl, projectId)
headers = {"PRIVATE-TOKEN": privateToken, "Content-Type": "application/json"}
# id (required) - The ID or URL-encoded path of the project owned by the authenticated user
# tag_name (required) - The name of a tag
# ref (required) - Create tag using commit SHA, another tag name, or branch name.
# message (optional) - Creates annotated tag.
# release_description (optional) - Add release notes to the git tag and store it in the GitLab database.
createReleaseTagUrl = ("%s/api/v4//projects/%s/repository/tags" %
(instanceUrl, projectId))
headers = {"PRIVATE-TOKEN": privateToken,
"Content-Type": "application/json"}
payloadCreateReleaseTag = {
"tag_name": releaseTag,
@ -124,7 +122,8 @@ if createReleaseTag:
"message": "Tag for release %s" % releaseName
}
createReleaseTagResult = requests.post(createReleaseTagUrl, headers=headers,
createReleaseTagResult = requests.post(createReleaseTagUrl,
headers=headers,
data=json.dumps(payloadCreateReleaseTag))
if createReleaseTagResult.status_code != 201:

View File

@ -1,7 +1,7 @@
{
"releaseTag": "v1.2",
"releaseTag": "v1.6",
"createReleaseTag": "true",
"releaseName": "Third release of the uploader",
"description": "Verbose switch integrated to limit output"
"releaseName": "Seventh release of the uploader",
"description": "Work on readme and change of CI script"
}

110
readme.md Normal file
View File

@ -0,0 +1,110 @@
# Release Uploader for Gitlab
Creating releases on Gitlab seems to work only via the REST API.
This Python script handles the upload of a release file, the creation of
the required release tag in the repository and the creation of the actual
release referring to both the tag and the file.
It supports commandline options and an input file, adjusted to be used in
Gitlab CI scripts.
## Usage
wn@tron:~/workspace-python/gitlabreleaseuploader [master ≡]$ ./gitlabreleaseuploader.py -h
usage: gitlabreleaseuploader.py [-h] --privateToken PRIVATETOKEN --projectId
PROJECTID --projectUrl PROJECTURL --file FILE
[--releaseName RELEASENAME]
[--releaseTag RELEASETAG]
[--releaseTagTarget RELEASETAGTARGET]
[--createReleaseTag]
[--description DESCRIPTION]
[--releaseInfoFile RELEASEINFOFILE]
[--instanceUrl INSTANCEURL] [--verbose]
Gitlab Release Uploader
optional arguments:
-h, --help show this help message and exit
--privateToken PRIVATETOKEN, -p PRIVATETOKEN
Private token to access Gitlab
--projectId PROJECTID, -i PROJECTID
ProjectID of the related project
--projectUrl PROJECTURL, -u PROJECTURL
URL of the related project at Gitlab
--file FILE, -f FILE File to be released
--releaseName RELEASENAME, -n RELEASENAME
Name of the release
--releaseTag RELEASETAG, -t RELEASETAG
Tag of the release in the repo
--releaseTagTarget RELEASETAGTARGET, -T RELEASETAGTARGET
Commit or branch the tag should point to
--createReleaseTag, -c
Shall the release be created here
--description DESCRIPTION, -d DESCRIPTION
Description of the release
--releaseInfoFile RELEASEINFOFILE, -F RELEASEINFOFILE
File containing JSON object with release info (release
tag, create release tag, description
--instanceUrl INSTANCEURL, -I INSTANCEURL
URL of your gitlab instance
--verbose, -v verbose output
wn@tron:~/workspace-python/gitlabreleaseuploader [master ≡]$
### Without release info file:
gitlabreleaseuploader.py -p PRIVATE_TOKEN -i PROJECT_ID -u PROJECT_URL
-f FILE_TO_BE_RELEASED -n RELEASE_NAME
-t RELEASE_TAG -T RELEASE_TAG_TARGET -c
-d RELEASE_DESCRIPTION -I INSTANCE_URL
### With release info file:
Release Info File:
{
"releaseTag": "v1.5",
"createReleaseTag": "true",
"releaseName": "Sixth release of the uploader",
"description": "Now with CI script and automatic release upload (he, eat your own dogfood)"
}
Command:
gitlabreleaseuploader.py -p PRIVATE_TOKEN -i PROJECT_ID -u PROJECT_URL
-f FILE_TO_BE_RELEASED -F RELEASE_INFO_FILE
### Use in CI script
The PRIVATE_TOKEN should not be entered directly into the CI script but added as protected a CI variable to you particular project.
Then add the following stage into your CI script:
release:
stage: release
image: registry.gitlab.com/wolutator/base-build-env
only:
- release
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
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
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.