https://www.christian-knedel.de/en/tags/gitlab-runner/ Recent content in gitlab-runner on Christian Knedel Hugo -- gohugo.io en-us Sun, 16 Feb 2020 00:00:00 +0000 https://www.christian-knedel.de/en/post/2020/february/20200216-synology-trigger/ Sun, 16 Feb 2020 00:00:00 +0000 https://www.christian-knedel.de/en/post/2020/february/20200216-synology-trigger/ In order to trigger a Gitlab pipeline automatically, a so-called trigger must be created. You can create as many triggers as you want in the project settings. These triggers look like this. Of course, the (placeholders) must be replaced. x – + Terminal $ curl -X POST -F token=(TOKEN) -F ref=(BRANCH) http://(ip):(port)/api/v4/projects/(project-id)/trigger/pipeline This curl call can be entered into the Synology task scheduler, Done! https://www.christian-knedel.de/en/post/2019/july/20190717-gitlab-on-synology/ Wed, 17 Jul 2019 00:00:00 +0000 https://www.christian-knedel.de/en/post/2019/july/20190717-gitlab-on-synology/ Here I show how I installed Gitlab and a Gitlab runner on my Synology nas. First, you need to install the GitLab application as a Synology package. Search for “Gitlab” in the “Package Center” and click “Install”. The service listens on port “30000” for me. If everything worked, I call my gitlab with http://SynologyHostName:30000 and see this picture: At the first login I am asked for the future “admin” password. https://www.christian-knedel.de/en/post/2019/july/20190717-synology-gitlab-runner/ Wed, 17 Jul 2019 00:00:00 +0000 https://www.christian-knedel.de/en/post/2019/july/20190717-synology-gitlab-runner/ How do I install a Gitlab runner as a Docker container on my Synology NAS? Step 1: Find Docker image I click on the “Registration” tab in the Synology Docker window and search for Gitlab. I select the Docker image “gitlab/gitlab-runner” and then select the tag “bleeding”. Step 2: Put image/image into operation: Hosts problem My synology-gitlab-insterlation always identifies itself by hostname only. Since I took the original synology-gitlab-package from the package-center, this behavior cannot be changed afterwards.