1 May 2019

Setting up Jenkins on Linux with a Windows Build Executor

Basics/ Getting the master online

So setup jenkins… It’s really not that hard, apt-get does the trick for the most part on linux, then if you wanna get fancy, install nginx, and have it forward to jenkins which by default is listening on port 8080. If you don’t know how to make it fancy, don’t bother, it’s not worth the wasted time!

I usually like to make all of my infrastructure codified to be configured how it is from scratch. Jenkins is entirely configured via .xml files on the build master –there are no databases! The plugins are just downloaded jar. All configuration is in /var/lib/jenkins. All build configurations and logs are in there too! Weird, so how do you do backups and restores? You can just use git if you want!

Configuration as Code Though?

Down the road, I intend to have all the jobs mounted as an NFS share (with ZFS doing snapshots on it in the background). After that I’ll lean heavily on the /var/lib/jenkins/init.groovy and /var/lib/jenkins/init.groovy.d/ scripts to have jenkins configuration as code which should work pretty well.

Refs:

Create a Build Agent (on windows)

Out of the box, build jobs can run directly on the master node. But we want to run windows jobs for things like Unity and Unreal4Engine. So we just need to…

Once that’s done with, you should be able to execute your build jobs from jenkins on your gaming machine!

ref: https://theithollow.com/2016/04/11/add-a-jenkins-node-for-windows-powershell/

Categories: infrastructure - jenkins