Automator CI Scripts

Introduction

These scripts are meant for use with DeepCrawl Automator system and placed in your CI platform after deployment is complete.

Debugging

Bash

For basic debugging output you can edit your bash script to add -x to #!/bin/bash in the start of the file.

If you want to debug via vs-code this extension is useful https://marketplace.visualstudio.com/items?itemName=rogalmic.bash-debug

Powershell

Using vscode is easiest way to lint, autocomplete and debug powershell https://marketplace.visualstudio.com/items?itemName=ms-vscode.PowerShell

Environment Variables

The following environment variables should be set in your CI platform to allow the scripts to work correctly.

AUTOMATOR_TOKEN (access token)

AUTOMATOR_TEST_SUITE_ID (optional) // can be passed into ci as param

example: AUTOMATOR_TEST_SUITE_ID replace with your id

$: ./ci.ps1 -testSuiteId AUTOMATOR_TEST_SUITE_ID
$: ./ci.sh AUTOMATOR_TEST_SUITE_ID

CI Platform Usage

Travis

matrix:
  include:
    - language: bash
      os: linux
      dist: bionic
      sudo: false
      addons:
        apt:
          packages:
            - jq
      script: ./ci.sh

Jenkins

Azure Pipelines

trigger:
  - master
pr:
  - master
pool:
  vmImage: "vs2017-win2016"

steps:
  - task: PowerShell@2
    env:
      AUTOMATOR_TEST_SUITE_ID: $(testId)
      AUTOMATOR_TOKEN: $(token)
    inputs:
      filePath: "$(System.DefaultWorkingDirectory)/ci.ps1"

General

Run either script with the correct enviroment variables and that should start the test suite build and poll for results.