archives/pleroma-ansible-playbook
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
This repository has been archived on 2023-05-06. You can view files and clone it, but cannot push or open issues or pull requests.
pleroma-ansible-playbook/.gitlab-ci.yml

16 lines
335 B
YAML
Raw Normal View History

fix: implement an upgrade procedure for Pleroma. This commit implements different installation paths when running the pleroma-main role, depending on whether Pleroma needs to be installed for the first time or upgraded. For first time installations the playbook will run through the normal download and installation process and also executes the database migration. If Pleroma is already installed then, by default, the playbook will not re-install Pleroma or re-run the database migration. If the user wants to update Pleroma to a newer version then they can re-run the playbook with the command-line argument '--extra-vars enable_pleroma_upgrade=True'. This commit also introduces a custom module used to compare the installed and downloaded semantic versions of Pleroma. The playbook uses this to see whether the version change is an upgrade, a downgrade or no version change. If it's an upgrade the playbook will proceed with the re-installation of Pleroma. If there is no change then the playbook will skip installation. Finally if it detects that the user is trying to downgrade Pleroma then it will fail. This commit resolves dananglin/pleroma-ansible-playbook#9 and also resolves dananglin/pleroma-ansible-playbook#5
2020-03-06 12:04:48 +00:00
---
ci: test environment docker image for CI pipelines This commit includes a Dockerfile for building a test environment for future CI pipelines. This commit also refactors the GitLab CI pipeline files by splitting the jobs into different files: - .gitlab-ci.yml: Global CI pipeline file. - .gitlab/ci/test-env.gitlab-ci.yml: Jobs to test and publish the docker image for the test environment. - .gitlab/ci/playbook.gitlab-ci.yml: Jobs to test and publish the docker image for the pleroma playbook - .gitlab/ci/templates/docker.gitlab-ci.yml: Template jobs for testing and publishing docker images. Part of dananglin/pleroma-ansible-playbook#17
2020-07-10 07:22:39 +01:00
workflow:
rules:
- if: '$CI_PIPELINE_SOURCE == "merge_request_event"'
- if: '$CI_COMMIT_TAG'
- if: '$CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH'
fix: implement an upgrade procedure for Pleroma. This commit implements different installation paths when running the pleroma-main role, depending on whether Pleroma needs to be installed for the first time or upgraded. For first time installations the playbook will run through the normal download and installation process and also executes the database migration. If Pleroma is already installed then, by default, the playbook will not re-install Pleroma or re-run the database migration. If the user wants to update Pleroma to a newer version then they can re-run the playbook with the command-line argument '--extra-vars enable_pleroma_upgrade=True'. This commit also introduces a custom module used to compare the installed and downloaded semantic versions of Pleroma. The playbook uses this to see whether the version change is an upgrade, a downgrade or no version change. If it's an upgrade the playbook will proceed with the re-installation of Pleroma. If there is no change then the playbook will skip installation. Finally if it detects that the user is trying to downgrade Pleroma then it will fail. This commit resolves dananglin/pleroma-ansible-playbook#9 and also resolves dananglin/pleroma-ansible-playbook#5
2020-03-06 12:04:48 +00:00
stages:
- test
ci: push Docker image to container registry Update the CI pipeline file and Makefile to push the Docker image on tagged releases. Part of dananglin/pleroma-ansible-playbook#14
2020-04-23 00:59:53 +01:00
- publish
fix: implement an upgrade procedure for Pleroma. This commit implements different installation paths when running the pleroma-main role, depending on whether Pleroma needs to be installed for the first time or upgraded. For first time installations the playbook will run through the normal download and installation process and also executes the database migration. If Pleroma is already installed then, by default, the playbook will not re-install Pleroma or re-run the database migration. If the user wants to update Pleroma to a newer version then they can re-run the playbook with the command-line argument '--extra-vars enable_pleroma_upgrade=True'. This commit also introduces a custom module used to compare the installed and downloaded semantic versions of Pleroma. The playbook uses this to see whether the version change is an upgrade, a downgrade or no version change. If it's an upgrade the playbook will proceed with the re-installation of Pleroma. If there is no change then the playbook will skip installation. Finally if it detects that the user is trying to downgrade Pleroma then it will fail. This commit resolves dananglin/pleroma-ansible-playbook#9 and also resolves dananglin/pleroma-ansible-playbook#5
2020-03-06 12:04:48 +00:00
ci: test environment docker image for CI pipelines This commit includes a Dockerfile for building a test environment for future CI pipelines. This commit also refactors the GitLab CI pipeline files by splitting the jobs into different files: - .gitlab-ci.yml: Global CI pipeline file. - .gitlab/ci/test-env.gitlab-ci.yml: Jobs to test and publish the docker image for the test environment. - .gitlab/ci/playbook.gitlab-ci.yml: Jobs to test and publish the docker image for the pleroma playbook - .gitlab/ci/templates/docker.gitlab-ci.yml: Template jobs for testing and publishing docker images. Part of dananglin/pleroma-ansible-playbook#17
2020-07-10 07:22:39 +01:00
include:
- local: '/.gitlab/ci/templates/docker.gitlab-ci.yml'
- local: '/.gitlab/ci/test-env.gitlab-ci.yml'
- local: '/.gitlab/ci/playbook.gitlab-ci.yml'
Reference in a new issue Copy permalink