-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Add gitlab ci diff cli / pr comment #27153
base: main
Are you sure you want to change the base?
Conversation
[Fast Unit Tests Report] On pipeline 38129343 (CI Visibility). The following jobs did not run any unit tests: Jobs:
If you modified Go files and expected unit tests to run in these jobs, please double check the job logs. If you think tests should have been executed reach out to #agent-devx-help |
Regression DetectorRegression Detector ResultsRun ID: 02600f9b-ae99-4ecc-8e2f-d2bf0b202e7e Metrics dashboard Target profiles Baseline: 671f875 Performance changes are noted in the perf column of each table:
No significant changes in experiment optimization goalsConfidence level: 90.00% There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.
|
perf | experiment | goal | Δ mean % | Δ mean % CI | links |
---|---|---|---|---|---|
➖ | pycheck_1000_100byte_tags | % cpu utilization | +1.75 | [-3.20, +6.70] | Logs |
➖ | basic_py_check | % cpu utilization | +1.30 | [-1.45, +4.05] | Logs |
➖ | idle | memory utilization | +0.70 | [+0.67, +0.74] | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | +0.57 | [-12.04, +13.18] | Logs |
➖ | file_tree | memory utilization | +0.30 | [+0.26, +0.34] | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.01, +0.01] | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.00 | [-0.00, +0.00] | Logs |
➖ | otel_to_otel_logs | ingress throughput | -0.13 | [-0.94, +0.68] | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -1.04 | [-1.92, -0.15] | Logs |
Explanation
A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".
For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.
-
Its configuration does not mark it "erratic".
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.
Great work 🎉. Some general comments after testing for a bit:
- We should show the contents of added jobs - we want to be able to quickly read what a new job does in PR review,
- I'd make the naming of the parameters of
inv -e notify.gitlab-ci-diff
more consistent, eg. "before" vs. "after", For local use, I'd like to be able to say "use my local (uncommitted) config" as one of the comparison points - right now, you need to commit changes to be able to evaluate them,already done- If the linting API fails (because the Gitlab config is invalid), the task should not immediately crash, and instead show that error in the PR comment.
Example Gitlab CI Configuration ChangesModified Jobs
|
Removed | Modified | Added | Renamed |
---|---|---|---|
0 | 1 | 1 | 1 |
Gitlab CI Configuration ChangesAdded Jobs
|
Removed | Modified | Added | Renamed |
---|---|---|---|
0 | 0 | 1 | 0 |
👏 praise: Wtf this is so clean omg thank you for this !!!! |
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.
LGTM !
export GITHUB_APP_ID=$($CI_PROJECT_DIR/tools/ci/aws_ssm_get_wrapper.sh $GITHUB_PR_COMMENTER_INTEGRATION_ID_SSM_NAME) | ||
export GITHUB_INSTALLATION_ID=$($CI_PROJECT_DIR/tools/ci/aws_ssm_get_wrapper.sh $GITHUB_PR_COMMENTER_INSTALLATION_ID_SSM_NAME) | ||
export GITLAB_TOKEN=$($CI_PROJECT_DIR/tools/ci/aws_ssm_get_wrapper.sh $GITLAB_FULL_API_TOKEN_SSM_NAME) | ||
- inv -e notify.gitlab-ci-diff --pr-comment |
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 there be a problem if CI config changes have been made on main
that aren't present on the branch? Would the diff also show these changes?
""" | ||
|
||
pr_comment_head = 'Gitlab CI Configuration Changes' | ||
job_url = os.environ['CI_JOB_URL'] |
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.
This makes the task hard to use locally, you have to set the CI_JOB_URL
locally, even though it's only used in the case where a PR comment is made.
What does this PR do?
This adds a task that prints gitlab ci modifications as shown below.
It also comments on PRs.
Motivation
Additional Notes
This adds:
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes