1. Install the Anka Build Virtualization Software onto a macOS host machine.
   • You'll also need an Anka Template and Tag (you can use our getting started repo's create-template script)
2. Install and ensure you have registered a shared (org level; found under org settings/actions) or project specific self-hosted runner (found under repo settings/actions) with GitHub. These runners need to be running on the host machines you run your Anka Virtualization CLI.

   If you want ephemeral VMs to spin up for your CI/CD job, install the github actions runner inside of the node running the Anka Build Virtualization software. For persistent VMs, install the runner inside of the VM and don't use this action.

3. Include a .github/workflows/{whatever}.yml in your repo
4. Make sure to set your mapping key uses: to veertuinc/anka-vm-github-action@vX.X.X
5. There are a few required key/values you need to include under with:: anka-template and commands (see the Inputs section for more information)

name: My Project's CI/CD
on:
  push:
    branches: [ master ]
jobs:
  ios:
    runs-on: [self-hosted, macOS]
    steps:
      - uses: actions/checkout@v2
      - name: build
        id: build
        uses: veertuinc/anka-vm-github-action@v1.2.1-beta
        with:
          anka-template: "10.15.6"
          anka-tag: "base:port-forward-22:xcode11-v1"
          anka-run-options: "--env"
          commands: |
            echo \"Starting build process on \$(hostname)\"
            ./build.sh && \
            ./cleanup.sh
          artifacts: |
            log.txt
            build/binaryfile-v1

The above example will clone your project repo to the github action runner's working directory, pull the Template 10.15.6 and Tag base:port-forward-22:xcode11-v1 from the Registry, prepare an Anka VM using that Template and Tag, execute the commands inside of the VM ensuring Environment Variables are passed in with anka-run-options: "--env", and then upload artifacts ./log.txt and ./build/binaryfile-v1 from the current directory (which is mounted by default into the VM).

Build and test time can be significantly impacted by the default host -> guest mount. It's suggested that you use anka-run-options: "--wait-network --wait-time --no-volume" and then git clone your repo inside of commands:. Or, if you need to upload artifacts (requires they exist on the host), just cd out of the mounted directory (/private/var/tmp/ankafs.0) inside of the VM and then do the git clone so you can execute your builds and tests. This allows you to then move the files you want to upload as an artifact back into the mounted directory so they are seen on the host.**

These are defined under the with: mapping key inside of your workflow yaml.

• Name or UUID of your Anka Template

• Commands you wish to run inside of the Anka VM
• You can use commands: | for multi-line input, OR, you can just use a single line string commands: "echo 123"
• You need to escape nested/inner double quotes \": commands: "echo \"123\""
• You need to escape any dollar signs \$ so that it doesn't interpolate from the host side. Unless of course you wish to pass in something from the host into the VM.
• When interpolating, be sure to use the proper amount of escapes for the desired effect:

  \\\$(echo $HOME)
  \\\$(echo \$HOME)
  \\\$(echo \\\$HOME)

  will result in...

  $(echo /Users/nathanpierce) # HOST level env was interpolated
  $(echo /Users/anka)         # GUEST level env was interpolated
  $(echo $HOME)               # No interpolation

• Name of Anka Tag
• Defaults to latest tag

• Label for the cloned VM that will execute your code
• Defaults to github-actions-${GITHUB_REPOSITORY}-${GITHUB_RUN_NUMBER}-${GITHUB_JOB}-${GITHUB_ACTION}
• Your custom label will have a random number added to the end of it to prevent collisions when two VMs are running on the same node with the same label

• Commands you wish to run outside on the node (host) BEFORE preparation of and execution inside the VM
• You need to escape double quotes \"

• Commands you wish to run outside on the node (host) AFTER preparation of and execution inside the VM
• You need to escape double quotes \"

• Options set for the anka start execution

• Options set for anka run execution

• Options set for anka registry pull execution

• Options to use for github actions exec command
• Do not use single quotes to wrap values { cwd: 'This Wont Work' }
• Supported options: https://github.com/actions/toolkit/blob/master/packages/exec/src/interfaces.ts

• Location where the pull/clone lock file exists
• Defaults to "/tmp"

• Each file you wish to upload and include in the final artifact, newline separated
• Requires the default host <-> guest mounted volume so that the artifact creation/upload code, running on the host, can see the files you specify and are created inside of the VM.

• Name of the artifact (archive) that contains all of the files specified in the artifact-files input
• Defaults to "artifact"

• An absolute or relative file path that denotes the root parent directory of the files being uploaded
• Defaults to "./"

• Skip the registry pull; useful if you do not have a registry or it is down but the Template + Tag are already on the node

These are returned to your workflow.yaml so that subsequent steps can use them.

• The STDOUT and STDERR from the executed commands
• Includes artifact upload output

Usage:

jobs:
  functional-tests-second-agent:
    runs-on: [self-hosted, macOS]
    needs: prep
    steps:
      - uses: actions/checkout@v2
      - name: sleep
        run: "sleep 20"
      - name: pull test 2
        id: pull-test-2
        uses: veertuinc/anka-vm-github-action@v1.2.1-beta
        with:
          anka-template: "10.15.6"
          anka-tag: "base:port-forward-22"
          commands: |
            env
            ls -laht ./
            ls -laht ../
            pwd
            echo \"HERE\" && \
            echo \"THERE HERE WHERE\"

      - name: Check for output
        run: |
          PULL_TEST_STD="${{ steps.pull-test-2.outputs.std }}"
          printf "pull test std ========================\n$PULL_TEST_STD"
          [[ ! -z "$(echo \\"$PULL_TEST_STD\\" | head -n 1)" ]] || exit 50
          [[ ! -z "$(echo \\"$PULL_TEST_STD\\" | grep 'Lock file /tmp/registry-pull-lock-10.15.6 found')" ]] || exit 51
          true

npm install

There are two types of tests we perform:

1. Unit tests (testing functions)

   npm test

2. Functional testing using a workflow yaml (not in this repo)

npm run package

• Figure out how to handle agent lost situations (steps just run indefinitely)
• Support multiple artifacts and files for those artifacts
• Better tests with mocks so we can avoid so much functional testing
• Clone within VM (with skip-clone inputs)