[ABLD-300] Also pass CI to docker build for bazel (and others)#43672
Conversation
Gitlab CI Configuration ChangesChanges Summary
ℹ️ Diff available in the job log. |
CI to docker build for bazel CI configCI to docker build for bazel (and others)
d6ec9e1 to
76f58d3
Compare
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 2869418 Optimization Goals: ✅ No significant changes detected
|
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | docker_containers_cpu | % cpu utilization | -2.04 | [-4.96, +0.87] | 1 | Logs |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | tcp_syslog_to_blackhole | ingress throughput | +2.42 | [+2.36, +2.48] | 1 | Logs |
| ➖ | quality_gate_metrics_logs | memory utilization | +1.65 | [+1.43, +1.86] | 1 | Logs bounds checks dashboard |
| ➖ | otlp_ingest_metrics | memory utilization | +0.63 | [+0.49, +0.78] | 1 | Logs |
| ➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | +0.35 | [+0.30, +0.41] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulativetodelta_exporter | memory utilization | +0.33 | [+0.09, +0.57] | 1 | Logs |
| ➖ | file_tree | memory utilization | +0.30 | [+0.25, +0.35] | 1 | Logs |
| ➖ | file_to_blackhole_500ms_latency | egress throughput | +0.08 | [-0.29, +0.45] | 1 | Logs |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.01 | [-0.07, +0.08] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api | ingress throughput | -0.00 | [-0.13, +0.12] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api_v3 | ingress throughput | -0.01 | [-0.14, +0.13] | 1 | Logs |
| ➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.03 | [-0.43, +0.38] | 1 | Logs |
| ➖ | file_to_blackhole_100ms_latency | egress throughput | -0.03 | [-0.07, +0.02] | 1 | Logs |
| ➖ | file_to_blackhole_0ms_latency | egress throughput | -0.07 | [-0.46, +0.33] | 1 | Logs |
| ➖ | docker_containers_memory | memory utilization | -0.12 | [-0.20, -0.03] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulative | memory utilization | -0.15 | [-0.30, -0.01] | 1 | Logs |
| ➖ | otlp_ingest_logs | memory utilization | -0.20 | [-0.30, -0.11] | 1 | Logs |
| ➖ | quality_gate_idle | memory utilization | -0.24 | [-0.29, -0.19] | 1 | Logs bounds checks dashboard |
| ➖ | quality_gate_idle_all_features | memory utilization | -0.38 | [-0.43, -0.32] | 1 | Logs bounds checks dashboard |
| ➖ | ddot_logs | memory utilization | -0.42 | [-0.47, -0.36] | 1 | Logs |
| ➖ | ddot_metrics | memory utilization | -0.63 | [-0.83, -0.43] | 1 | Logs |
| ➖ | ddot_metrics_sum_delta | memory utilization | -0.72 | [-0.93, -0.51] | 1 | Logs |
| ➖ | quality_gate_logs | % cpu utilization | -1.33 | [-2.76, +0.10] | 1 | Logs bounds checks dashboard |
| ➖ | docker_containers_cpu | % cpu utilization | -2.04 | [-4.96, +0.87] | 1 | Logs |
Bounds Checks: ✅ Passed
| perf | experiment | bounds_check_name | replicates_passed | links |
|---|---|---|---|---|
| ✅ | docker_containers_cpu | simple_check_run | 10/10 | |
| ✅ | docker_containers_memory | memory_usage | 10/10 | |
| ✅ | docker_containers_memory | simple_check_run | 10/10 | |
| ✅ | file_to_blackhole_0ms_latency | lost_bytes | 10/10 | |
| ✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 | |
| ✅ | file_to_blackhole_1000ms_latency | lost_bytes | 10/10 | |
| ✅ | file_to_blackhole_1000ms_latency | memory_usage | 10/10 | |
| ✅ | file_to_blackhole_100ms_latency | lost_bytes | 10/10 | |
| ✅ | file_to_blackhole_100ms_latency | memory_usage | 10/10 | |
| ✅ | file_to_blackhole_500ms_latency | lost_bytes | 10/10 | |
| ✅ | file_to_blackhole_500ms_latency | memory_usage | 10/10 | |
| ✅ | quality_gate_idle | intake_connections | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_idle | memory_usage | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_idle_all_features | intake_connections | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_idle_all_features | memory_usage | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_logs | intake_connections | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_logs | lost_bytes | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_logs | memory_usage | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | cpu_usage | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | intake_connections | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | lost_bytes | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | memory_usage | 10/10 | bounds checks dashboard |
Explanation
Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%
Performance changes are noted in the perf column of each table:
- ✅ = significantly better comparison variant performance
- ❌ = significantly worse comparison variant performance
- ➖ = no significant change in performance
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".
CI Pass/Fail Decision
✅ Passed. All Quality Gates passed.
- quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
Extend `CI` environment variable propagation to `docker build` contexts, enabling nested `bazel` invocations to automatically benefit from `bazel --config=ci` settings (as configured in `.bazelrc`) and applicable caching. Following the same approach as commit PR #43274 which generalized `bazel` CI configuration for `docker run` commands, this ensures `docker build` operations also detect the CI environment. The `CI` variable is a _de facto_ standard (GitLab CI, GitHub Actions, Travis, CircleCI) already leveraged by existing tools including `pip`, `dda`, etc.. Using the standard `CI` variable rather than a custom name avoids propagation issues from omitted remapping - tools and scripts that check for CI presence work automatically without requiring explicit variable renaming (e.g., `CIBUILD=$CI`) at each layer or invocation. This therefore replaces the custom `CIBUILD` variable with the standard `CI` variable in Dockerfiles, ensuring uniform treatment across all `docker` operations (both `build` and `run` contexts).
76f58d3 to
97eea4f
Compare
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
CI to docker build for bazel (and others)CI to docker build for bazel (and others)
What does this PR do?
Following the same approach as PR #43274 which generalized
bazelCI configuration fordocker runcommands, this extends theCIenvironment variable propagation todocker buildcontexts, enabling nestedbazelinvocations to automatically benefit frombazel --config=cisettings (as configured in.bazelrc) and cache detection when applicable.Motivation
The
CIvariable is a de facto standard (GitLab CI, GitHub Actions, Travis, CircleCI) already leveraged by other tools includingpip,dda, etc.Using it rather than the custom
CIBUILDavoids propagation issues from omitted remapping - tools and scripts that check for CI presence work automatically without requiring explicit variable renaming (e.g.,CIBUILD=$CI) at each layer or invocation.Additional Notes
With
--build-arg CI/--build-arg=CIwithout a value,docker buildautomatically propagates its value verbatim) from the host environment (if defined) into the container (doc, similar to-e/--envfordocker run).