Support multiple lang-branch overrides in PR title#6468
Draft
Conversation
Previously, specifying a tracer branch override in the PR title (e.g. [java@my-branch]) only supported a single override at a time. This change allows multiple overrides like [java@branch1][dotnet@branch2] so that different libraries can each use their own dev branch. The get_target_branch action now outputs a JSON map of library to branch, and the compute-workflow-parameters workflow extracts the correct branch for each library before passing it to load-binary.sh. Backward compatibility with plain branch strings is preserved. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
|
|
Update target branch selection docs to reflect that multiple [lang@branch] pairs can now be specified simultaneously in the PR title. Update the workflow parameter description to note JSON map support. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
The system-tests CI supports specifying a tracer branch override in the PR title like
[java@my-branch], but it only supported one branch override at a time. This made it impossible to test PRs that need changes from multiple tracer libraries simultaneously (e.g.[java@branch1][dotnet@branch2]).Changes
get_target_branchaction: Updated to capture all[lang@branch]pairs from the PR title and output them as a JSON map (e.g.{"java":"branch1","dotnet":"branch2"}). Added ahas-target-branchboolean output.compute-workflow-parameters.yml: Added a step to extract the specific library's branch from the JSON map before passing it toload-binary.sh. Also extracts theagentbranch separately for properAGENT_TARGET_BRANCHenv var support.compute_libraries_and_scenarios.yml: Exposed the newhas-target-branchoutput.ci.yml: Updated the "Fail if target branch is specified" check to use the newhas-target-branchoutput.Backward compatibility is preserved: plain branch strings from external callers still work via the legacy fallback path.
Examples
My PR [java@branch1]{"java":"branch1"}My PR [java@b1][dotnet@b2]{"java":"b1","dotnet":"b2"}My PR [java@b1][golang@b2][ruby@b3]{"java":"b1","golang":"b2","ruby":"b3"}My PR(no override)Workflow
🚀 Once your PR is reviewed and the CI green, you can merge it!
🛟 #apm-shared-testing 🛟
Reviewer checklist
tests/ormanifests/is modified ? I have the approval from R&P teambuild-XXX-imagelabel is present🤖 Generated with Claude Code