Skip to content

configure-ci.md

Latest commit

 

History

History
78 lines (56 loc) · 4.17 KB

configure-ci.md

File metadata and controls

78 lines (56 loc) · 4.17 KB

Configuring Continuous Integration

There is a Jenkinsfile included in this repo for use with Jenkins Blue Ocean. Our CI setup makes use of the following:

Jenkins is run inside a docker container, and Holodeck itself is built inside a docker container generated by ue4-docker. ue4-cli is used to make the build process easier.

Configuring a new build server

Install Docker and Python 3.6+, you'll need these later.

Step 1: Build ue4-docker image

You'll want to do this first, since it takes several hours.

  1. Follow the instructions for Configuring Linux

    You might need to add ppas for Python 3.6 (-dev too!) and then python3.6 -m pip install ... to install the pip package

  2. Build the ue4-complete image. Make sure to specify the current Holodeck engine version.

    Note that you will need ~300gb of disk space for this to succeed! The requirements aren't overestimating

Step 2: Install Jenkins

We run Jenkins in a docker container, and use a Docker volume to persist data (instead of a bind mount. Avoids permissions issues).

  1. Install jenkinsci/blueocean

    docker pull jenkinsci/blueocean

  2. Create a docker volume

    docker volume create jenkins-data

  3. Copy this sample startup script somewhere

    docker run \
 -u root \
 --rm \
 -d \
 -p 80:8080 \
 -p 50000:50000 \
 -v jenkins-data:/var/jenkins_home \
 -v /var/run/docker.sock:/var/run/docker.sock \
 jenkinsci/blueocean

    • -u runs Jenkins as the root user in the container

    • --rm cleans up any temporary volumes

    • -p 80:8080 forwards port 8080 in the container to port 80 on the host

    • -v jenkins-data.. binds /var/jenkins_home in the container to the docker volume jenkins-data

    • -v -v /var/run/docker.sock... allows the Jenkins instance inside the container to access the docker deamon outside of the container so that the dockerized Jenkins can have docker containers for builds.

      (we heard you liked docker so we put docker inside your docker so you can docker while you docker)

  4. Configure that script to be run on startup somehow

Step 3: Configure Jenkins

  1. Connect to localhost, wait until you get the Unlock Jenkins screen.

    We will need to put in a password that Jenkins generated, to do so we need to enter the docker container.

  2. Run docker ps - note the name for the jenkinsci/blueocean container (eg vigilant_mayer)

  3. Run docker exec -it vigilant_mayer bash - this should get you a shell inside the container. Get the password from /var/jenkins_home/secrets/initialAdminPassword

  4. Install suggested plugins, create an admin user, wait for it to restart.

  5. Navigate to localhost/blue, you should see the new-looking Jenkins Blue UI instead of the janky old one

  6. Select "Create new Pipeline" -> "Github"

  7. Follow the link to create a new Personal Access Token. Write it down somewhere, once generated you can never see it again!

    Note - I think this token is associated with a user and not the organization, so if my GitHub account (jaydenmilne) gets removed from the org, Jenkins might break.

  8. Select the Holodeck-Engine repo, it should detect the repo and begin to build it

  9. Open a pull request, verify that Jenkins automatically begins to build it.

    If it doesn't there could be an issue with the Jenkins server being publicly accessible, if it isn't on the open internet, Github won't be able to use webhooks to notifiy Jenkins of a new commit or PR. You will have to manually make Jenkins scan the repo every time:

    • Open the configuration for the pipeline
    • "Scan Repository Now" on the left

    If the server is publically availible and build still aren't automatically happening, you may be a victim of JENKINS-50883. See this blog post