titan-iac/services/jenkins/configmap-plugins.yaml
jenkins 162c59047d feat(jenkins): install junit and pipeline-stage-view
Without the junit plugin the pipeline's junit step throws NoSuchMethodError,
jenkins.failed_tests is always empty, and auto-triage has only raw console
text to reason from. That was the root of two separate diagnosis failures:
the enforced failure being crowded out of the evidence budget, and the
patcher being unable to locate the defective source file.

Pinned to junit 1369.v15da_00283f06, the newest release that runs on core
2.528.3 - the current 1418 requires 2.533. scm-api moves 724 -> 728 because
the workflow-cps these pull in requires it; verified the whole 30-plugin
dependency closure needs no core newer than 2.528.3, and rehearsed the exact
jenkins-plugin-cli install in a throwaway pod before committing.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-06 06:08:17 -03:00

30 lines
1.0 KiB
YAML

# services/jenkins/configmap-plugins.yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: jenkins-plugins
namespace: jenkins
data:
plugins.txt: |
kubernetes:4423.vb_59f230b_ce53
workflow-aggregator:608.v67378e9d3db_1
git:5.8.1
pipeline-utility-steps:2.20.0
configuration-as-code:2036.v0b_c2de701dcb_
oic-auth:4.609.v9de140f63d01
job-dsl:1.93
simple-theme-plugin:230.v8b_fd91b_b_800c
workflow-multibranch:821.vc3b_4ea_780798
branch-api:2.1268.v044a_87612da_8
scm-api:728.vc30dcf7a_0df5
gitea:268.v75e47974c01d
gitea-checks:603.621.vc708da_fb_371d
multibranch-scan-webhook-trigger:1.0.11
# Structured test evidence. Without junit the `junit` step throws
# NoSuchMethodError, jenkins.failed_tests is always empty, and triage
# has only raw console text to work from. Pinned to the newest release
# that runs on core 2.528.3 - the current 1418 needs 2.533. The scm-api
# bump above is required by the workflow-cps these pull in.
junit:1369.v15da_00283f06
pipeline-stage-view:2.41