With npx checkly test --record cli script we can specify GIT meta data enviroment variables to overwrite and existing or set and non-existing values.
This doesnt work with npx checkly trigger --record script.
Usecase:
We have our tests in a project, our pipeline packages the project and pushes to a tool called 'Octopus Server' to actually release the production files. As part of release process we want to trigger the tests to run.
I have the trigger script working but setting the git meta data env values does not work.
Here is full script we're using (its in powershell)
$env:CHECKLY_API_KEY="Our Key"
$env:CHECKLY_ACCOUNT_ID="Our Account ID"
$env:CHECKLY_REPO_BRANCH="A branch name"
$env:CHECKLY_REPO_COMMIT_OWNER="Person who triggered release"
$env:CHECKLY_TEST_ENVIRONMENT="Our Test Environment"
$env:CHECKLY_REPO_COMMIT_MESSAGE="E2E Test Run"
npx checkly trigger --record --tags=some-tag -e ENVIRONMENT_URL=https://dynamic-uat-or-prod-url.com --test-session-name="Product Name: https://dynamic-uat-or-prod-url.com" --location=eu-west-1 --reporter=ciI've also tried specifying the Git meta data via the -e setting which also doesn't work.
Please authenticate to join the conversation.
In Review
π‘ Feature Request
CLI
Over 2 years ago

Nick McBurney
Get notified by email when there are changes.
In Review
π‘ Feature Request
CLI
Over 2 years ago

Nick McBurney
Get notified by email when there are changes.