Propagate CI env to further docker runs#43662
Conversation
Gitlab CI Configuration Changes
|
| Removed | Modified | Added | Renamed |
|---|---|---|---|
| 0 | 1 | 0 | 0 |
Updated: .gitlab/trigger_distribution/include.yml
Modified Jobs
publish_winget_7_x64
publish_winget_7_x64:
before_script:
- $tmpfile = [System.IO.Path]::GetTempFileName()
- (& "$CI_PROJECT_DIR\tools\ci\fetch_secret.ps1" -parameterName "$Env:WINGET_PAT"
-tempFile "$tmpfile")
- If ($lastExitCode -ne "0") { exit "$lastExitCode" }
- $wingetPat=$(cat "$tmpfile")
- Remove-Item "$tmpfile"
dependencies: []
rules:
- if: $BUCKET_BRANCH != "beta" && $BUCKET_BRANCH != "stable"
when: never
- allow_failure: true
when: manual
script:
- $ErrorActionPreference = "Stop"
- - 'docker run --rm -v "$(Get-Location):c:\mnt" -e WINGET_GITHUB_ACCESS_TOKEN=${wingetPat}
+ - 'docker run --rm -v "$(Get-Location):c:\mnt" -e CI -e WINGET_GITHUB_ACCESS_TOKEN=${wingetPat}
? ++++++
-e GENERAL_ARTIFACTS_CACHE_BUCKET_URL ${WINBUILDIMAGE} Powershell -C "C:\mnt\tasks\winbuildscripts\Update-Winget.ps1"
'
- If ($lastExitCode -ne "0") { throw "Previous command returned $lastExitCode" }
stage: deploy_packages
tags:
- windows-v2:2022
variables:
ARCH: x64
OVERRIDE_GIT_STRATEGY: clone
WINBUILDIMAGE: registry.ddbuild.io/ci/datadog-agent-buildimages/windows_ltsc2022_${ARCH}${CI_IMAGE_WIN_LTSC2022_X64_SUFFIX}:${CI_IMAGE_WIN_LTSC2022_X64}Changes Summary
| Removed | Modified | Added | Renamed |
|---|---|---|---|
| 0 | 1 | 0 | 0 |
ℹ️ Diff available in the job log.
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: f3e5cec Optimization Goals: ✅ No significant changes detected
|
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | docker_containers_cpu | % cpu utilization | +2.05 | [-0.91, +5.00] | 1 | Logs |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | docker_containers_cpu | % cpu utilization | +2.05 | [-0.91, +5.00] | 1 | Logs |
| ➖ | quality_gate_metrics_logs | memory utilization | +0.82 | [+0.60, +1.03] | 1 | Logs bounds checks dashboard |
| ➖ | quality_gate_idle_all_features | memory utilization | +0.75 | [+0.69, +0.80] | 1 | Logs bounds checks dashboard |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | +0.63 | [+0.55, +0.71] | 1 | Logs |
| ➖ | otlp_ingest_logs | memory utilization | +0.42 | [+0.33, +0.51] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulativetodelta_exporter | memory utilization | +0.35 | [+0.11, +0.59] | 1 | Logs |
| ➖ | quality_gate_logs | % cpu utilization | +0.30 | [-1.15, +1.75] | 1 | Logs bounds checks dashboard |
| ➖ | ddot_metrics_sum_cumulative | memory utilization | +0.27 | [+0.10, +0.43] | 1 | Logs |
| ➖ | docker_containers_memory | memory utilization | +0.10 | [+0.01, +0.19] | 1 | Logs |
| ➖ | ddot_metrics_sum_delta | memory utilization | +0.05 | [-0.15, +0.25] | 1 | Logs |
| ➖ | quality_gate_idle | memory utilization | +0.03 | [-0.02, +0.08] | 1 | Logs bounds checks dashboard |
| ➖ | ddot_metrics | memory utilization | +0.01 | [-0.22, +0.25] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api | ingress throughput | +0.01 | [-0.11, +0.14] | 1 | Logs |
| ➖ | ddot_logs | memory utilization | +0.01 | [-0.06, +0.08] | 1 | Logs |
| ➖ | file_tree | memory utilization | -0.00 | [-0.05, +0.05] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api_v3 | ingress throughput | -0.00 | [-0.14, +0.13] | 1 | Logs |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.08, +0.07] | 1 | Logs |
| ➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.00 | [-0.41, +0.41] | 1 | Logs |
| ➖ | file_to_blackhole_100ms_latency | egress throughput | -0.01 | [-0.06, +0.04] | 1 | Logs |
| ➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | -0.07 | [-0.12, -0.01] | 1 | Logs |
| ➖ | file_to_blackhole_0ms_latency | egress throughput | -0.07 | [-0.49, +0.35] | 1 | Logs |
| ➖ | file_to_blackhole_500ms_latency | egress throughput | -0.08 | [-0.45, +0.30] | 1 | Logs |
| ➖ | otlp_ingest_metrics | memory utilization | -0.32 | [-0.47, -0.17] | 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_metrics_logs, 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 cpu_usage: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check lost_bytes: 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.
- quality_gate_idle, 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_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
c189024 to
2d40860
Compare
docker run commandsCI environment variable to more docker run commands
CI environment variable to more docker run commandsCI environment variable to more docker run commands
CI environment variable to more docker run commandsCI env to more docker run commands
CI env to more docker run commandsCI env to futher docker runs
CI env to futher docker runsCI env to further docker runs
This is a follow-up of #43274 aiming at ensure the `CI` environment variable is propagated to all docker containers started from CI jobs. The `CI` variable is a de facto standard set by most CI systems (GitHub Actions, GitLab CI, Travis CI, CircleCI, etc.) to indicate code is running in an automated build environment and used by tools like: - `cargo-nextest`: automatically hides progress bar when CI is detected - `pipenv`: uses non-interactive defaults - `pytest`: adjusts output Notes: - `-e CI` and `--env=CI` are all equivalent, - if `CI` is absent from the host environment, it's not added to the container.
…ever be run in CI
2d40860 to
66e0780
Compare
CI env to further docker runsCI env to further docker runs
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
What does this PR do?
This is a follow-up of #43274 aiming at ensuring the
CIenvironment variable is propagated to further docker containers started from CI jobs.Motivation
The
CIvariable is a de facto standard set by most CI systems (GitHub Actions, GitLab CI, Travis CI, CircleCI, etc.) to indicate code is running in an automated build environment and used by tools such as (but not limited to):cargo-nextest: automatically hides progress bar when CI is detected,pipenv: uses non-interactive defaults,pytest: adjusts output,Additional Notes
-e CI,--env CIand--env=CIare all equivalent,CIis absent from the host environment, it's not added to the container.