[Backport 7.76.x] Push to `bazel*` caches from the `main` branch only by dd-octo-sts[bot] · Pull Request #46179 · DataDog/datadog-agent

dd-octo-sts · 2026-02-10T11:04:20Z

Backport 0463d57 from #46151.

What does this PR do?

Configure GitLab bazel* caches on ephemeral runners to use a pull-only policy by default, and pull-push only when running on the main branch.

This restriction applies only to GitLab caches - at this stage, the bazel remote cache remains indeed shared across all branches.

Motivation

avoid cache pollution from feature and release branches while allowing main to populate the cache in a progressive manner,
because the GitLab cache is uploaded to a shared S3 bucket, restricting uploads to main reduces S3 write contention and costs incurred by parallel cache overwrites.

Because the GitLab cache is shared across pipelines, allowing feature or release branches to push artifacts pollutes the cache with experimental entries from feature branches and meanwhile-evicted entries from oldest release branches.

Additional Notes

Release branches and feature branches behind main may fetch older dependencies, whereas feature branches ahead of main may fetch newer dependencies, but:

they'll still benefit from the bazel remote cache,
they'll no longer incur the overhead of uploading GitLab caches.

… does this PR do? Configure GitLab `bazel*` caches on ephemeral runners to use a `pull`-only policy by default, and `pull-push` only when running on the `main` branch. This restriction applies only to **GitLab** caches - at this stage, the `bazel` **remote** cache remains indeed shared across all branches. ### Motivation 1. avoid cache pollution from feature and release branches while allowing `main` to populate the cache in a _progressive_ manner, 2. because the GitLab cache is uploaded to a shared S3 bucket, restricting uploads to `main` reduces S3 write contention and costs incurred by parallel cache overwrites. Because the GitLab cache is shared across pipelines, allowing feature or release branches to push artifacts pollutes the cache with _experimental_ entries from feature branches and _meanwhile-evicted_ entries from oldest release branches. ### Additional Notes Release branches and feature branches _behind_ `main` may fetch _older_ dependencies, whereas feature branches _ahead_ of `main` may fetch _newer_ dependencies, but: - they'll still benefit from the `bazel` remote cache, - they'll no longer incur the overhead of uploading GitLab caches. Co-authored-by: regis.desgroppes <regis.desgroppes@datadoghq.com> (cherry picked from commit 0463d57) ___ Co-authored-by: Régis Desgroppes <rdesgroppes@gmail.com>

agent-platform-auto-pr · 2026-02-10T11:10:24Z

Gitlab CI Configuration Changes

⚠️ Diff too large to display on Github.

Changes Summary

Removed	Modified	Added	Renamed
1	128	0	0

ℹ️ Diff available in the job log.

agent-platform-auto-pr · 2026-02-10T11:43:01Z

Static quality checks

✅ Please find below the results from static quality gates
Comparison made with ancestor 188e66f
📊 Static Quality Gates Dashboard

31 successful checks with minimal change (< 2 KiB)

	Quality gate	Current Size
✅	agent_deb_amd64	752.558 MiB
✅	agent_deb_amd64_fips	712.540 MiB
✅	agent_heroku_amd64	326.020 MiB
✅	agent_msi	662.356 MiB
✅	agent_rpm_amd64	752.541 MiB
✅	agent_rpm_amd64_fips	712.524 MiB
✅	agent_rpm_arm64	731.344 MiB
✅	agent_rpm_arm64_fips	693.788 MiB
✅	agent_suse_amd64	752.541 MiB
✅	agent_suse_amd64_fips	712.524 MiB
✅	agent_suse_arm64	731.344 MiB
✅	agent_suse_arm64_fips	693.788 MiB
✅	docker_agent_amd64	814.677 MiB
✅	docker_agent_arm64	818.067 MiB
✅	docker_agent_jmx_amd64	1005.588 MiB
✅	docker_agent_jmx_arm64	997.760 MiB
✅	docker_cluster_agent_amd64	181.187 MiB
✅	docker_cluster_agent_arm64	196.997 MiB
✅	docker_cws_instrumentation_amd64	7.135 MiB
✅	docker_cws_instrumentation_arm64	6.689 MiB
✅	docker_dogstatsd_amd64	38.859 MiB
✅	docker_dogstatsd_arm64	37.191 MiB
✅	dogstatsd_deb_amd64	30.074 MiB
✅	dogstatsd_deb_arm64	28.219 MiB
✅	dogstatsd_rpm_amd64	30.074 MiB
✅	dogstatsd_suse_amd64	30.074 MiB
✅	iot_agent_deb_amd64	43.041 MiB
✅	iot_agent_deb_arm64	40.143 MiB
✅	iot_agent_deb_armhf	40.713 MiB
✅	iot_agent_rpm_amd64	43.042 MiB
✅	iot_agent_suse_amd64	43.042 MiB

On-wire sizes (compressed)

	Quality gate	Change	Size (prev → curr → max)
✅	agent_deb_amd64	-23.66 KiB (0.01% reduction)	183.910 → 183.886 → 184.810
✅	agent_deb_amd64_fips	+18.5 KiB (0.01% increase)	176.307 → 176.325 → 177.560
✅	agent_heroku_amd64	-12.47 KiB (0.01% reduction)	87.127 → 87.115 → 88.450
✅	agent_msi	-20.0 KiB (0.01% reduction)	143.148 → 143.129 → 143.300
✅	agent_rpm_amd64	-37.38 KiB (0.02% reduction)	186.806 → 186.770 → 188.160
✅	agent_rpm_amd64_fips	+34.29 KiB (0.02% increase)	177.936 → 177.970 → 178.900
✅	agent_rpm_arm64	-33.34 KiB (0.02% reduction)	168.564 → 168.531 → 169.930
✅	agent_rpm_arm64_fips	-20.45 KiB (0.01% reduction)	161.632 → 161.612 → 163.120
✅	agent_suse_amd64	-37.38 KiB (0.02% reduction)	186.806 → 186.770 → 188.160
✅	agent_suse_amd64_fips	+34.29 KiB (0.02% increase)	177.936 → 177.970 → 178.900
✅	agent_suse_arm64	-33.34 KiB (0.02% reduction)	168.564 → 168.531 → 169.930
✅	agent_suse_arm64_fips	-20.45 KiB (0.01% reduction)	161.632 → 161.612 → 163.120
✅	docker_agent_amd64	neutral	276.539 MiB → 277.400
✅	docker_agent_arm64	neutral	263.988 MiB → 266.040
✅	docker_agent_jmx_amd64	-3.32 KiB (0.00% reduction)	345.198 → 345.194 → 346.020
✅	docker_agent_jmx_arm64	-2.88 KiB (0.00% reduction)	328.625 → 328.622 → 330.660
✅	docker_cluster_agent_amd64	neutral	63.995 MiB → 64.510
✅	docker_cluster_agent_arm64	neutral	60.277 MiB → 61.170
✅	docker_cws_instrumentation_amd64	neutral	2.994 MiB → 3.330
✅	docker_cws_instrumentation_arm64	neutral	2.726 MiB → 3.090
✅	docker_dogstatsd_amd64	neutral	15.037 MiB → 15.820
✅	docker_dogstatsd_arm64	neutral	14.366 MiB → 14.830
✅	dogstatsd_deb_amd64	neutral	7.949 MiB → 8.790
✅	dogstatsd_deb_arm64	neutral	6.829 MiB → 7.710
✅	dogstatsd_rpm_amd64	neutral	7.962 MiB → 8.800
✅	dogstatsd_suse_amd64	neutral	7.962 MiB → 8.800
✅	iot_agent_deb_amd64	neutral	11.292 MiB → 12.040
✅	iot_agent_deb_arm64	neutral	9.652 MiB → 10.450
✅	iot_agent_deb_armhf	+2.93 KiB (0.03% increase)	9.848 → 9.851 → 10.620
✅	iot_agent_rpm_amd64	neutral	11.310 MiB → 12.060
✅	iot_agent_suse_amd64	neutral	11.310 MiB → 12.060

cit-pr-commenter-54b7da · 2026-02-10T11:55:40Z

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 75babe40-9707-4ee1-9dec-a7c1f5f6d3cb

Baseline: 188e66f
Comparison: 3570a08
Diff

Optimization Goals: ✅ No significant changes detected

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	docker_containers_cpu	% cpu utilization	+1.06	[-2.02, +4.15]	1	Logs

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	quality_gate_metrics_logs	memory utilization	+1.50	[+1.28, +1.73]	1	Logs bounds checks dashboard
➖	docker_containers_cpu	% cpu utilization	+1.06	[-2.02, +4.15]	1	Logs
➖	docker_containers_memory	memory utilization	+0.65	[+0.58, +0.72]	1	Logs
➖	ddot_metrics_sum_cumulative	memory utilization	+0.39	[+0.23, +0.56]	1	Logs
➖	ddot_metrics_sum_delta	memory utilization	+0.35	[+0.13, +0.56]	1	Logs
➖	file_tree	memory utilization	+0.34	[+0.29, +0.39]	1	Logs
➖	uds_dogstatsd_20mb_12k_contexts_20_senders	memory utilization	+0.32	[+0.27, +0.37]	1	Logs
➖	ddot_logs	memory utilization	+0.22	[+0.16, +0.29]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	+0.18	[+0.14, +0.22]	1	Logs bounds checks dashboard
➖	otlp_ingest_logs	memory utilization	+0.14	[+0.05, +0.23]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	+0.09	[-0.30, +0.47]	1	Logs
➖	ddot_metrics	memory utilization	+0.05	[-0.18, +0.29]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	+0.01	[-0.03, +0.05]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	+0.01	[-0.42, +0.44]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.01	[-0.09, +0.11]	1	Logs
➖	ddot_metrics_sum_cumulativetodelta_exporter	memory utilization	-0.01	[-0.24, +0.22]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	-0.01	[-0.12, +0.09]	1	Logs
➖	uds_dogstatsd_to_api_v3	ingress throughput	-0.02	[-0.14, +0.11]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	-0.02	[-0.47, +0.44]	1	Logs
➖	quality_gate_idle	memory utilization	-0.21	[-0.25, -0.17]	1	Logs bounds checks dashboard
➖	otlp_ingest_metrics	memory utilization	-0.55	[-0.70, -0.39]	1	Logs
➖	quality_gate_logs	% cpu utilization	-0.70	[-2.18, +0.79]	1	Logs bounds checks dashboard
➖	tcp_syslog_to_blackhole	ingress throughput	-3.09	[-3.19, -2.99]	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 memory_usage: 10/10 replicas passed. Gate passed.
quality_gate_idle_all_features, bounds check intake_connections: 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_metrics_logs, bounds check memory_usage: 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_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.

avonengel · 2026-02-11T12:49:55Z

/merge

gh-worker-devflow-routing-ef8351 · 2026-02-11T12:49:59Z

View all feedbacks in Devflow UI.

2026-02-11 12:49:58 UTC ℹ️ Start processing command /merge

2026-02-11 12:50:04 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in 7.76.x is approximately 48m (p90).

2026-02-11 13:27:29 UTC ℹ️ MergeQueue: This merge request was merged

dd-octo-sts bot added backport bot changelog/no-changelog No changelog entry needed labels Feb 10, 2026

dd-octo-sts bot requested a review from a team as a code owner February 10, 2026 11:04

dd-octo-sts bot added the internal Identify a non-fork PR label Feb 10, 2026

dd-octo-sts bot requested a review from a team as a code owner February 10, 2026 11:04

dd-octo-sts bot added qa/no-code-change No code change in Agent code requiring validation short review PR is simple enough to be reviewed quickly team/agent-build team/agent-devx labels Feb 10, 2026

avonengel approved these changes Feb 11, 2026

View reviewed changes

gh-worker-dd-mergequeue-cf854d bot merged commit d128b33 into 7.76.x Feb 11, 2026
447 checks passed

gh-worker-dd-mergequeue-cf854d bot deleted the backport-46151-to-7.76.x branch February 11, 2026 13:27

github-actions bot added this to the 7.76.0 milestone Feb 11, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Backport 7.76.x] Push to `bazel*` caches from the `main` branch only#46179

[Backport 7.76.x] Push to `bazel*` caches from the `main` branch only#46179
gh-worker-dd-mergequeue-cf854d[bot] merged 1 commit into7.76.xfrom
backport-46151-to-7.76.x

dd-octo-sts bot commented Feb 10, 2026

Uh oh!

agent-platform-auto-pr bot commented Feb 10, 2026 •

edited

Loading

Uh oh!

agent-platform-auto-pr bot commented Feb 10, 2026 •

edited

Loading

Uh oh!

cit-pr-commenter-54b7da bot commented Feb 10, 2026 •

edited

Loading

Experiments ignored for regressions

Fine details of change detection per experiment

Bounds Checks: ✅ Passed

Explanation

Uh oh!

avonengel commented Feb 11, 2026

Uh oh!

gh-worker-devflow-routing-ef8351 bot commented Feb 11, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

dd-octo-sts bot commented Feb 10, 2026

What does this PR do?

Motivation

Additional Notes

Uh oh!

agent-platform-auto-pr bot commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Gitlab CI Configuration Changes

Changes Summary

Uh oh!

agent-platform-auto-pr bot commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Static quality checks

Uh oh!

cit-pr-commenter-54b7da bot commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Regression Detector

Regression Detector Results

Optimization Goals: ✅ No significant changes detected

Experiments ignored for regressions

Fine details of change detection per experiment

Bounds Checks: ✅ Passed

Explanation

CI Pass/Fail Decision

Uh oh!

avonengel commented Feb 11, 2026

Uh oh!

gh-worker-devflow-routing-ef8351 bot commented Feb 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

agent-platform-auto-pr bot commented Feb 10, 2026 •

edited

Loading

agent-platform-auto-pr bot commented Feb 10, 2026 •

edited

Loading

cit-pr-commenter-54b7da bot commented Feb 10, 2026 •

edited

Loading

gh-worker-devflow-routing-ef8351 bot commented Feb 11, 2026 •

edited

Loading