stephan
/
blog
1
0
Fork 0
Code Issues Pull Requests Releases 1 Wiki Activity

finalized deployment article, adjusted drone build definition
continuous-integration/drone/push Build is failing Details

This commit is contained in:
Stephan Dörfler 2020-02-10 18:16:20 +01:00
parent 4ac9c8d8aa
commit 486474fcef
2 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.drone.yml
View File

@ -1,6 +1,6 @@
kind: pipeline kind: pipeline
type: docker type: docker
name: default name: Blog build and release
steps: steps:
- name: build - name: build
@ -11,8 +11,6 @@ steps:
- name: docker - name: docker
image: plugins/docker image: plugins/docker
settings: settings:
username:
password:
repo: registry.while-false.de/blog repo: registry.while-false.de/blog
tags: tags:
- 'latest' - 'latest'

10
content/blog/003-writing-articles/index.md
View File

@ -64,7 +64,7 @@ The worker then connected to the drone server. In the UI of the drone server I c
```yaml ```yaml
kind: pipeline kind: pipeline
type: docker type: docker
name: default name: Blog build and release
steps: steps:
- name: build - name: build
@ -88,4 +88,10 @@ For now I only require two steps:
1. build the gatsby project 1. build the gatsby project
2. build the new docker image and push it to the registry 2. build the new docker image and push it to the registry
Then, the last required step is to update the running container to the new version. The event on which to react would be the upload to the registry. There are some ways to handle this myself using webhooks, but as with the build trigger I decided to take a route a little more convenient: use [Watchtower](https://containrrr.github.io/watchtower). I tried watchtower before and don't feel comfortable blindly updating every container I run, so I [configure it to just watch the one blog container and update that automatically](https://containrrr.github.io/watchtower/container-selection/). An additional benefit of the drone build is this beatiful badge, every project has nowadays, conveniently prepared as markdown:
[![Build Status](https://drone.while-false.de/api/badges/stephan/blog/status.svg)](https://drone.while-false.de/stephan/blog)
```markdown
[![Build Status](https://drone.while-false.de/api/badges/stephan/blog/status.svg)](https://drone.while-false.de/stephan/blog)
```
Then, the last required step is to update the running container to the new version. The event on which to react would be the upload to the registry. There are some ways to handle this myself using webhooks, but as with the build trigger I decided to take a route a little more convenient: use [Watchtower](https://containrrr.github.io/watchtower). I tried watchtower before and don't feel comfortable blindly updating every container I run, so I [configure it to just watch the one blog container and update that automatically](https://containrrr.github.io/watchtower/container-selection/). As I am the only one pushing updates of the image for the blog I can take precautions when I know something will break.