-
Notifications
You must be signed in to change notification settings - Fork 1.5k
DEVPROD-16438 - migrate perf.send to cedar_report endpoint #1679
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
||
echo "Response Body: $response_body" | ||
echo "HTTP Status: $http_status" | ||
add_expansions_to_env: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since all expansions appear to be available during task execution and via expansions.update
, do we need this step?
script: | | ||
if [ "${requester}" == "commit" ]; then | ||
echo "is_mainline: true" >> expansion.yml | ||
else | ||
echo "is_mainline: false" >> expansion.yml | ||
fi | ||
|
||
echo "parsed_order_id: $(echo "${revision_order_id}" | awk -F'_' '{print $NF}')" >> expansion.yml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we move this script into a single shell.exec
command at line 793? It looks like we might be able to skip expansions.update
, which could help keep the CI file a bit more concise.
@@ -375,7 +375,7 @@ functions: | |||
STREAM_TYPE="netty" AUTH="${AUTH}" SSL="${SSL}" NETTY_SSL_PROVIDER="${NETTY_SSL_PROVIDER}" MONGODB_URI="${MONGODB_URI}" \ | |||
TOPOLOGY="${TOPOLOGY}" COMPRESSOR="${COMPRESSOR}" JAVA_VERSION="${JAVA_VERSION}" \ | |||
AZUREKMS_KEY_VAULT_ENDPOINT=${testazurekms_keyvaultendpoint} AZUREKMS_KEY_NAME=${testazurekms_keyname} \ | |||
.evergreen/run-tests.sh | |||
.evergreen/run-tests.sh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are a few random line break / whitespace changes. Could we revert those to help preserve the git history on those lines?
The perf.send functionality in evergreen is no longer maintained and is not the preferred method of sending performance data to the signal processing service. This PR updates the evergreen yaml file to instead send the data down stream using the preferred
performance-monitoring-api.corp.mongodb.com/raw_perf_results/cedar_report
end point.Changes were tested in this patch and data was confirmed to be sending correctly.