Separate release artifact publishing to depend on system test completion

[sarahchen6]

What Does This Do

Separate maven central and github artifact publishing, used during releases, into a separate publish-release-artifacts job. This way, we can configure them to depend on shared-pipeline system-tests to complete before any release artifact is published.

Motivation

In release 1.63.1 where GitLab system-tests failed, Maven and GitHub artifacts were deployed while OCI artifacts were not because only OCI artifacts depended on system-tests success. Ensure that publishing steps occur in line with each other after system-tests succeed.

Additional Notes

Check the effects of the changes in this PR by going to the GitLab pipeline, clicking "Job dependencies" and toggling "Show dependencies" (https://gitlab.ddbuild.io/DataDog/apm-reliability/dd-trace-java/-/pipelines/125758390).

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Once approved, use merge queue to merge the PR

Jira ticket: [PROJ-IDENT]

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	13.94 s	14.06 s	[-1.7%; +0.0%] (no difference)
startup:insecure-bank:tracing:Agent	13.03 s	13.10 s	[-1.2%; +0.0%] (no difference)
startup:petclinic:appsec:Agent	16.91 s	16.62 s	[+0.7%; +2.7%] (maybe worse)
startup:petclinic:iast:Agent	16.87 s	16.93 s	[-1.1%; +0.4%] (no difference)
startup:petclinic:profiling:Agent	16.78 s	16.38 s	[-2.0%; +6.8%] (no difference)
startup:petclinic:sca:Agent	16.91 s	16.80 s	[-0.4%; +1.7%] (no difference)
startup:petclinic:tracing:Agent	16.05 s	15.49 s	[-2.0%; +9.2%] (unstable)

Commit: cee96197 · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

[datadog-datadog-prod-us1]

More details

This PR correctly separates release artifact publishing into a dedicated pipeline stage that depends on system test completion. The implementation properly adds system_tests (optional) as a dependency to Maven Central deployment and positions the new publish-release-artifacts stage between shared-pipeline-test and shared-pipeline-publish. Jobs maintain correct ordering within the stage via explicit needs: declarations. Maven/GitHub artifacts will now be blocked if system tests fail, achieving the stated goal from release 1.63.1 where system test failures didn't prevent these deployments.

Was this helpful? React 👍 or 👎

_{📊 Validated against 5 scenarios · Open Bits AI session}

_{🤖 Datadog Autotest · Commit 2316221 · What is Autotest? · Any feedback? Reach out in #autotest}