Artalus / unity3d-ci-example

🍴Additional remote of unity3d CI example project for Travis and CircleCI on Github

unity3d ci example

This project is a PoC to run unity3d tests and builds inside a CI using gableroux/unity3d docker image. It currently creates builds for Windows, Linux, MacOS and webgl. The webgl build is published by the CI to gitlab-pages and github-pages! This repository is hosted on multiple remotes to provide examples for Gitlab-CI, Travis and CircleCI:

• github
• gitlab

Table of Contents generated with DocToc

• Getting started
• Points of interest
  • Build script
  • CI Configuration
    • gitlab-ci
    • WIP: CircleCI
    • Travis
  • Test files
• How to activate
  • Travis
• How to add build targets
  • gitlab-ci
  • iOS support
  • Android support
• How to run scripts manually
  • Test
  • Build
• Shameless plug
• License

Getting started

If you don't have a Unity project yet:

1. Fork this project from github or gitlab
2. Update the readme and remove undesired CI configurations
3. Follow How to activate instructions
4. Configure your CI

If you already have your own project:

1. Copy desired CI file
2. Update the Unity version according to your project version in the CI file. All versions are available at gableroux/unity3d docker image
3. Copy build script (make sure you use the same path as original project, it must be in an Editor folder)
4. Follow How to activate instructions
5. Configure your CI

Points of interest

This is probably what you're looking for.

Build script

Script passed to the unity3d command line as argument to create builds

• See BuildScript.cs

CI Configuration

Pick one, if you're on gitlab, use gitlab-ci as Travis and CircleCI don't support Gitlab as of september 2018, if you're on github, Travis is more popular but CircleCI and gitlab-ci will also work. If you can't decide, see CircleCI vs. GitLab CI/CD and Travis CI vs GitLab.

gitlab-ci

• .gitlab-ci.yml

WIP: CircleCI

TODO

• .circleci/config.yml

Travis

• .travis.yml

Test files

• editmode tests in Assets/Scripts/Editor/EditModeTests
• playmode tests in Assets/Tests/

How to activate

You'll first need to run this locally. All you need is docker installed on your machine.

1. Clone this project

2. Pull the docker image and run bash inside, passing unity username and password to env

   hint: you should write this to a shell script and execute the shell script so you don't have your credentials stored in your bash history. Also make sure you use your Unity3d email address for UNITY_USERNAME env var.

   UNITY_VERSION=2018.2.3f1
   docker run -it --rm \
   -e "UNITY_USERNAME=[e-mail]" \
   -e "UNITY_PASSWORD=example_password" \
   -e "TEST_PLATFORM=linux" \
   -e "WORKDIR=/root/project" \
   -v "$(pwd):/root/project" \
   gableroux/unity3d:$UNITY_VERSION \
   bash

3. In Unity docker container's bash, run once like this, it will try to activate

   xvfb-run --auto-servernum --server-args='-screen 0 640x480x24' \
   /opt/Unity/Editor/Unity \
   -logFile \
   -batchmode \
   -username "$UNITY_USERNAME" -password "$UNITY_PASSWORD"

4. Wait for output that looks like this:

   LICENSE SYSTEM [2017723 8:6:38] Posting <?xml version="1.0" encoding="UTF-8"?><root><SystemInfo><IsoCode>en</IsoCode><UserName>[...]
   

   If you get the following error:

   Can't activate unity: No sufficient permissions while processing request HTTP error code 401

   Make sure your credentials are valid. You may try to disable 2FA in your account and try again. Once done, you should enable 2FA again for security reasons. See #11 for more details.

5. Copy xml content and save as unity3d.alf

6. Open https://license.unity3d.com/manual and answer questions

7. Upload unity3d.alf for manual activation

8. Download Unity_v2018.x.ulf

9. Copy the content of Unity_v2018.x.ulf license file to your CI's environment variable UNITY_LICENSE_CONTENT. Note: if you are doing this on windows, chances are the line endings will be wrong as explained here. Luckily for you, .gitlab-ci.yml solves this by removing \r character from the env variable so you'll be alright .gitlab-ci.yml will then place the UNITY_LICENSE_CONTENT to the right place before running tests or creating the builds.

Travis

Travis doesn't support multiple-lines env variable out of the box and I had troubles with escaping so I recommend encrypting the license file. .travis.yml will decrypt the file and add its content to UNITY_LICENSE_CONTENT env var itself afterward.

travis encrypt-file --pro -r YOUR_TRAVIS_USERNAME/YOUR_TRAVIS_REPO_NAME ./Unity_v2018.x.ulf

For the record, the message I was getting:

The previous command failed, possibly due to a malformed secure environment variable. Please be sure to escape special characters such as ' ' and '$'. For more information, see https://docs.travis-ci.com/user/encryption-keys.

How to add build targets

Supported build targets can be found here

gitlab-ci

Update .gitlab-ci.yml by adding a build section like this:

build-StandaloneWindows64:
  <<: *build
  variables:
    BUILD_TARGET: StandaloneWindows64

iOS support

Help wanted! See #16

Android support

Help wanted! See #17

How to run scripts manually

You can execute the local scripts and specify the path of your Unity executable using UNITY_EXECUTABLE. You may try this in your project before you setup the whole CI so you confirm it works with your current unity version 👍

Test

UNITY_EXECUTABLE="/Applications/Unity/Hub/Editor/2018.2.6f1/Unity.app/Contents/MacOS/Unity" \
  ./local_test.sh

Build

UNITY_EXECUTABLE="/Applications/Unity/Hub/Editor/2018.2.6f1/Unity.app/Contents/MacOS/Unity" \
  ./local_build.sh

Shameless plug

I made this for free as a gift to the video game community so if this tool helped you, I would be very happy if you'd like to support me, support Totema Studio on Patreon: 🍻

License

MIT © Gabriel Le Breton