fix(slack): make slack work with distributed tests #2754
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
1. Enabling Slack Plugin for Fargate runs:
run-cluster.js
similar toensure
plugin. ( plugins are not automatically loaded in main thread for Fargate runs)slack
in cloud workers to avoid sending duplicate notifications.global.artillery.cloudEnabled
variable inrun-fargate
.slack
uses this variable to check if a run URL needs to be included in the notification. It is set inrun.js
when cloud is enabled but was missing inrun-fargate
slack
to both official plugin lists2. Enabling Slack Plugin for Lambda runs
WORKER_ID
toprocess.env
.zip file
version but can't test easily as local changes from other unreleased packages aren't reflected3. A few additional smaller changes have been added:
duration
-seconds
are ceiled rather than floored so that duration in notification doesn't always appear to be 1 second less that theduration
set in the test script.Testing
arrivalRate
,duration
and containercount
ensure
plugin as well as with and withoutfailed checks
.errors
Pre-merge checklist