Add automatic release pipeline
This commit is contained in:
parent
3e1d5cf1b2
commit
cec51554d0
2 changed files with 31 additions and 15 deletions
29
.gitlab-ci.yml
Normal file
29
.gitlab-ci.yml
Normal file
|
|
@ -0,0 +1,29 @@
|
|||
stages:
|
||||
- release
|
||||
|
||||
create_release:
|
||||
stage: release
|
||||
image: registry.gitlab.com/gitlab-org/release-cli:latest
|
||||
only:
|
||||
- tags
|
||||
rules:
|
||||
- if: $CI_COMMIT_TAG =~ /^[0-9]+\.[0-9]+\.[0-9]+.*$/
|
||||
script:
|
||||
- |
|
||||
# Get the previous tag to generate changelog
|
||||
PREVIOUS_TAG=$(git describe --tags --abbrev=0 $CI_COMMIT_TAG^ 2>/dev/null || echo "")
|
||||
|
||||
# Generate changelog
|
||||
if [ -n "$PREVIOUS_TAG" ]; then
|
||||
CHANGELOG=$(git log --pretty=format:"* %s (%an)" $PREVIOUS_TAG..$CI_COMMIT_TAG)
|
||||
else
|
||||
CHANGELOG=$(git log --pretty=format:"* %s (%an)" $CI_COMMIT_TAG)
|
||||
fi
|
||||
|
||||
# Save changelog to file for release
|
||||
echo -e "## Changes\n$CHANGELOG" > changelog.md
|
||||
release:
|
||||
name: 'Release $CI_COMMIT_TAG'
|
||||
tag_name: '$CI_COMMIT_TAG'
|
||||
description: './changelog.md'
|
||||
ref: '$CI_COMMIT_TAG'
|
||||
17
README.md
17
README.md
|
|
@ -145,18 +145,5 @@ docker compose -f hedgedoc/docker-compose.yml up -d
|
|||
- More automatisation when installing the environment.
|
||||
- Add more services
|
||||
- [ ] Matrix/Synapse + Element
|
||||
- Better reuse of gits for updating and maintainment.
|
||||
|
||||
## Changelog
|
||||
|
||||
0.0.3
|
||||
- Fix the postgres-loose-it-all-volume mistake...
|
||||
+ Volume have to be `/var/lib/postgresql/data` not `/var/lib/postgresql/` or everthing will be deleted, if the container is rebuild.
|
||||
- More robust Nextcloud config.
|
||||
0.0.2
|
||||
- Make things more agnostic by
|
||||
+ use original gits
|
||||
+ have envs and overrides in parent dirs
|
||||
- better automatisation with copy_overrides-bash and create_infra.bash on root level.
|
||||
0.0.1
|
||||
- First release.
|
||||
- Fix all the Nextcloud errors
|
||||
+ Your web server is not properly set up to resolve `.well-known` URLs, failed on: `/.well-known/webfinger` For more details see the documentation ↗.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue