Skip to content

[Backport 7.75.x] Push to bazel* caches from the main branch only#46325

Merged
gh-worker-dd-mergequeue-cf854d[bot] merged 1 commit into7.75.xfrom
backport-46151-to-7.75.x
Feb 12, 2026
Merged

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

Conversation

@dd-octo-sts
Copy link
Copy Markdown
Contributor

@dd-octo-sts dd-octo-sts bot commented Feb 12, 2026

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

  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.

@dd-octo-sts @rdesgroppes
Push to bazel* caches from the main branch only (#46151) ### What…
baa055d 
… 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>
@dd-octo-sts dd-octo-sts bot requested a review from a team as a code owner February 12, 2026 11:14
@dd-octo-sts dd-octo-sts bot requested a review from a team as a code owner February 12, 2026 11:14
@dd-octo-sts dd-octo-sts bot added changelog/no-changelog No changelog entry needed internal Identify a non-fork PR 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 12, 2026
@agent-platform-auto-pr
Copy link
Copy Markdown
Contributor

agent-platform-auto-pr bot commented Feb 12, 2026 •
edited
Loading

Gitlab CI Configuration Changes

⚠️ Diff too large to display on Github.

Changes Summary

Removed Modified Added Renamed
0 118 0 0

ℹ️ Diff available in the job log.

@FlorentClarret
Copy link
Copy Markdown
Member

FlorentClarret commented Feb 12, 2026

/merge

@gh-worker-devflow-routing-ef8351
Copy link
Copy Markdown

gh-worker-devflow-routing-ef8351 bot commented Feb 12, 2026 •
edited
Loading

View all feedbacks in Devflow UI.

2026-02-12 11:45:14 UTC ℹ️ Start processing command /merge

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

The expected merge time in 7.75.x is approximately 45m (p90).

2026-02-12 12:41:16 UTC ℹ️ MergeQueue: This merge request was merged

@agent-platform-auto-pr
Copy link
Copy Markdown
Contributor

agent-platform-auto-pr bot commented Feb 12, 2026 •
edited
Loading

Static quality checks

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

Successful checks

Info

Quality gate Delta On disk size (MiB) Delta On wire size (MiB)
✅ agent_deb_amd64 DataNotFound $${707.45}$$ < $${708.6}$$ DataNotFound $${173.76}$$ < $${174.5}$$
✅ agent_deb_amd64_fips DataNotFound $${702.73}$$ < $${703.97}$$ DataNotFound $${172.68}$$ < $${173.77}$$
✅ agent_heroku_amd64 DataNotFound $${327.91}$$ < $${329.53}$$ DataNotFound $${87.33}$$ < $${88.43}$$
✅ agent_msi DataNotFound $${570.31}$$ < $${982.08}$$ DataNotFound $${142.73}$$ < $${143.02}$$
✅ agent_rpm_amd64 DataNotFound $${707.43}$$ < $${708.85}$$ DataNotFound $${176.3}$$ < $${177.66}$$
✅ agent_rpm_amd64_fips DataNotFound $${702.71}$$ < $${703.96}$$ DataNotFound $${175.93}$$ < $${176.63}$$
✅ agent_rpm_arm64 DataNotFound $${689.0}$$ < $${693.49}$$ DataNotFound $${159.89}$$ < $${161.21}$$
✅ agent_rpm_arm64_fips DataNotFound $${685.15}$$ < $${688.44}$$ DataNotFound $${159.29}$$ < $${160.46}$$
✅ agent_suse_amd64 DataNotFound $${707.43}$$ < $${708.85}$$ DataNotFound $${176.3}$$ < $${177.66}$$
✅ agent_suse_amd64_fips DataNotFound $${702.71}$$ < $${703.96}$$ DataNotFound $${175.93}$$ < $${176.63}$$
✅ agent_suse_arm64 DataNotFound $${689.0}$$ < $${693.49}$$ DataNotFound $${159.89}$$ < $${161.21}$$
✅ agent_suse_arm64_fips DataNotFound $${685.15}$$ < $${688.44}$$ DataNotFound $${159.29}$$ < $${160.46}$$
✅ docker_agent_amd64 DataNotFound $${769.23}$$ < $${770.69}$$ DataNotFound $${261.63}$$ < $${262.46}$$
✅ docker_agent_arm64 DataNotFound $${775.37}$$ < $${780.17}$$ DataNotFound $${250.7}$$ < $${252.63}$$
✅ docker_agent_jmx_amd64 DataNotFound $${960.14}$$ < $${961.57}$$ DataNotFound $${330.28}$$ < $${331.09}$$
✅ docker_agent_jmx_arm64 DataNotFound $${955.06}$$ < $${959.77}$$ DataNotFound $${315.32}$$ < $${317.26}$$
✅ docker_cluster_agent_amd64 DataNotFound $${180.8}$$ < $${181.2}$$ DataNotFound $${63.86}$$ < $${64.51}$$
✅ docker_cluster_agent_arm64 DataNotFound $${196.62}$$ < $${198.49}$$ DataNotFound $${60.14}$$ < $${61.17}$$
✅ docker_cws_instrumentation_amd64 DataNotFound $${7.13}$$ < $${7.18}$$ DataNotFound $${2.99}$$ < $${3.33}$$
✅ docker_cws_instrumentation_arm64 DataNotFound $${6.69}$$ < $${6.92}$$ DataNotFound $${2.73}$$ < $${3.09}$$
✅ docker_dogstatsd_amd64 DataNotFound $${38.81}$$ < $${39.38}$$ DataNotFound $${15.02}$$ < $${15.82}$$
✅ docker_dogstatsd_arm64 DataNotFound $${37.13}$$ < $${37.94}$$ DataNotFound $${14.34}$$ < $${14.83}$$
✅ dogstatsd_deb_amd64 DataNotFound $${30.02}$$ < $${30.61}$$ DataNotFound $${7.94}$$ < $${8.79}$$
✅ dogstatsd_deb_arm64 DataNotFound $${28.18}$$ < $${29.11}$$ DataNotFound $${6.82}$$ < $${7.71}$$
✅ dogstatsd_rpm_amd64 DataNotFound $${30.02}$$ < $${30.61}$$ DataNotFound $${7.95}$$ < $${8.8}$$
✅ dogstatsd_suse_amd64 DataNotFound $${30.02}$$ < $${30.61}$$ DataNotFound $${7.95}$$ < $${8.8}$$
✅ iot_agent_deb_amd64 DataNotFound $${42.97}$$ < $${43.29}$$ DataNotFound $${11.25}$$ < $${12.04}$$
✅ iot_agent_deb_arm64 DataNotFound $${40.1}$$ < $${40.92}$$ DataNotFound $${9.62}$$ < $${10.45}$$
✅ iot_agent_deb_armhf DataNotFound $${40.68}$$ < $${41.03}$$ DataNotFound $${9.82}$$ < $${10.62}$$
✅ iot_agent_rpm_amd64 DataNotFound $${42.97}$$ < $${43.29}$$ DataNotFound $${11.26}$$ < $${12.06}$$
✅ iot_agent_suse_amd64 DataNotFound $${42.97}$$ < $${43.29}$$ DataNotFound $${11.26}$$ < $${12.06}$$

@cit-pr-commenter-54b7da
Copy link
Copy Markdown

cit-pr-commenter-54b7da bot commented Feb 12, 2026 •
edited
Loading

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 5c8ec8cf-9dc6-4761-914e-6f7b5d4997e6

Baseline: 44f039c
Comparison: baa055d
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 +0.73 [-2.26, +3.72] 1 Logs

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI trials links
➖ quality_gate_logs % cpu utilization +3.16 [+1.65, +4.66] 1 Logs bounds checks dashboard
➖ ddot_metrics memory utilization +0.76 [+0.52, +0.99] 1 Logs
➖ docker_containers_cpu % cpu utilization +0.73 [-2.26, +3.72] 1 Logs
➖ uds_dogstatsd_20mb_12k_contexts_20_senders memory utilization +0.28 [+0.23, +0.34] 1 Logs
➖ docker_containers_memory memory utilization +0.12 [+0.04, +0.19] 1 Logs
➖ file_to_blackhole_500ms_latency egress throughput +0.04 [-0.33, +0.41] 1 Logs
➖ file_to_blackhole_1000ms_latency egress throughput +0.03 [-0.38, +0.43] 1 Logs
➖ uds_dogstatsd_to_api_v3 ingress throughput +0.01 [-0.12, +0.15] 1 Logs
➖ tcp_dd_logs_filter_exclude ingress throughput +0.00 [-0.07, +0.07] 1 Logs
➖ uds_dogstatsd_to_api ingress throughput -0.00 [-0.14, +0.14] 1 Logs
➖ file_to_blackhole_0ms_latency egress throughput -0.02 [-0.40, +0.36] 1 Logs
➖ quality_gate_idle memory utilization -0.05 [-0.10, -0.01] 1 Logs bounds checks dashboard
➖ file_tree memory utilization -0.06 [-0.11, -0.00] 1 Logs
➖ file_to_blackhole_100ms_latency egress throughput -0.06 [-0.11, -0.02] 1 Logs
➖ ddot_metrics_sum_delta memory utilization -0.08 [-0.29, +0.13] 1 Logs
➖ quality_gate_idle_all_features memory utilization -0.11 [-0.15, -0.07] 1 Logs bounds checks dashboard
➖ otlp_ingest_logs memory utilization -0.13 [-0.22, -0.03] 1 Logs
➖ ddot_metrics_sum_cumulativetodelta_exporter memory utilization -0.23 [-0.46, -0.00] 1 Logs
➖ ddot_metrics_sum_cumulative memory utilization -0.42 [-0.58, -0.25] 1 Logs
➖ otlp_ingest_metrics memory utilization -0.50 [-0.65, -0.35] 1 Logs
➖ ddot_logs memory utilization -0.60 [-0.67, -0.53] 1 Logs
➖ tcp_syslog_to_blackhole ingress throughput -0.65 [-0.76, -0.54] 1 Logs
➖ quality_gate_metrics_logs memory utilization -1.44 [-1.64, -1.24] 1 Logs bounds checks dashboard

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:

  1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

  2. 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.

  3. 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 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_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_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 intake_connections: 10/10 replicas passed. Gate passed.

@gh-worker-dd-mergequeue-cf854d gh-worker-dd-mergequeue-cf854d bot merged commit bf08c6d into 7.75.x Feb 12, 2026
439 of 441 checks passed
@gh-worker-dd-mergequeue-cf854d gh-worker-dd-mergequeue-cf854d bot deleted the backport-46151-to-7.75.x branch February 12, 2026 12:41
@FlorentClarret FlorentClarret mentioned this pull request Feb 16, 2026
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@FlorentClarret FlorentClarret FlorentClarret approved these changes

Assignees

No one assigned

Labels

backport bot changelog/no-changelog No changelog entry needed internal Identify a non-fork PR 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

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@FlorentClarret