Skip to content

Merge supplementalGroups when combining pod YAML with builder spec#2850

Open
amarkdotdev wants to merge 1 commit into
jenkinsci:masterfrom
amarkdotdev:fix/supplemental-groups-yaml-override
Open

Merge supplementalGroups when combining pod YAML with builder spec#2850
amarkdotdev wants to merge 1 commit into
jenkinsci:masterfrom
amarkdotdev:fix/supplemental-groups-yaml-override

Conversation

@amarkdotdev

@amarkdotdev amarkdotdev commented Jul 8, 2026

Copy link
Copy Markdown
Member

Fixes #2849

Summary

  • Merge supplementalGroups in PodTemplateUtils.combine(Pod, Pod) alongside existing pod-level runAsUser / runAsGroup handling
  • Add unit tests in PodTemplateUtilsTest and SupplementalGroupsYamlOverrideReproTest

Problem

Pod template Supplemental Groups are dropped when raw pod YAML uses Override merge strategy. Jenkins console raw YAML and the live pod both show only:

securityContext:
  runAsGroup: 1000
  runAsUser: 1000

Test plan

  • PodTemplateUtilsTest#shouldCombinePodSupplementalGroupsFromTemplate
  • SupplementalGroupsYamlOverrideReproTest
  • CI (mvn verify)

PodTemplateUtils.combine() only copied runAsUser and runAsGroup into the
merged pod securityContext. supplementalGroups configured on the pod
template (UI, CasC, or pipeline) were dropped whenever raw pod YAML was
present with the Override merge strategy.

Add supplementalGroups resolution alongside the existing pod-level security
context merge and cover the regression in unit tests.

Signed-off-by: amarkdotdev <amarkdotdev@users.noreply.github.com>
@amarkdotdev amarkdotdev force-pushed the fix/supplemental-groups-yaml-override branch from 1f1b028 to c122a91 Compare July 12, 2026 19:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

supplementalGroups dropped from pod when raw YAML uses Override merge strategy

1 participant