Skip to main content

Shell Scripts

Introduction​

The Deepcrawl Automate shell scripts allow your CI platform to start a crawl on a Lumar Protect development environment and waits for a result. They can be found in the main repo (ci.sh and ci.ps) and should be placed in your CI platform after deployment is complete.

Environment Variables​

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

AUTOMATOR_USER_KEY_ID (-userKeyId) (Key ID for generated API Key)

AUTOMATOR_USER_KEY_SECRET (-userKeySecret) (Secret value for generated API Key)

AUTOMATOR_TEST_SUITE_ID (-testSuiteId) can be passed into ci as param or provided as environmental variable

AUTOMATOR_START_ONLY (-startOnly) (optional, set to `1` or `true` to run Deepcrawl Automate without blocking a build)

PowerShell​

Example 1:

$env:AUTOMATOR_USER_KEY_ID = <number>
$env:AUTOMATOR_USER_KEY_SECRET = <string>
$env:AUTOMATOR_TEST_SUITE_ID = <string>
$env:AUTOMATOR_START_ONLY = <boolean> | 1 | 0
./ci.ps1

Example 2:

  • replace AUTOMATOR_TEST_SUITE_ID with your id
  • (optional) replace AUTOMATOR_START_ONLY and can be set to 1, 0, false or true
$env:AUTOMATOR_USER_KEY_ID = <number>
$env:AUTOMATOR_USER_KEY_SECRET = <string>
./ci.ps1 -testSuiteId AUTOMATOR_TEST_SUITE_ID -startOnly AUTOMATOR_START_ONLY

Bash​

Example 1

export AUTOMATOR_TEST_SUITE_ID=<string>
export AUTOMATOR_USER_KEY_SECRET=<string>
export AUTOMATOR_TEST_SUITE_ID=<number>
export AUTOMATOR_START_ONLY=<boolean> | 0 | 1
./ci.sh

Example 2

  • replace AUTOMATOR_TEST_SUITE_ID with your id
export AUTOMATOR_USER_KEY_SECRET=<string>
export AUTOMATOR_TEST_SUITE_ID=<number>
./ci.sh AUTOMATOR_TEST_SUITE_ID

Authentication variables​

The authentication variables AUTOMATOR_USER_KEY_ID and AUTOMATOR_USER_KEY_SECRET can be retrieved from either your Lumar API settings, or by generating them in the API

General​

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

Using Deepcrawl Automate scripts without blocking builds​

From time to time, you may want to use Deepcrawl Automate without letting your CI system wait for the crawl to complete, or allowing the script impact whether your build succeeds. In this case, you can add the AUTOMATOR_START_ONLY environment variable set to true or 1. You can also pass the value as a second script argument after test suite ID. This flag modifies the behaviour of the script to start a test suite test, then return without polling for a result.

In this case Lumar Protect will send an email or other notification about the status of your tests, and the test results will be available in the Lumar Protect app.

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