Since I don’t want to install and manage a compatible version of Ruby for my Jekyll version and all dependencies of my website I decided to use Jekylls’ Docker image to develop this page. For my build pipeline in Gitlab CI I wanted to make use of these already existing definitions. I created a simple docker-compose.yml file that loads my source files as a volume, like explained in the documentation of Jekyll’s Docker Image :
For every blog post I specify an image that is shown on the front page. I also use the jekyll-feed plugin to generate an rss feed. This plugin uses the front matter information to generate the necessary meta-data. So the image front matter data is used to fill the <media:thumbnail> tag in the feed. But the jekyll-assets plugin don’t need fully qualified paths to the assets but just its name.
For the last year my current project developed several playmode tests in Unity. These tests get executed by our Jenkins as part of our continues integration strategy. But since we started using them we experienced strange randomly failing tests because they reached their timeout. Today we finally found the issue! Until now (version 2018.2), Unity (on MacOS? We don’t build on Windows machines) slows down when no output device is detected and the user is not logged in.
Previously I only used to have a simple portfolio website at this place. But in my day-to-day work I figured that I actually get in touch with a lot of awesome technology and daily I discover something interesting that is worth writing about to help others in the same situation. This is what this blog will be about. I’ll share my knowledge, give hints on problems related to programming and operating a modern software and tell my opinion on programming styles and recent debates.
Marcus Held