Repository navigation
fix(ci): pair the development Java agent with its OpenFeature provider - #8188
Merged
Merged
Conversation
Use the provider artifact from the selected Java development branch so FFE tests do not mix a development agent with a released provider. Environment: Datadog workspace Co-Authored-By: Codex GPT-6 <noreply@localhost>
Contributor
|
|
vjfridge
marked this pull request as ready for review
October 26, 2026 22:19
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Contributor
❌ ErrorsYour PR has failed checks. Please review the issues below and take necessary action before merging. 🚦 1 Pipeline job failed
ℹ️ InfoNo other issues found (see more)🧪 All tests passed Useful? React with 👍 / 👎 This comment will be updated automatically if new data arrives.🔗 Commit SHA: 8e24327 | Docs | View more details | Give us feedback! |
cbeauchesne
approved these changes
Oct 27, 2026
This was referenced Oct 27, 2026
vjfridge
added a commit
that referenced
this pull request
Oct 27, 2026
Include the matching Java development provider download from #8188 and current main updates. Environment: Datadog workspace Co-Authored-By: Codex GPT-6 <noreply@localhost>
vjfridge
added a commit
that referenced
this pull request
Oct 27, 2026
Include the matching Java development provider download from #8188 and current main updates. Environment: Datadog workspace Co-Authored-By: Codex GPT-6 <noreply@localhost>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Our Java Feature Flags documentation advises customers: “Use the same version of
dd-java-agentanddd-openfeature.” Java development CI currently does something different: it downloads the development Java agent but builds the test application with the latest released OpenFeature provider from Maven Central.dd-trace-java #12976 is a concrete example of why that mismatch matters. Following the Java Feature Flags API refactor, the development agent makes older providers return caller defaults instead of evaluating flags. Previously passing system tests now fail when CI combines agent
1.69.0-SNAPSHOTwith provider1.68.0. On unchanged system-tests main,test_default_agentless_sourcepasses with the released1.68.0pair and fails when only the agent is upgraded to that development build.These failures exercise a version pairing we advise customers not to use. This PR makes Java
system-testsdevelopment CI download the provider alongside the agent from the same development branch, so it tests the matching components together.Changes
Download
dd-openfeature.jaralongsidedd-java-agent.jarfrom the selected Java development branch. The existing weblog and parametric installers already consume the custom provider JAR. A missing provider download fails the loader instead of silently falling back to a released version. Java Lambda retains its existing agent-only download.This fixes shared development-artifact selection independently of #8093; no test assertions or activation gates change.
Validation
Ran
Test_FFE_Agentless_Configuration::test_default_agentless_sourceusing unmodified main test/application sources (f95c57973), then the downloader change:df2ab9bf59)defaultinstead ofon-value; no configuration requestsdf2ab9bf59)./format.sh --checkpassed.Live validation covered the focused agentless test on ARM64; the full Java matrix remains for CI.