use conductor to drive our nightly pipelines

[chouquette]

What does this PR do?

This PR introduces a configuration for conductor, in order to drive our nightly pipelines through that tool.

Motivation

We currently have 2 nightly pipelines that essentially do the same thing, One is ran from the k8s-datadog-agent-ops repo, the other one from datadog-agent.

The k8s deployment now need to run through conductor, which is why the duplicated job was introduced initially. If the datadog-agent nightly pipelines start though conductor, the k8s pipeline will no longer be needed.

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

[pr-commenter[bot]]

Bloop Bleep... Dogbot Here

Regression Detector Results

Run ID: 8cb16c7d-10f2-4a31-b40d-0f8a98f2aadb Baseline: 387b4f6702b060c272ce3d43f3561530444acc02 Comparison: cf729f5f98117f04a7ecf9069025251b272a005b

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

Experiments with missing or malformed data

• basic_py_check

Usually, this warning means that there is no usable optimization goal data for that experiment, which could be a result of misconfiguration.

No significant changes in experiment optimization goals

Confidence level: 90.00% Effect size tolerance: |Δ mean %| ≥ 5.00%

There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.

Experiments ignored for regressions

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

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	file_to_blackhole	% cpu utilization	+0.33	[-6.18, +6.85]

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	file_tree	memory utilization	+1.74	[+1.63, +1.86]
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	+0.66	[-0.81, +2.13]
➖	otel_to_otel_logs	ingress throughput	+0.35	[-0.29, +0.99]
➖	file_to_blackhole	% cpu utilization	+0.33	[-6.18, +6.85]
➖	idle	memory utilization	+0.23	[+0.20, +0.27]
➖	trace_agent_json	ingress throughput	+0.03	[-0.01, +0.07]
➖	uds_dogstatsd_to_api	ingress throughput	-0.00	[-0.00, +0.00]
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.00, +0.00]
➖	trace_agent_msgpack	ingress throughput	-0.01	[-0.01, -0.00]
➖	process_agent_standard_check	memory utilization	-0.42	[-0.46, -0.38]
➖	process_agent_standard_check_with_stats	memory utilization	-0.68	[-0.72, -0.64]
➖	process_agent_real_time_mode	memory utilization	-0.86	[-0.91, -0.81]
➖	tcp_syslog_to_blackhole	ingress throughput	-0.93	[-0.99, -0.88]

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:

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

[chouquette]

/merge

[dd-devflow[bot]]

:steam_locomotive: MergeQueue

Pull request added to the queue.

There are 2 builds ahead! (estimated merge in less than 44m)

Use /merge -c to cancel this operation!

[chouquette]

/merge -c

[dd-devflow[bot]]

:warning: MergeQueue

This merge request build was cancelled

If you need support, contact us on Slack #ci-interfaces!

[chouquette]

/merge

[dd-devflow[bot]]

:steam_locomotive: MergeQueue

This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals. Note: if you pushed new commits since the last approval, you may need additional approval. You can remove it from the waiting list with /remove command.

Use /merge -c to cancel this operation!

[dd-devflow[bot]]

:warning: MergeQueue

This merge request was unqueued

If you need support, contact us on Slack #ci-interfaces!

[chouquette]

/merge

[dd-devflow[bot]]

:steam_locomotive: MergeQueue

Pull request added to the queue.

This build is going to start soon! (estimated merge in less than 27m)

Use /merge -c to cancel this operation!